Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • MOVED events are not propagated when the virtual machine is moved to a host not managed by Abiquo (it is not added to Abiquo and not monitored by the Monitor Manager/Virtual System Monitor) but it is managed by vCenter. The virtual machine will remain with the last known state. Then:
    • if the destination host is added to Abiquo, a MOVED event will be generated properly.
    • if the virtual machine goes back to the original host, its state will be updated.
  • VMWare HA is not supported.
  • Abiquo does not support movements between machines with different Network Service Types unless the machines are connected to a dvSwitch. You must configure the same network service type for source and destination machine network interfaces or you will not be able to use the moved VM in Abiquo.
    • dvSwitch :   Abiquo will only allow you to change the Network Service Type of a dvSwitch if there are no virtual machines deployed on any of the machines attached to that dvSwitch. 
  • Storage vMotion to the same ESX host is supported since version 3.0
    • When you are performing a vMotion operation, vCenter asks if you want to migrate the datastore on which the VM is located. If you vMotion a VM to the same host and you just change the destination datastore, this will work in vCenter and Abiquo will detect it when it synchronizes the virtual machine defintiondefinition. You can set the frequency of this check with the abiquo.vsm.vmsyncfrequency.vmx_04 property. See Abiquo Configuration Properties#vsm

...