diff options
author | Adrian Freihofer <adrian.freihofer@siemens.com> | 2020-03-17 16:26:50 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-03-19 09:59:56 +0000 |
commit | 59bfdc331c1494c05ab38804b281878a1f571f6d (patch) | |
tree | bcc3f33da1e483fb9622bb0163f50bd4c692b095 /meta/recipes-core/musl | |
parent | 61d80b07bcfa4adf5f1feb2904fec0a8d09c89f6 (diff) | |
download | openembedded-core-contrib-59bfdc331c1494c05ab38804b281878a1f571f6d.tar.gz |
runqemu: support multiple NICs
Emulating more than one network interface with runqemu is a bit tricky,
but possible. For example, the following leads to an emulated device with
eth0 and eth1:
QB_NETWORK_DEVICE_prepend = " \
-device virtio-net-device,mac=52:54:00:12:34:03 \
"
or
QB_NETWORK_DEVICE_append = " \
-device virtio-net-pci,mac=52:54:00:12:34:03 \
"
When booting Qemu with two NICs, the kernel does not know which
interface the specified ip=192.168.7.... command line argument
should be applied. This delays the boot process for a very long
time and a guest wihtout IP configuration.
This add two new configuraton parameters to runqemu:
QB_CMDLINE_IP_SLIRP and QB_CMDLINE_IP_TAP to explicitely specify the ip=
kernel command line arguments for tap and slirp mode.
Note: Simply adding "::eth0" broke some builds on the Yocto autobuilder.
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/musl')
0 files changed, 0 insertions, 0 deletions