[libvirt] qemu error: "fsdev is not supported by this qemu build."

When trying to add a 9p filesystem to a guest, I get the qemu error "fsdev is not supported by this qemu build." (when starting the guest). I'm still looking at this. It seems to be something to do with the machine type causing the -fsdev option not to be registered inside qemu. I just wanted to record the problem here in case anyone else has any ideas. Full XML and qemu command line is below. Occurs with: libvirt-0.9.2-2.fc16.x86_64 2:qemu-system-x86-0.14.0-8.fc16.x86_64 Also occurs with the latest qemu & libvirt in Fedora 15, but reportedly not with older versions of qemu. Rich. ---------------------------------------------------------------------- <domain type='kvm'> <name>F14x64</name> <uuid>799ae7ca-23a2-f622-c691-48feebcddbe6</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc-0.14'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu match='exact'> <model>core2duo</model> <vendor>Intel</vendor> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/vg_pin/F14x64'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/tmp'/> <target dir='org.kernel.tmp'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </filesystem> <interface type='network'> <mac address='52:54:00:18:04:63'/> <source network='default'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/tmp/f14socket'/> <target type='virtio' name='org.libguestfs.channel.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='de'/> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <watchdog model='ib700' action='reset'/> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </memballoon> </devices> </domain> ---------------------------------------------------------------------- LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc-0.14 -cpu core2duo -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name F14x64 -uuid 799ae7ca-23a2-f622-c691-48feebcddbe6 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/F14x64.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -boot c -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/dev/vg_pin/F14x64,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/tmp -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=org.kernel.tmp,bus=pci.0,addr=0x6 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:18:04:63,bus=pci.0,addr=0x4 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/tmp/f14socket,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.libguestfs.channel.0 -usb -vnc 127.0.0.1:0 -k de -vga cirrus -device ib700,id=watchdog0 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 qemu-kvm: -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/tmp: there is no option group "fsdev" fsdev is not supported by this qemu build. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/

On Wed, Jun 22, 2011 at 11:43:48AM +0100, Richard W.M. Jones wrote:
When trying to add a 9p filesystem to a guest, I get the qemu error "fsdev is not supported by this qemu build." (when starting the guest).
I'm still looking at this. It seems to be something to do with the machine type causing the -fsdev option not to be registered inside qemu. I just wanted to record the problem here in case anyone else has any ideas.
Full XML and qemu command line is below.
This is all fine & practically identical to what I've used
Occurs with:
libvirt-0.9.2-2.fc16.x86_64 2:qemu-system-x86-0.14.0-8.fc16.x86_64
I have qemu-0.14.0-0.1.201102107aa8c46.fc15.x86_64 which I built myself. IIUC the code, the only way you can lack the fsdev support is if libattr.so was not present during the build. So perhaps the Fedora QEMU RPM is missing a BuildRequires: libattr-devel, and I just happened to have that available on the machine I did my build on. Regards, 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 Wed, Jun 22, 2011 at 12:27:50PM +0100, Daniel P. Berrange wrote:
On Wed, Jun 22, 2011 at 11:43:48AM +0100, Richard W.M. Jones wrote:
When trying to add a 9p filesystem to a guest, I get the qemu error "fsdev is not supported by this qemu build." (when starting the guest).
I'm still looking at this. It seems to be something to do with the machine type causing the -fsdev option not to be registered inside qemu. I just wanted to record the problem here in case anyone else has any ideas.
Full XML and qemu command line is below.
This is all fine & practically identical to what I've used
Occurs with:
libvirt-0.9.2-2.fc16.x86_64 2:qemu-system-x86-0.14.0-8.fc16.x86_64
I have qemu-0.14.0-0.1.201102107aa8c46.fc15.x86_64 which I built myself. IIUC the code, the only way you can lack the fsdev support is if libattr.so was not present during the build. So perhaps the Fedora QEMU RPM is missing a BuildRequires: libattr-devel, and I just happened to have that available on the machine I did my build on.
Yep, that's the problem. Looking in http://kojipkgs.fedoraproject.org/packages/qemu/0.14.0/8.fc16/data/logs/x86_... I see the configure summary: ATTR/XATTR support no 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 Wed, Jun 22, 2011 at 12:33:49PM +0100, Daniel P. Berrange wrote:
On Wed, Jun 22, 2011 at 12:27:50PM +0100, Daniel P. Berrange wrote:
On Wed, Jun 22, 2011 at 11:43:48AM +0100, Richard W.M. Jones wrote:
When trying to add a 9p filesystem to a guest, I get the qemu error "fsdev is not supported by this qemu build." (when starting the guest).
I'm still looking at this. It seems to be something to do with the machine type causing the -fsdev option not to be registered inside qemu. I just wanted to record the problem here in case anyone else has any ideas.
Full XML and qemu command line is below.
This is all fine & practically identical to what I've used
Occurs with:
libvirt-0.9.2-2.fc16.x86_64 2:qemu-system-x86-0.14.0-8.fc16.x86_64
I have qemu-0.14.0-0.1.201102107aa8c46.fc15.x86_64 which I built myself. IIUC the code, the only way you can lack the fsdev support is if libattr.so was not present during the build. So perhaps the Fedora QEMU RPM is missing a BuildRequires: libattr-devel, and I just happened to have that available on the machine I did my build on.
Yep, that's the problem. Looking in
http://kojipkgs.fedoraproject.org/packages/qemu/0.14.0/8.fc16/data/logs/x86_...
I see the configure summary:
ATTR/XATTR support no
Ah, missing BR, which also explains why my qemu RPM built by hand worked OK ... I'll fix this up in Fedora. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
participants (2)
-
Daniel P. Berrange
-
Richard W.M. Jones