search

stackhpc / ansible-role-libvirt-vm

This role configures and creates VMs on a KVM hypervisor.
128 stars 67 forks source link

Changing definition of VM does not seem to update VM #74

Closed thomwiggers closed 3 years ago

thomwiggers commented 3 years ago

I've changed the definition of my vm, eg. the amount of RAM, but the "ensure the VM is defined" task doesn't do anything.

I'm running Debian 10 with KVM. libvirt-python is version 5.0. I've checked using virsh define updated.xml. updated.xml was created via virsh dumpxml > updated.xml and then changing the number of CPU cores. If I then do virsh dumpxml --inactive | grep vcpu I see the new value.

But if I try to make the same change via this Ansible module, nothing happens.

thomwiggers commented 3 years ago

though that might just be https://github.com/ansible-collections/community.libvirt/pull/48

Edit: nope, that doesn't solve it.

thomwiggers commented 3 years ago

It's a problem in the community.virt.libvirt command.

thomwiggers commented 3 years ago

https://github.com/ansible-collections/community.libvirt/issues/53

markgoddard commented 3 years ago

Thanks for updating.