Closed edgd1er closed 8 months ago
Any VM still using nvram is problematic when using virsh or libvirt commands. I will look to see if I can make it work but it seems like libvirt/virsh support for nvram is not good. Do you still have the issue when the VM is powered off?
all commands were ran when vm was shutdown as --live arg with the same commands were not giving more results. is the plugin deleting the vm before recreating the same when editing memory or vcpu ?
the link gave me information: https://earlruby.org/2014/05/increase-a-vms-vcpu-count-with-virsh/
all commands were ran when vm was shutdown as --live arg with the same commands were not giving more results.
Does that mean you used menus in the plugin while it was shutdown and things still didn't work?
is the plugin deleting the vm before recreating the same when editing memory or vcpu ?
No. The plugin runs libvirt or virsh commands. Those commands may redefine the xml behind the scenes.
all commands were ran when vm was shutdown as --live arg with the same commands were not giving more results.
Does that mean you used menus in the plugin while it was shutdown and things still didn't work?
yes, here is what I tried:
<vcpu placement='static'>6</vcpu>
<topology sockets='1' dies='1' cores='3' threads='2'/>
``
Can you post the xml for the VM causing issues?
error when upgrading from 2 to 4 cpu.
So, it doesn't work because you have something other than one for threads. The plugin is only changing cores and vcpu must match sockets cores threads, You have 2 threads which means the plugin is setting vcpu to half of what it should. If I change the plugin to force one for threads, sockets, and dies, it works fine.
This is fixed now by forcing the dies, sockets, and threads to 1.
thanks for the fix.
I have a ryzen 5600g (12 cpu) on which i set up a 2 cpu windows 11 vm. That was ok until i tried to add 2 cpu to the vm.
I got this error:
I suppose the plugin try to dele the vm to recreate it. I tried to change through command lines without any success:
when trying to edit the xml, I managed to set vcpu, changing these two values vcpu placement and cores:
I set librvirt-manager with ssh+qemu to have access to all settings. I hope that the manager won't set feature that the plugin won't be able to handle.
I'm new to kvm and this plugin, I don't know if it's a known limitation, a bug or a feature to be developped.