diff options
author | Robert Yang <liezhi.yang@windriver.com> | 2016-11-28 22:02:05 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-01-23 12:04:00 +0000 |
commit | 7dddd090806914a62d977730440d803e48f44763 (patch) | |
tree | 9e61013e8bd5f73b8344afe6a898340e41a33175 /oe-init-build-env-memres | |
parent | 84b2281595bbdb497daa42640e3ee4658bf0bed8 (diff) | |
download | openembedded-core-7dddd090806914a62d977730440d803e48f44763.tar.gz openembedded-core-7dddd090806914a62d977730440d803e48f44763.tar.bz2 openembedded-core-7dddd090806914a62d977730440d803e48f44763.zip |
runqemu: fixes for slirp, network device and hostfwd
Fixed:
- Add QB_NETWORK_DEVICE to set network device, it will be used by both
slirp and tap.
- Set QB_NETWORK_DEVICE to "-device virtio-net-pci" in qemuboot.bbclass
but runqemu will default to "-device e1000" when QB_NETWORK_DEVICE is
not set, this is because oe-core's qemu targets support
virtio-net-pci, but the one outside of oe-core may not,
"-device e1000" is more common.
- Set hostfwd by default: 2222 -> 22, 2323 -> 23, and it will choose a
usable port when the one like 222 is being used. This can avoid
conflicts when multilib slirp qemus are running. We can forward more
ports by default if needed, and bsp.conf can custom it.
- Use different mac sections for slirp and tap to fix conflicts when
running both of them on the same host.
[YOCTO #7887]
CC: Nathan Rossi <nathan@nathanrossi.com>
CC: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Diffstat (limited to 'oe-init-build-env-memres')
0 files changed, 0 insertions, 0 deletions