Hide Forgot
Description of problem: vhostforce can't be used with '-netdev tap,...,forcevhost=off' ? Version-Release number of selected component (if applicable): qemu-kvm-debuginfo-0.12.1.2-2.148.el6.x86_64 qemu-img-0.12.1.2-2.148.el6.x86_64 qemu-kvm-tools-0.12.1.2-2.148.el6.x86_64 gpxe-roms-qemu-0.9.7-6.4.el6.noarch qemu-kvm-0.12.1.2-2.148.el6.x86_64 How reproducible: Steps to Reproduce: 1. start guest with '-netdev tap,...,forcevhost=off' Actual results: qemu exits, error msg: qemu: -netdev tap,id=idgzAJ1F,vhost=on,ifname=t0-113608-cltH,script=/etc/qemu-ifup,downscript=no,forcevhost=off: Invalid parameter 'forcevhost' Expected results: Guest can boot up successfully Additional info: # qemu-kvm -drive file='/mnt/linux/RHEL-Server-5.6-64-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=qcow2,aio=native,snapshot=on -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,netdev=idqJrk0t,mac=9a:0c:2b:2e:ab:13,netdev=idqJrk0t,id=ndev00idqJrk0t,bus=pci.0,addr=0x3 -netdev tap,id=idqJrk0t,vhost=on,ifname='t0-165012-Ywsy',script='/etc/qemu-ifup',downscript='no',vhostforce=off ...
'vhostforce' option can be used in qemu-kvm-0.12.1.2-2.151.el6 I checked by perf tool, vhost_net can be forced enabled for rhel5/4 when 'vhostforce' is 'on' in fixed version. So moving to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: bug in the qemu option parse code. Consequence: vhost_force option could not be used. Fix: Fix qemu option parsing code. Result: vhost_force option could be used to force start vhost_net backend.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0534.html