PlateSpin Orchestrate modifies a paravirtualized or hardware virtualized Xen VM with the appropriate driver to match its network adapters. The “ioemu” driver is meant only for a fully virtualized guest, while the “netfront” driver is a paravirtualized driver that can be used either with a paravirtualized guest or with a hardware virtualized guest that has the proper paravirtualized drivers installed.

If you find that the VM is not obtaining proper connectivity or if you encounter some other networking error, check the vnic.type custom fact for the vNIC that is associated with the VM. Make sure the value for this fact matches the type of network adapter required by the VM.

If you use virt-manager to create a VM in the default repository and then copy its config file from /etc/xen/vm/<VM_name> to a new location on a different repository, both of these config files point to the same physical disk image. If you do not remember to use the xm delete command on the original VM, the Discovery action on both the original repository and the new repository results in the same VM being discovered in both repositories. This can cause the provisioning adapter to become confused as to which repository holds the VM image you want to use. To avoid this issue, we recommend that you use the Orchestrate Development Client to move any VMs you happen to create manually. The client takes care of properly deleting and re-creating the configuration for the VM.