Ask Your Question

Revision history [back]

When you modify VM properties this way, Nova’s database will contai incorrect information about its instances and hypervisor hosts, which is likely to cause problems. As a minimum, Nova will schedule new instances based on incorrect hypervisor hosts’ resource usage data.

Having said that, you could use Virtual Machine Manager, or write your own tools using a libvirt library, or perhaps even kill the qemu process and rerun it manually (not easy given the complexity of its command line options).

I am curious why you want to launch VMs with OpenStack and then manage them with another tool? And why you need an alternative to virsh?

When you modify VM properties this way, Nova’s database will contai contain incorrect information about its instances and hypervisor hosts, which is likely to cause problems. As a minimum, Nova will schedule new instances based on incorrect hypervisor hosts’ resource usage data.

Having said that, you could use Virtual Machine Manager, or write your own tools using a libvirt library, or perhaps even kill the qemu process and rerun it manually (not easy given the complexity of its command line options).

I am curious why you want to launch VMs with OpenStack and then manage them with another tool? And why you need an alternative to virsh?