<div dir="ltr"><div class="gmail_extra">Hi Patrick,</div><div class="gmail_extra"><br><div class="gmail_quote">On 4 November 2014 08:09, Patrick Ohly <span dir="ltr"><<a href="mailto:patrick.ohly@intel.com" target="_blank">patrick.ohly@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":we" class="a3s" style="overflow:hidden">Recently I built a custom image which depended on a DHCP server to<br>
configure Ethernet. runqemu with tap for networking doesn't provide one<br>
at the moment, so ssh logins did not work.<br>
<br>
Instead of customizing images for runqemu, I think it would be better to<br>
adapt runqemu and uses images as on the target device. Attached two<br>
patches which work for me. Is that of interest for inclusion upstream?<br></div></blockquote><div><br></div><div>I've long been of the opinion that runqemu needs the ability to setup a DHCP/DNS server for the guest, as whilst you can special-case qemu machines and hard-code the relevant network configuration it doesn't help with testing. That said, I'm not convinced that dhcpd+bind is the right way forward, something like dnsmasq (currently in meta-networking) might be quicker to build and more flexible in this environment.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":we" class="a3s" style="overflow:hidden">
I suppose more work is needed, in particular around how to enable or<br>
disable this feature. Patching the .bb files also leads to a (to me)<br>
strange QA error. See the comments in the patches for details.</div></blockquote></div><br>This is likely due to bind using PACKAGES_prepend instead of PACKAGES =+ (=+ is prepend), which messes up the native.bbclass magic.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>