[poky] QEMU bug in scripts (maybe just XILINX zynq)
Arno
star at gmx.li
Thu Jun 2 03:24:00 PDT 2016
Not sure whether this is a bug in xilinx or in poky layer.
"runqemu qemuzynq" out of the yocto build directory failed.
Reason is, that it calls qemu with params: "-net nic,model=virtio", which is not present.
Instead of this, the available nic for zynq is "candence_gem".
I searched a while and found this hardcoded it poky/scripts/qemurun-internal.
A change there, and it works.
The second issue is with qemu and NFS.
According to manual I call
yocto_qemu$ runqemu qemuzynq ~/.y/nfs_qemu
The output is below:
-----------
Assuming /home/user/.y/nfs_qemu is an nfs rootfs
Continuing with the following parameters:
KERNEL: [/home/user/.y/yocto_qemu/tmp/deploy/images/qemuzynq/uImage]
ROOTFS: [/home/user/.y/nfs_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/.y/nfs_qemu
No PID file, not stopping rpc.nfsd
Creating exports file...
Starting User Mode nfsd
/home/user/.y/yocto_qemu/tmp/sysroots/x86_64-linux/usr/bin/pseudo -P /home/user/.y/yocto_qemu/tmp/sysroots/x86_64-linux/usr /home/user/.y/yocto_qemu/tmp/sysroots/x86_64-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/.y/nfs_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/.y/nfs_qemu
Stopping rpc.nfsd
Removing exports file
---------
The "Error: Unable to support this combination of options" is issued by runqemu-internal.
best regards
Arno
More information about the poky
mailing list