On Fri, Mar 13, 2015 at 12:58:52PM -0400, Lee Revell wrote: > On 03/13/2015 12:21 PM, Richard W.M. Jones wrote: > >So what's happening is that /etc/resolv.conf in the appliance never > >gets created. > > > > Is the /dev/tcp test by IP evidence that the problem goes deeper > than name resolution? > > >Run `./run virt-rescue --network --scratch' on the Ubuntu host and see if: > > > > - either dhclient or dhcpcd exists in the appliance > > > > - they work when you run them, or if there is an error message > > > > - if running one of them creates /etc/resolv.conf > > > > ><rescue> which dhclient > /sbin/dhclient > ><rescue> /sbin/dhclient > ><rescue> ls /etc/resolv.conf > ls: cannot access /etc/resolv.conf: No such file or directory
I wonder why dhclient doesn't create /etc/resolv.conf . > ><rescue> which dhcpcd > ><rescue> > > Would there be any point in testing latest code from git? I think you were testing 1.29.29, which is only a few days old. There haven't been any changes to the appliance. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
