Other behaviors of the xen provisioning adapter that you should be aware of include the following:
The VM Builder running on a SLES 11 VM host now supports three additional VM OS types:
These OS types are not available for build when you use the VM Builder running on a SLES 10 SP2 VM host. These OS types can only be built and provisioned to a SLES 11 VM host.
VMs that were supported on SLES 10 SP2 are supported on SLES 11; that is, if the VM was built on SLES 10 SP2, the provisioning adapter supported for that VM on SLES 10 SP2 can also be supported when the VM runs on SLES 11.
Although VM migration from a SLES 11 VM host to a SLES 10 SP2 VM host is not supported, VM migration is supported in the following scenarios:
VM on a SLES 10 SP2 VM host migrating to a SLES 11 VM host
VM on a SLES 10 SP2 VM host migrating to a SLES 10 SP2 VM host
VM on a SLES 11 VM host migrating to a SLES 11 VM host
Virtual machines built on SLES 10 SP2 can be provisioned on either SLES 10 SP2 or SLES 11 VM hosts.
Virtual machines (regardless of OS type) built on SLES 11 cannot be provisioned on a SLES 10 SP2 VM host.
RHEL 5 VMs managed by the xen provisioning adapter must have the following characteristics:
They must not use LVM
If LVM is used on the VM, its volume groups (VGs) must have unique (that is, non-default) names.
To illustrate what can happen when you use a default LVM configuration, consider the following example:
You create two RHEL 5 VMs. During this process, the default disk configuration (which incorporates LVM) is utilized, so the two VMs have identical VG names. If these VMs are located on the same Xen host, a naming conflict occurs when those VMs are concurrently discovered by the Orchestration Server. This results in one of the VMs not being properly discovered.
HINT:As a general rule, we do not recommend using LVM for VM disks.
For information about the VMs provisioned by this provisioning adapter, see Section 21.1, Configuration Policies Used by the SUSE Xen Provisioning Adapter.