On Tue, 2014-05-27 at 12:22 +0200, Adrian Freihofer wrote: > Fixes [YOCTO #6356] > > Problem: If QEMU parameters are extended to emulate additional > network interfaces, NFS boot does not work. Example: > runqemu ... qemuparams="-net nic,model=virtio... -net tap, ..." > This is solved by extending the kernel parameters by "::eth0:on" > --- > scripts/runqemu-internal | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal > index d317dfd..30d6514 100755 > --- a/scripts/runqemu-internal > +++ b/scripts/runqemu-internal > @@ -249,7 +249,7 @@ else > n1=$(($n0 * 2 + 1)) > n2=$(($n1 + 1)) > > - KERNEL_NETWORK_CMD="ip=192.168.7.$n2::192.168.7.$n1:255.255.255.0" > + > KERNEL_NETWORK_CMD="ip=192.168.7.$n2::192.168.7.$n1:255.255.255.0::eth0:on" > QEMU_TAP_CMD="-net tap,vlan=0,ifname=$TAP,script=no,downscript=no" > if [ "$KVM_ACTIVE" = "yes" ]; then > QEMU_NETWORK_CMD="-net nic,model=virtio $QEMU_TAP_CMD,vhost=on"
Unfortunately this results in failures in all our automated sanity tests: https://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/94/steps/Running%20Sanity%20Tests_1/logs/stdio Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
