[OE-core] runqemu + dhcp server

Adrian Freihofer adrian.freihofer at gmail.com
Tue Feb 17 16:24:16 UTC 2015


On Tuesday 17 February 2015 11.34:14 you wrote:
> On Mon, 2014-11-10 at 22:57 +0100, Adrian Freihofer wrote:
> > > I haven't tried NFS rootfs. My hope is that it would still work because the
> > > ip parameter and the DHCP server assign the same IP address and thus nothing
> > > changes inside the guest when switching from one to the other.
> > > 
> > 
> > I see, the patch you are working on will provide just another option
> > to get eth0 configured. This would definitely be an improvement.
> 
> I had to put this aside for a while, but I'm still interested in getting
> this merged.
> 
> > Did you ever run the automated image tests? If I remember correctly
> > the image tests are somehow related to the current implementation of
> > the network configuration. At least the tests require a hostname
> > starting with "qemu" and probably they run from NFS rootfs.
> 
> Where do I find more information about these tests, in particular how to
> run them?
On 2014-05-29 I got the following hint from Saul Wold:
"You can try the sanity testing locally by setting IMAGETEST in local.conf (please look at local.conf for details)."
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=6356)[1]
> 
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#testing-packages-with-ptest describes how to add tests to an image, but leaves it open how one invokes ptest-runner. What you describe sounds like a mechanism built on top of that which automatically boots up a machine and captures the output of ptest-runner.
> 
> > Would be nice, if you get the DHCP based network configuration
> > fulfilling these requirements. An alternative approach is implemented
> > in systemd networkd. I guess it does not touch interfaces which are
> > already configured e.g. by kernel boot parameters. This could be done
> > in connman as well. It would allow you to run the productive image in
> > qemu.
> 
> There might be also other improvements. For example, I just booted a
> core-image-minimal with systemd as init with runqemu. eth0 is
> configured, but /etc/resolv.conf is missing, so ptests like the one for
> wget fail because www.google.com cannot be resolved.
> 
> This was without the DHCP server patches. My expectation is that
> bringing up eth0 with DHCP-supplied information about DNS servers would
> have created (or could be made to create) resolv.conf.
> 
> 


--------
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6356
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150217/9dd6040e/attachment-0002.html>


More information about the Openembedded-core mailing list