[OE-core] [meta-oe][PATCH 0/3] runqemu improve networking

[Aws Ismail]

Thanks Adrian for the explanation. I have tested it now and it works
fine in my case. I think this should be merged upstream because it is
an important feature to have specially if the user is planning to use
the VM for extended use.


Tested-by: Aws Ismail <aws.ismail at gmail.com>



On Tue, Nov 17, 2015 at 7:24 AM, Adrian Freihofer
<adrian.freihofer at gmail.com> wrote:
> Hi Aws
>
> The interfaces of my virtual device are configured as:
> eth0: static IP, 192.168.7.2 (This IP is hard coded in many scripts of poky.)
>       This interface is for debugging purpose, it is not available
>       on my physical devices running in a productive environment.
>       The interface is configured by the kernel command line
>       provided by the runqemu script. This interface should
>       (or must in case of NFS rootfs) be ignored by connman, networkmanager
>       or what ever manages the network settings of your device.
> eth1: Configured by connman or networkmanager running on the virtual device.
>       The part of the setup depends on the particular use case you need
>       to emulate. In my setup the tap interfaces of the host ar part
>       of a bridge. On the bridge a dnsmasq instance serves IP addresses.
>       This part of my setup is not published. It is verry specific. But based
>       on my patch set it should be easy to do something similar fitting your
>       use case. The simplest approach might be a static IP address e.g.
>       assigned by a bbappend file e.g. for connman.
>
> runqemu is started with additional parameters to create eth1:
> runqemu hostonly qemuparams="-device virtio-net-pci,netdev=netif1,mac=${macaddr1} -netdev
> tap,id=netif1,ifname=${HOST_TAP_NAME},script=no,downscript=no"
>
> Regards,
> Adrian
>
> On Mon, 2015-11-16 at 17:16 -0500, Aws Ismail wrote:
>> Hi Adrian,
>>
>> What's the runqemu line you are running with ?
>>
>> I am passing -net nic -net nic to the qemuparams line which works
>> fine, but the the two devices come up with no IP addresses.
>>
>> My full qemu line is:
>>
>> ROOTFS=<path to qemu.ext4> runqemu qemux86-64 nographic
>> qemuparams="-cpu host --enable-kvm -m 4096 -net nic -net nic"
>>
>> Aws\
>>
>> On Sun, Nov 15, 2015 at 1:01 AM, Aws Ismail <aws.ismail at gmail.com> wrote:
>> > Thanks Adrian for the patchset. I will test it and get back to you.
>> >
>> > Aws\
>> >
>> > On Sat, Nov 14, 2015 at 4:35 PM, Adrian Freihofer
>> > <adrian.freihofer at gmail.com> wrote:
>> > > This patch series adds two features to runqemu:
>> > > - Support the emulation of more than one NIC
>> > > - Add a hostonly networking mode. This networking mode enables
>> > >   the user to implement different virtual networking environments
>> > >   such as a bridged network as discussed in #7887.
>> > >
>> > > Note: Without the first patch connman fails if the virtual device
>> > >       provides more than one NIC.
>> > >
>> > > @Aws Ismail: I'm using this since more than one year. Would be great
>> > >              if you could test this and provide feedback.
>> > >
>> > > Adrian Freihofer (3):
>> > >   connman: fix qemu config
>> > >   runqemu: add support for multiple NICs
>> > >   runqemu: support hostonly net mode
>> > >
>> > >  .../connman/connman-conf/qemuall/wired-setup       |  6 ++--
>> > >  scripts/runqemu                                    |  7 +++-
>> > >  scripts/runqemu-gen-tapdevs                        | 11 ++++---
>> > >  scripts/runqemu-ifdown                             | 33 +++++++++++--------
>> > >  scripts/runqemu-ifup                               | 38 +++++++++++++---------
>> > >  scripts/runqemu-internal                           | 21 +++++++-----
>> > >  6 files changed, 72 insertions(+), 44 deletions(-)
>> > >
>> > > --
>> > > 2.4.3
>> > >