Bug#742076: [Pkg-libvirt-maintainers] Bug#742076: libvirt-bin: setvcpus command fails to shrink the numbers of vcpu

2014-03-20 Thread Sdkfz262
Oops it seems that my sentence was misleading. I do edit the definition file through "virsh edit", I don't edit directly the file stored in /etc/libvirt/... I've just performed the modification the way you described it and restarted the domain. Back to "normal", that is : vcpucount maximum

Bug#742076: [Pkg-libvirt-maintainers] Bug#742076: libvirt-bin: setvcpus command fails to shrink the numbers of vcpu

2014-03-20 Thread Guido Günther
On Thu, Mar 20, 2014 at 11:34:09AM +0100, Sdkfz262 wrote: > Hi Guido, > > And thanks for that quick feedback. From what you wrote and the post you > linked Yesterday I understand that's not a bug, or at least not a Debian > bug, but something which requires (as of now) more configuration than a >

Bug#742076: [Pkg-libvirt-maintainers] Bug#742076: libvirt-bin: setvcpus command fails to shrink the numbers of vcpu

2014-03-20 Thread Sdkfz262
Hi Guido, And thanks for that quick feedback. From what you wrote and the post you linked Yesterday I understand that's not a bug, or at least not a Debian bug, but something which requires (as of now) more configuration than a simple "setvcpus" while the guest is running. I gave a try to yo

Bug#742076: [Pkg-libvirt-maintainers] Bug#742076: libvirt-bin: setvcpus command fails to shrink the numbers of vcpu

2014-03-19 Thread Guido Günther
Hi, > While on the guest side a cat /proc/cpuinfo still gives back two cpu > available. This needs support from qemu and (at least last time I checked) a running guest agent. This isn't available in wheezy so you should see the updated CPUs after reboot only. See. e.g.: http://lost-and-found