Bug#582021: linux-image-2.6.32-bpo.4-xen-amd64 misses networking booting domUs installed via xen-tools

[Ian Campbell <ijc@hellion.org.uk>]

On Thu, 2010-11-18 at 09:56 +0200, Timo Juhani Lindfors wrote:
> Hi,
> 
> it would be useful to know:

In addition it would be very useful to try a much newer kernel. There
have been many changes to the pvops kernel patches between 2.6.32-11 and
now including a bunch of net{front,back} changes which may be related to
this problem.

Please can you also clarify which kernel is in use in domain 0 vs.
domain U.

Thanks,
Ian.

> 
> sudo brctl show
> sudo xm info
> sudo xm list
> lsmod
> dpkg-query -W linux-image-$(uname -r)
> 
> on dom0 when you have no networking and
> 
> sudo ip link
> lsmod
> dpkg-query -W linux-image-$(uname -r)
> 
> on domU when you have no networking.
> 
> With squeeze dom0 and domU on amd64 at least
> 
> cat > config <<EOF
> name = 'squeeze64'
> 
> bootloader = '/usr/bin/pygrub'
> 
> vcpus = '4'
> memory = '512'
> 
> disk = [ 'file:/local/xen/squeeze64/disk.img,xvda,w' ]
> vif = [ 'mac=00:01:01:99:7e:eb' ]
> EOF
> sudo xm create -c config
> 
> has networking.
> 
> 
> 
> 

-- 
Ian Campbell
Current Noise: Angelcorpse - Embrace

Take me drunk, I'm home again!