3184 2012-09-26 22:29:59 +0000 running an image with kvm enabled fails if the runqemu command is used 2012-10-08 14:35:42 +0000 1 1 7 Build System, Metadata & Runtime OE-Core virtual machines unspecified x86 Multiple VERIFIED FIXED 4b5d9da07c2b4946cf2321ce537047bd61366a6e Medium+ normal 1.3 M5 1 laurentiu.serban cristian.iorga alexandru.c.georgescu alexandru.damian poky.bs.watcher poky.watcher sgw --- --- --- oldest_to_newest 25816 0 laurentiu.serban 2012-09-26 22:29:59 +0000 Following the wiki https://wiki.yoctoproject.org/wiki/Running_an_x86_Yocto_Linux_image_under_QEMU_KVM causes this error while starting the machine: lserban@computer1:~/work/master/build$ runqemu tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-minimal-qemux86-20120926220014.rootfs.ext3 kvm nographic Set MACHINE to [qemux86] based on kernel [tmp/deploy/images/bzImage-qemux86.bin] Continuing with the following parameters: KERNEL: [tmp/deploy/images/bzImage-qemux86.bin] ROOTFS: [tmp/deploy/images/core-image-minimal-qemux86-20120926220014.rootfs.ext3] FSTYPE: [ext3] Setting up tap interface under sudo Acquiring lockfile for tap0... WARNING: distccd not present, no distcc support loaded. Running qemu-system-i386... /home/lserban/work/master/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel tmp/deploy/images/bzImage-qemux86.bin -net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no,vhost=on -drive file=tmp/deploy/images/core-image-minimal-qemux86-20120926220014.rootfs.ext3,if=virtio -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -nographic -enable-kvm -cpu host -m 128 --append "vga=0 root=/dev/vda rw mem=128M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 console=ttyS0" qemu-system-i386: -net tap,vlan=0,ifname=tap0,script=no,downscript=no,vhost=on: vhost-net requested but could not be initialized qemu-system-i386: -net tap,vlan=0,ifname=tap0,script=no,downscript=no,vhost=on: Device 'tap' could not be initialized Set 'tap0' nonpersistent Releasing lockfile of preconfigured tap device 'tap0' if the command /home/lserban/work/master/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel tmp/deploy/images/bzImage-qemux86.bin -net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no,vhost=on -drive file=tmp/deploy/images/core-image-minimal-qemux86-20120926220014.rootfs.ext3,if=virtio -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -nographic -enable-kvm -cpu host -m 128 --append "vga=0 root=/dev/vda rw mem=128M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 console=ttyS0" is run with sudo the machine starts. This is an incorrect behavior, the sudo password should be asked when the machine starts 25830 1 cristian.iorga 2012-09-27 06:35:54 +0000 Hello, This is the key: "vhost-net requested but could not be initialized" This is not a problem of poky, Yocto Linux or qemu. This basically means that the user did not configure properly vhost-net driver in order to be run also under a user without administrative rights. See this part from the guide: Change the kvm dev ownership for non-root user qemu is started as non-root user in poky, but /dev/kvm from some distribution remains root:root that only allow root to use KVM. To work around this, we need create a new group named kvm, and make both /dev/kvm and the non-root user belongs to it. $ sudo addgroup --system kvm $ sudo adduser $USER kvm $ sudo chown root:kvm /dev/kvm $ sudo chmod 0660 /dev/kvm The output of "ls -l /dev/kvm" should be like this: crw-rw----+ 1 root kvm 10, 232 2010-07-02 09:27 /dev/kvm On a system that runs udev, you will probably need to add the following line somewhere in your udev configuration so it will automatically give the right group to the newly created device (i-e for ubuntu add a line to /etc/udev/rules.d/40-permissions.rules). KERNEL=="kvm", GROUP="kvm" Something similar must be done for vhost-net!! Note You need log out then log in the non-root user to take the effect Some distributions have already made this, so that we can skip this step And also: Basically, follow the same guide as for enabling KVM on the host (step 1.), but replace kvm with vhost_net Or course that running under sudo solves the issue. And if someone authenticated himself/herself to run something under sudo, there a limited period of time in which the system does not ask you again for your password. 26022 2 alexandru.damian 2012-10-02 11:14:41 +0000 Please document all this with the ready-to-run copy-paste scripts in the Wiki page. The wiki page is not clear on what you are supposed to do. Please detect in the runqemu script when this error is triggered, and provide an informative message with a link to the wiki page. 26023 3 cristian.iorga 2012-10-02 11:17:52 +0000 Agreed. 1. Online guide will be updated. 2. Reported error will be clarified and a link to the online guide will be provided. Regards, Cristian 26105 4 cristian.iorga 2012-10-03 10:55:24 +0000 Patch submitted for review. 26106 5 cristian.iorga 2012-10-03 10:56:03 +0000 Online guide has been updated and clarified. See: https://wiki.yoctoproject.org/wiki/Running_an_x86_Yocto_Linux_image_under_QEMU_KVM 26189 6 cristian.iorga 2012-10-04 06:26:54 +0000 Fixed. 26342 7 alexandru.c.georgescu 2012-10-08 14:35:42 +0000 Verified. Following the wiki could help me boot qemu kvm enabled.