Libguestfs - Mar 2015 - Re: Name resolution not working inside virt-customize

On 03/13/2015 01:29 PM, Richard W.M. Jones wrote:
>
> I wonder why dhclient doesn't create /etc/resolv.conf .
>
FWIW, I've also found that on the fedora 21 host, supermin passes all 8 
"make check" tests. On the Ubuntu 14.04 host, it fails 2 of 8. The log
is attached.

Additionally there are other weird differences, like /etc/passwd and 
/etc/shadow and many other /etc files present in the working appliance 
are missing on the non-working one.

Lee

On Fri, Mar 13, 2015 at 04:59:32PM -0400, Lee Revell
wrote:
> On 03/13/2015 01:29 PM, Richard W.M. Jones wrote:
> >
> >I wonder why dhclient doesn't create /etc/resolv.conf .
> >
> 
> FWIW, I've also found that on the fedora 21 host, supermin passes
> all 8 "make check" tests. On the Ubuntu 14.04 host, it fails 2 of
8.
> The log is attached.
The failures almost certainly have nothing to do with the problem at
hand.  They seem to happen because you don't have 'augeas-tools'
installed which is required for the test suite.
> Additionally there are other weird differences, like /etc/passwd and
> /etc/shadow and many other /etc files present in the working
> appliance are missing on the non-working one.
"working" == Fedora?  I wouldn't pay too much attention to these
differences.

I went back and had a look at the guestfish-network-test*.log files
that you sent previously, and there is one major problem:
virtio_net.ko doesn't exist on your host (or it does exist, but
supermin isn't picking it up for the appliance, but this unlikely).

This explains why the network doesn't work and why dhclient doesn't
work too.  I don't know why virtio-net isn't used -- perhaps it
isn't
compiled into your host kernel.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html

On 03/16/2015 08:13 AM, Richard W.M. Jones wrote:
> I went back and had a look at the guestfish-network-test*.log files
> that you sent previously, and there is one major problem:
> virtio_net.ko doesn't exist on your host (or it does exist, but
> supermin isn't picking it up for the appliance, but this unlikely).
>
> This explains why the network doesn't work and why dhclient doesn't
> work too.  I don't know why virtio-net isn't used -- perhaps it
isn't
> compiled into your host kernel.
Ok, I'll look into this. What's strange is that I have a virtualized 
Openstack environment on the same host using multiple virtual networks 
and that all works perfectly.

Lee

[Please keep replies on the list]

On Mon, Mar 16, 2015 at 09:28:28AM -0400, Lee Revell
wrote:
> On 03/16/2015 09:14 AM, Lee Revell wrote:
> >>This explains why the network doesn't work and why dhclient
doesn't
> >>work too.  I don't know why virtio-net isn't used --
perhaps it isn't
> >>compiled into your host kernel.
> >
> 
> leer@eng-leer:~$ grep VIRTIO_NET /boot/config-3.16.0-31-generic
> CONFIG_VIRTIO_NET=y
If you look at the logs you provided, ethX isn't appearing in the
guest, so something is wrong.

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

On 03/16/2015 09:45 AM, Richard W.M. Jones wrote:
>
> If you look at the logs you provided, ethX isn't appearing in the
> guest, so something is wrong.
>
Thanks, I ended up just switching to a Fedora 21 build host.

Lee