Am 09.08.13 15:09, schrieb Eric Blake:> On 08/09/2013 06:26 AM, Thomas Stein wrote: >> Hello. >> >> Does someone know in what state setvcpu command is? >> >> I get: >> >> virsh # setvcpus gentookvm 4 >> error: internal error: cannot change vcpu count of this domain >> >> and >> >> error : qemuDomainHotplugVcpus:4087 : internal error: cannot change vcpu >> count of this domain >> >> Does this work for someone? > > It works for xen:// URIs. Upstream qemu vcpu hotplug is still a work in > progress; I don't know if qemu 1.6 will support it, or if you'll have to > wait for qemu 1.7. Meanwhile, you can try using 'setvcpus gentookvm > --guest 4' to use the guest agent (assuming you have qemu-ga running in > the guest, and the proper plumbing of the guest agent channel in your > domain XML) to use the guest to take vcpus on- or offline.Tried that with no luck so far. virsh # setvcpus gentookvm --guest 2 error: internal error: unable to execute QEMU agent command 'guest-get-vcpus': The command guest-get-vcpus has not been found It's qemu-1.4.2 and libvirt-1.1.1. In general it seems to work. virsh # shutdown 3 --mode agent Domain 3 is being shutdown Any hints? And once again, thanks for your support Eric. cheers t.
On 08/09/2013 09:01 AM, Thomas Stein wrote:>> Meanwhile, you can try using 'setvcpus gentookvm >> --guest 4' to use the guest agent (assuming you have qemu-ga running in >> the guest, and the proper plumbing of the guest agent channel in your >> domain XML) to use the guest to take vcpus on- or offline. > > Tried that with no luck so far. > > virsh # setvcpus gentookvm --guest 2 > error: internal error: unable to execute QEMU agent command > 'guest-get-vcpus': The command guest-get-vcpus has not been found > > It's qemu-1.4.2 and libvirt-1.1.1.There's your problem. Guest-agent support for hotplug wasn't introduced until qemu 1.5. Upgrade at least your qemu-ga in your guest, and probably also the qemu running your guest. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Am 09.08.13 17:03, schrieb Eric Blake:> On 08/09/2013 09:01 AM, Thomas Stein wrote: >>> Meanwhile, you can try using 'setvcpus gentookvm >>> --guest 4' to use the guest agent (assuming you have qemu-ga running in >>> the guest, and the proper plumbing of the guest agent channel in your >>> domain XML) to use the guest to take vcpus on- or offline. >> >> Tried that with no luck so far. >> >> virsh # setvcpus gentookvm --guest 2 >> error: internal error: unable to execute QEMU agent command >> 'guest-get-vcpus': The command guest-get-vcpus has not been found >> >> It's qemu-1.4.2 and libvirt-1.1.1. > > There's your problem. Guest-agent support for hotplug wasn't introduced > until qemu 1.5. Upgrade at least your qemu-ga in your guest, and > probably also the qemu running your guest.Okay, thank you. cheers t.
On Friday 09 August 2013 09:03:50 Eric Blake wrote:> On 08/09/2013 09:01 AM, Thomas Stein wrote: > >> Meanwhile, you can try using 'setvcpus gentookvm > >> > >> --guest 4' to use the guest agent (assuming you have qemu-ga running in > >> the guest, and the proper plumbing of the guest agent channel in your > >> domain XML) to use the guest to take vcpus on- or offline. > > > > Tried that with no luck so far. > > > > virsh # setvcpus gentookvm --guest 2 > > error: internal error: unable to execute QEMU agent command > > 'guest-get-vcpus': The command guest-get-vcpus has not been found > > > > It's qemu-1.4.2 and libvirt-1.1.1. > > There's your problem. Guest-agent support for hotplug wasn't introduced > until qemu 1.5. Upgrade at least your qemu-ga in your guest, and > probably also the qemu running your guest.Just upgraded qemu-quest-agent to 1.5.2 and now it works. Cool. Host still at 1.4.2 by the way. Thanks again. cheers t.