[Pkg-xen-devel] Problems with amd64 hypervisor and i386 dom0 (Was: Re: i386 hypervisor seeing only ~16G RAM, amd64 required?)

[Andy Smith]

Hi Bastian,

Thanks for your help.

On Thu, Jan 15, 2009 at 09:26:20AM +0100, Bastian Blank wrote:
> On Thu, Jan 15, 2009 at 12:46:43AM +0000, Andy Smith wrote:
> > I have several machines using xen-hypervisor-3.2-1-i386 from
> > etch-backports
> 
> This version is not supported by anyone. Use the version from Lenny.

On a spare dom0 that is currently Etch/i386, I installed:

http://packages.debian.org/lenny/xen-hypervisor-3.2-1-amd64
http://packages.debian.org/lenny/linux-image-2.6.26-1-xen-686
http://packages.debian.org/lenny/linux-modules-2.6.26-1-xen-686

When I boot the amd64 hypervisor with the Lenny kernel, the dom0 boots
as far as mounting the root filesystem, but then no further output
is displayed on console:

[   14.509793] device-mapper: uevent: version 1.0.3
[   14.509793] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel at redhat.com
[   14.614850] kjournald starting.  Commit interval 5 seconds
[   14.615097] EXT3-fs: mounted filesystem with ordered data mode.
[   15.721768] Adding 979924k swap on /dev/sda1.  Priority:-1 extents:1 across:979924k
[   15.863945] EXT3 FS on sda3, internal journal

I know there have possibly been some console changes between Etch
and Lenny, though I can't find any details on that which relate to
dom0 (as opposed to domU).  Also if that were the case I would
expect it to eventually complete the boot sequence and be
accessible via network, but this doesn't seem to happen.

I then tried rebooting into the amd64 hypervisor with the Etch i386
kernel, and that on the surface appears to work.

Here's what my grub entry looks like for the amd64 hypervisor /
Lenny kernel combo:

title           Xen 3.2-1-amd64 / Debian GNU/Linux, kernel 2.6.26-1-xen-686
root            (hd0,1)
kernel          /xen-3.2-1-amd64.gz com1=9600,8n1 console=com1,vga dom0_mem=1024M
module          /vmlinuz-2.6.26-1-xen-686 root=UUID=1f838bea-0d4a-45d4-a4b9-af79f865faeb ro console=ttyS0,9600n8 console=tty0
module          /initrd.img-2.6.26-1-xen-686

Maybe it's just something simple I am missing.

On the other hand, I realise that 32bit Etch userland with Lenny Xen
dom0 kernel and Lenny amd64 hypervisor is a bit of an unusual
configuration.  I would really like to avoid reinstalling the dom0
userland of existing servers if I can get away with it though.  If
what I'm trying to do is unsupported I suppose I have to upgrade the
dom0s to Lenny.

Any thoughts?

Cheers,
Andy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20090121/d215ce09/attachment.pgp