[libvirt-users] What's the most recent compatible libvirt and qemu-kvm?
Figured I'd test qemu-kvm-1.0.1 and libvirt-0.9.12, but the result after default compiles is: root@black:/usr/local/sbin# ./libvirtd 2012-06-12 19:53:41.894+0000: 6076: info : libvirt version: 0.9.12 2012-06-12 19:53:41.894+0000: 6076: warning : ebiptablesDriverInit:4084 : Could not find 'ebtables' executable 2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209 : unsupported configuration: this qemu binary requires libvirt to be compiled with yajl 2012-06-12 19:53:42.677+0000: 6076: error : virDomainDefParseXML:8312 : internal error No guest options available for arch 'x86_64' Is it just the "yajl" thing missing, or is this combo just not to be expected to work? Also, should http://libvirt.org/compiling.html mention "yajl"? Thanks, Whit
On Tue, Jun 12, 2012 at 03:59:45PM -0400, Whit Blauvelt wrote:
Figured I'd test qemu-kvm-1.0.1 and libvirt-0.9.12, but the result after default compiles is:
root@black:/usr/local/sbin# ./libvirtd 2012-06-12 19:53:41.894+0000: 6076: info : libvirt version: 0.9.12 2012-06-12 19:53:41.894+0000: 6076: warning : ebiptablesDriverInit:4084 : Could not find 'ebtables' executable 2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209 : unsupported configuration: this qemu binary requires libvirt to be compiled with yajl 2012-06-12 19:53:42.677+0000: 6076: error : virDomainDefParseXML:8312 : internal error No guest options available for arch 'x86_64'
Is it just the "yajl" thing missing, or is this combo just not to be expected to work?
Yes, you need to install the yajl-devel RPM and rebuild libvirt. This is because latest QEMU binaries are quite alot of functionality that is only available via the JSON protocol monitor & libvirt needs this stuff.
Also, should http://libvirt.org/compiling.html mention "yajl"?
It should mention quite a lot more ! Look at the libvirt.spec.in file in libvirt GIT and see everything listed in a 'BuildRequires' line. You will want most of it present when building libvirt. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
On 06/13/2012 03:59 AM, Whit Blauvelt wrote:
Figured I'd test qemu-kvm-1.0.1 and libvirt-0.9.12, but the result after default compiles is:
root@black:/usr/local/sbin# ./libvirtd 2012-06-12 19:53:41.894+0000: 6076: info : libvirt version: 0.9.12 2012-06-12 19:53:41.894+0000: 6076: warning : ebiptablesDriverInit:4084 : Could not find 'ebtables' executable 2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209 : unsupported configuration: this qemu binary requires libvirt to be compiled with yajl 2012-06-12 19:53:42.677+0000: 6076: error : virDomainDefParseXML:8312 : internal error No guest options available for arch 'x86_64'
Is it just the "yajl" thing missing, or is this combo just not to be expected to work?
Also, should http://libvirt.org/compiling.html mention "yajl"? Need to install yajl-devel rpm package. Thanks, Whit
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
On 06/13/2012 01:14 PM, Alex Jia wrote:
On 06/13/2012 03:59 AM, Whit Blauvelt wrote:
Figured I'd test qemu-kvm-1.0.1 and libvirt-0.9.12, but the result after default compiles is:
root@black:/usr/local/sbin# ./libvirtd 2012-06-12 19:53:41.894+0000: 6076: info : libvirt version: 0.9.12 2012-06-12 19:53:41.894+0000: 6076: warning : ebiptablesDriverInit:4084 : Could not find 'ebtables' executable 2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209 : unsupported configuration: this qemu binary requires libvirt to be compiled with yajl 2012-06-12 19:53:42.677+0000: 6076: error : virDomainDefParseXML:8312 : internal error No guest options available for arch 'x86_64'
Is it just the "yajl" thing missing, or is this combo just not to be expected to work?
Also, should http://libvirt.org/compiling.html mention "yajl"? Need to install yajl-devel rpm package. # ./configure -h | grep yajl --with-yajl use YAJL for JSON parsing/formatting [default=check]
If you hasn't disable this option, libvirt will check yajl library default when compiling source codes then you will meet above error if you indeed hasn't install yajl relevant rpm package.
Thanks, Whit
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
On 06/12/2012 11:21 PM, Alex Jia wrote:
2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209 : unsupported configuration: this qemu binary requires libvirt to be compiled with yajl
Need to install yajl-devel rpm package. # ./configure -h | grep yajl --with-yajl use YAJL for JSON parsing/formatting [default=check]
Hmm, I'm wondering if libvirt's configure.ac should be enhanced to probe 'qemu -version' when qemu support is enabled, and insist on yajl in that case. Obviously, this probe would have to be tolerant of qemu not existing, but erroring out earlier than runtime might help people build correctly since this seems to be a recurring question on the list. And it must not break on RHEL 5, where qemu is old enough to not require yajl and where yajl is not available by default. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
On 06/13/2012 06:09 AM, Eric Blake wrote:
On 06/12/2012 11:21 PM, Alex Jia wrote:
2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209 : unsupported configuration: this qemu binary requires libvirt to be compiled with yajl
Need to install yajl-devel rpm package. # ./configure -h | grep yajl --with-yajl use YAJL for JSON parsing/formatting [default=check]
Hmm, I'm wondering if libvirt's configure.ac should be enhanced to probe 'qemu -version' when qemu support is enabled, and insist on yajl in that case. Obviously, this probe would have to be tolerant of qemu not existing, but erroring out earlier than runtime might help people build correctly since this seems to be a recurring question on the list. And it must not break on RHEL 5, where qemu is old enough to not require yajl and where yajl is not available by default.
In fact, I just proposed a patch to do that: https://www.redhat.com/archives/libvir-list/2012-June/msg00527.html -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
participants (4)
-
Alex Jia -
Daniel P. Berrange -
Eric Blake -
Whit Blauvelt