Re: [libvirt-users] [libvirt] libvirt 1.2.10 and latest EL6 qemu-kvm
[Dropping libvir list and adding libvir-users list.] On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote:
Hi all,
I had libvirt 1.2.10 running without issues together with the qemu package qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm
That's a really old QEMU and the libvirt you're using is relatively newer.
Now, after updating my server, qemu-kvm became version qemu-kvm-0.12.1.2-2.448.el6_6.x86_64
And as a result, when doing 'virsh start' (virsh define worked ok), the following error occured:
2015-01-19 15:05:26.539+0000: 4347: error : qemuMonitorJSONCheckError:379 : internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been
You seem to be hitting this bug (although the bug is for RHEL7, looks like the same behavior): https://bugzilla.redhat.com/show_bug.cgi?id=1082124 Where Michal Privoznik says, it should already be fixed with these commits in libvirt: 730af8f2cd7bc0e4c98b97200857909f42ea817f -- qemuMonitorJSONGetCPUx86Data: Don't fail on ancient qemus 84f69602143551433e3e0a5226dc572ecb33c059 -- qemu: Check for presence of device and properities when getting CPUID a6a6f84af92a506f83fdecf56f292bcb89905492 -- qemu: Change return type of qemuMonitorGetGuestCPU()
The only thing I could do (even downgrading libvirt to 1.2.9 didn't work), was to downgrade qemu-kvm to the older version again ... Any hints on this?
For the EL distrubtione you're using, I think using whatever the newest supported combination of libvirt and QEMU should help. -- /kashyap
Kashyap Chamarthy <kchamart@redhat.com> schreef op 19 januari 2015 19:00:23 CET:
[Dropping libvir list and adding libvir-users list.]
Hi all,
I had libvirt 1.2.10 running without issues together with the qemu
On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: package
qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm
That's a really old QEMU and the libvirt you're using is relatively newer.
Now, after updating my server, qemu-kvm became version qemu-kvm-0.12.1.2-2.448.el6_6.x86_64
And as a result, when doing 'virsh start' (virsh define worked ok), the following error occured:
2015-01-19 15:05:26.539+0000: 4347: error : qemuMonitorJSONCheckError:379 : internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been
You seem to be hitting this bug (although the bug is for RHEL7, looks like the same behavior):
https://bugzilla.redhat.com/show_bug.cgi?id=1082124
Where Michal Privoznik says, it should already be fixed with these commits in libvirt:
730af8f2cd7bc0e4c98b97200857909f42ea817f -- qemuMonitorJSONGetCPUx86Data: Don't fail on ancient qemus 84f69602143551433e3e0a5226dc572ecb33c059 -- qemu: Check for presence of device and properities when getting CPUID a6a6f84af92a506f83fdecf56f292bcb89905492 -- qemu: Change return type of qemuMonitorGetGuestCPU()
The only thing I could do (even downgrading libvirt to 1.2.9 didn't work), was to downgrade qemu-kvm to the older version again ... Any hints on this?
For the EL distrubtione you're using, I think using whatever the newest supported combination of libvirt and QEMU should help.
Yes, I know it's old but there is no newer qemu-kvm package on centos6. But the bug you reported is not the same: it is about qom-list, not qom-get and also: it workerd fine with an older qemu-kvm package. So I guess something in the newer qemu-kvm package has changed and libvirt is not yet taking that into account. I"d be more than happy to update qemu-kvm to something newer, but that requires a lot more work ... Franky Franky
On Mon, Jan 19, 2015 at 08:25:55PM +0100, Franky Van Liedekerke wrote:
Kashyap Chamarthy <kchamart@redhat.com> schreef op 19 januari 2015 19:00:23 CET:
[. . .]
And as a result, when doing 'virsh start' (virsh define worked ok), the following error occured:
2015-01-19 15:05:26.539+0000: 4347: error : qemuMonitorJSONCheckError:379 : internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been
I forgot to note, your error message is truncated. I guess it's 'qom-list has not been found"
You seem to be hitting this bug (although the bug is for RHEL7, looks like the same behavior):
https://bugzilla.redhat.com/show_bug.cgi?id=1082124
Where Michal Privoznik says, it should already be fixed with these commits in libvirt:
730af8f2cd7bc0e4c98b97200857909f42ea817f -- qemuMonitorJSONGetCPUx86Data: Don't fail on ancient qemus 84f69602143551433e3e0a5226dc572ecb33c059 -- qemu: Check for presence of device and properities when getting CPUID a6a6f84af92a506f83fdecf56f292bcb89905492 -- qemu: Change return type of qemuMonitorGetGuestCPU()
The only thing I could do (even downgrading libvirt to 1.2.9 didn't work), was to downgrade qemu-kvm to the older version again ... Any hints on this?
For the EL distrubtione you're using, I think using whatever the newest supported combination of libvirt and QEMU should help.
Yes, I know it's old but there is no newer qemu-kvm package on centos6.
You can probably check with the oVirt project, who does rebuilds of QEMU http://resources.ovirt.org/pub/ovirt-3.5/rpm/el6Server/x86_64/
But the bug you reported is not the same: it is about qom-list, not qom-get
Your error message says: "unable to execute QEMU command 'qom-list'" And, this commit message mentions 'qom-list' commit 730af8f2cd7bc0e4c98b97200857909f42ea817f Author: Michal Privoznik <mprivozn@redhat.com> Date: Tue Nov 19 15:42:28 2013 +0100 qemuMonitorJSONGetCPUx86Data: Don't fail on ancient qemus On the domain startup, this function is called to dump some info about the CPUs. At the beginning of the function we check if we aren't running older qemu which is not exposing the CPUs via 'qom-list'. However, we are not checking for even older qemus, which throw 'CommandNotFound' error. Signed-off-by: Michal Privoznik <mprivozn@redhat.com
and also: it workerd fine with an older qemu-kvm package. So I guess something in the newer qemu-kvm package has changed and libvirt is not yet taking that into account.
I'm not an expert on this subject, but if you want to narrow down the issue further, you might want to investigate with libvirt debug logs http://wiki.libvirt.org/page/DebugLogs
I"d be more than happy to update qemu-kvm to something newer, but that requires a lot more work ...
-- /kashyap
participants (2)
-
Franky Van Liedekerke -
Kashyap Chamarthy