runqemu-internal: add NIC to kernel parameters
PATCH 1/1 runqemu-internal: add NIC to kernel parameters
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(-)
scripts/runqemu-internal +1 -1
@@ -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"
Signature · 1 line
1.9.1
Quoted 15 lines · Adrian Freihofer
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(-)scripts/runqemu-internal +0
-0
scripts/runqemu-internal else · line 255
Quoted 8 lines
scripts/runqemu-internal +1
-1@@ -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:
Cheers,
Richard
Quoted 20 lines · Richard Purdie
Quoted 18 lines · Adrian Freihofer
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(-)scripts/runqemu-internal +0
-0@@ -249,7 +249,7 @@ else n1=$(($n0 * 2 + 1)) n2=$(($n1 + 1))
Quoted 1 line
scripts/runqemu-internal else · line 252
Quoted 1 line
scripts/runqemu-internal +0
-1-
KERNEL_NETWORK_CMD="ip=192.168.7.$n2::192.168.7.$n1:255.255.255.0"
Quoted 1 line
scripts/runqemu-internal else · line 252
Quoted 1 line
scripts/runqemu-internal +1
-0+
KERNEL_NETWORK_CMD="ip=192.168.7.$n2::192.168.7.$n1:255.255.255.0::eth0:on"
Quoted 1 line
scripts/runqemu-internal else · line 253
Quoted 1 line
scripts/runqemu-internal +0
-0QEMU_TAP_CMD="-net
tap,vlan=0,ifname=$TAP,script=no,downscript=no"
Quoted 2 lines
scripts/runqemu-internal else · line 255
Quoted 2 lines
scripts/runqemu-internal +0
-0if [ "$KVM_ACTIVE" = "yes" ]; then QEMU_NETWORK_CMD="-net nic,model=virtio
$QEMU_TAP_CMD,vhost=on"
Quoted 4 lines
Unfortunately this results in failures in all our automated sanity tests:
It should be noted that minimal images do have network so this might upset connman...
Cheers,
Stefan
Quoted 1 line
Quoted 10 lines
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core