1 Reply Latest reply on Jul 4, 2015 11:10 AM by npadmani

    ABOUT VMOTION

    vijayalka Novice
    Visibility: Open to anyone

      Virtual Machine Conditions and Limitations for vMotion in the vSphere Web Client

       

       

      To successfully migrate virtual machines with vMotion, the virtual machine must meet certain network, disk, CPU, USB, and other device requirements.

      The following virtual machine conditions and limitations apply:

      1

       

      The source and destination management network IP address families must match. You cannot migrate a virtual machine from a host that is registered to vCenter Server with an IPv4 address to a host that is registered with an IPv6 address.

      2

      If virtual CPU performance counters are enabled, you can migrate virtual machines only to hosts that have compatible CPU performance counters.

      Need ans of 2nd point in simple language.....

      3

      You can migrate virtual machines with USB devices that are connected to a physical USB device on the host. You must enable the devices for vMotion.

       

      Please explain 4th and 5th point which i can understand easily.

      4

      You cannot use migration with vMotion to migrate a virtual machine that uses a virtual device backed by a device that is not accessible on the destination host. For example, you cannot migrate a virtual machine with a CD drive backed by the physical CD drive on the source host. Disconnect these devices before you migrate the virtual machine.

      5

      You cannot use migration with vMotion to migrate a virtual machine that uses a virtual device backed by a device on the client computer. Disconnect these devices before you migrate the virtual machine.

       

      Query updated

        • 1. Re: ABOUT VMOTION
          npadmani Master
          vExpertVMware Employees

          2

          If virtual CPU performance counters are enabled, you can migrate virtual machines only to hosts that have compatible CPU performance counters.

          Need ans of 2nd point in simple language.....

          You can use performance tuning tools in the guest operating system for software profiling. You can identify and improve processor performance problems. This capability is useful for software developers who optimize or debug software that runs in the virtual machine. but then when it's in use, you face certain limitations like the one which is mentioned in point no 2 in your list

          Ref: VMware vSphere 5.1

           

          4. You cannot use migration with vMotion to migrate a virtual machine that uses a virtual device backed by a device that is not accessible on the destination host. For example, you cannot migrate a virtual machine with a CD drive backed by the physical CD drive on the source host. Disconnect these devices before you migrate the virtual machine.


          5. You cannot use migration with vMotion to migrate a virtual machine that uses a virtual device backed by a device on the client computer. Disconnect these devices before you migrate the virtual machine.

          Let's say we take an example of virtual CD/DVD drive of your VM, this has three options,

          Screen Shot 2015-07-04 at 11.32.52 pm.png

           

          Point number 4 in your list is referring to Host Device, if your VM's cd/dvd drive is set of Host Device, that means it has local dependancy, so it cannot be vMotion migrated. even if I try, it will give me following error

          Screen Shot 2015-07-04 at 11.32.23 pm.png

          Similarly if my VM's virtual hardware component is dependant upon physical hardware component on client device, that will also face trouble being vMotion migrated.

           

          See if this helps.