[poky] QEMU

[Arno]

Have problems starting QEMU in NFS mode.
Referring to this document:
http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#dev-manual-qemu

Configured with current krogath an qemuzynq and created an SDK.



According to manual I tried to start it out of bitbake folder:

user at VB:~/.y/yocto_qemu$ runqemu qemuzynq

Continuing with the following parameters:
KERNEL: [/home/user/.y/yocto_qemu/tmp/deploy/images/qemuzynq/uImage]
ROOTFS: [/home/user/.y/yocto_qemu/tmp/deploy/images/qemuzynq/core-image-minimal-qemuzynq-20160531062534.rootfs.cpio]
FSTYPE: [cpio]
Acquiring lockfile for tap0...
Using preconfigured tap device 'tap0'
If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
Running qemu-system-arm...
/home/user/.y/yocto_qemu/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm -kernel /home/user/.y/yocto_qemu/tmp/deploy/images/qemuzynq/uImage -net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M xilinx-zynq-a9 -serial null -serial mon:stdio -dtb /home/user/.y/yocto_qemu/tmp/deploy/images/qemuzynq/uImage-qemuzynq.dtb -initrd /home/user/.y/yocto_qemu/tmp/deploy/images/qemuzynq/core-image-minimal-qemuzynq-20160531062534.rootfs.cpio -no-reboot -m 1024 -append "earlyprintk root=/dev/ram rw ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=1024M "
qemu-system-arm: Unsupported NIC model: virtio
Releasing lockfile of preconfigured tap device 'tap0'

---

My Linux machine is an Ubuntu1604 (running as VM on Windows PC with Virtual Box).

Compared to 2 days ago I feel to be close, but can't manage it.


Best regards
Arno

PS: Actually I want o boot this out of SDK into NFS:

I extracted the rootfs
runqemu-extract-sdk tmp/deploy/images/qemuzynq/core-image-minimal-qemuzynq.tar.gz ~/rootfs_qemu

out of the SDK folder, with sourced environment for SDK:
source environment-setup-cortexa9hf-neon-poky-linux-gnueabi

Starting the qemu gives error, that I don't understand:

user at VB:~/sdk_qemu$ runqemu qemuzynq ~/yocto_qemu/tmp/deploy/images/qemuzynq/uImage--4.4-xilinx+git0+89cc643aff-r0-qemuzynq-20160531062534.bin ~/rootfs_qemu bootparams=\"172.20.20.171:/home/user/rootfs_qemu,nfsvers=3,port=,mountprog=,nfsprog=,udp,mountport=\"

Assuming /home/user/rootfs_qemu is an nfs rootfs

Continuing with the following parameters:
KERNEL: [/home/user/yocto_qemu/tmp/deploy/images/qemuzynq/uImage--4.4-xilinx+git0+89cc643aff-r0-qemuzynq-20160531062534.bin]
ROOTFS: [/home/user/rootfs_qemu]
FSTYPE: [nfs]
Acquiring lockfile for tap0...
Using preconfigured tap device 'tap0'
If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
runqemu-export-rootfs restart /home/user/rootfs_qemu
No PID file, not stopping rpc.nfsd
Creating exports file...
Starting User Mode nfsd
  /home/user/sdk_qemu/sysroots/x86_64-pokysdk-linux/usr/bin/pseudo -P /home/user/sdk_qemu/sysroots/x86_64-pokysdk-linux/usr /home/user/sdk_qemu/sysroots/x86_64-pokysdk-linux/usr/bin/unfsd -p -N -i /home/user/.runqemu-sdk/nfs0.pid -e /home/user/.runqemu-sdk/exports0 -x 11111 -n 3049 -y 21111 -m 3048
 
On your target please remember to add the following options for NFS
nfsroot=IP_ADDRESS:/home/user/rootfs_qemu,nfsvers=3,port=,mountprog=,nfsprog=,udp,mountport=
Error: Unable to support this combination of options
Releasing lockfile of preconfigured tap device 'tap0'
Shutting down the userspace NFS server...
runqemu-export-rootfs stop /home/user/rootfs_qemu
Stopping rpc.nfsd
Removing exports file


I tried also qemuparams instead of bootparams, but result was same. It seems it doesn't take over this params.

?!?!?