Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
thomwiggers opened this issue Dec 17, 2020 · 4 comments
Closed

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

thomwiggers opened this issue Dec 17, 2020 · 4 comments

Comments

@thomwiggers
Copy link
Contributor

thomwiggers commented Dec 17, 2020 •
edited
Loading

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
Copy link
Contributor Author

thomwiggers commented Dec 17, 2020 •
edited
Loading

though that might just be ansible-collections/community.libvirt#48

Edit: nope, that doesn't solve it.

@thomwiggers
Copy link
Contributor Author

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

@thomwiggers
Copy link
Contributor Author

ansible-collections/community.libvirt#53

@markgoddard
Copy link

Thanks for updating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thomwiggers @markgoddard