Cannot boot a new VPS on XenHVM node if the VMID greater than 10000

Symptoms

Cannot boot a new VPS on XenHVM node if the VMID greater than 10000. Here is an output on attempt to start VPS from command line:

# xl create -c /home/xen/vm10003/vm10003.cfg
Parsing config from /home/xen/vm10003/vm10003.cfg
WARNING: ignoring "vncviewer" option. Use "-V" option of "xl create" to automatically spawn vncviewer.
WARNING: you seem to be using "kernel" directive to override HVM guest firmware. Ignore that. Use "firmware_override" instead if you really want a non-default firmware
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge add [12018] exited with error status 1
libxl: error: libxl_device.c:1150:device_hotplug_child_death_cb: script: ip link set vif1541.0-emu name vifvm10003.0-emu failed
libxl: error: libxl_create.c:1384:domcreate_attach_vtpms: unable to add nic devices

Cause

Length name for virtual network interface (like vifvm10003.0) is too long

Resolution

1. Connect to the SolusVM Xen slave server via SSH
2. Comment out the option no_vif_prefix in configuration file /usr/local/solusvm/data/config.ini and set is as true

   CONFIG_TEXT: [XEN]
   ; Set this to true to remove the vifvm prefix from the interface vif names
   no_vif_prefix = true

3. If the file /usr/local/solusvm/data/config.ini does not exist, create it from /usr/local/solusvm/data/config.ini.example:

   # cp /usr/local/solusvm/data/config.ini.example /usr/local/solusvm/data/config.ini

4. The new setting will be applied for the new VPSes automatically. For already existing VPS, rewrite configuration file of the VPS by clicking on Rewrite Config icon on the virtual server management page:
   

If the issue persists on the new server, there is a probability that NetworkManager prevents starting virtual interface. Check the following article for more details