Re: [Xen-users] 32bit kernel under amd64

[SZABO Zsolt <szazs@xxxxxxxxx>]

On Sat, 14 Feb 2009, SZABO Zsolt wrote:

> I have an xen-3.2.1 source under amd64 arch:
> # uname -a
> Linux xenserver 2.6.18.8-xen #1 SMP Thu Jul 31 23:51:53 CEST 2008 x86_64 
> GNU/Linux
> I would like to compile a 32bit kernel for my domU, so I did the following:
>
> # cd xen-3.2.1
> # make XEN_TARGET_ARCH=x86_32 linux-2.6-xenU-prep
> # cd build-linux-2.6.18-xenU_x86_32
> # make ARCH=i386 menuconfig
> # make ARCH=i386
> # make ARCH=i386 install modules_install
> # mkinitramfs -o /boot/initrd.img-2.6.18.8-xenU 2.6.18.8-xenU
>
> Then here is my domU.conf:
>
> kernel="/boot/vmlinuz-2.6.18.8-xenU"
> ramdisk = "/boot/initrd.img-2.6.18.8-xenU"
[...]
> However when creating the domU in the xm console I see:
>
> [...]
> XENBUS: Device with no driver: device/console/0
> Freeing unused kernel memory: 196k freed
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
>
> [and it hangs here]
Now, I booted the domU with the older 32bit kernel, and I have issued

# mkinitramfs -o /boot/initrd.img-2.6.18.8-xenU 2.6.18.8-xenU

in the domU. Then shutdown the domU copy the initrd.img to dom0-s /boot,
and trying again. Now, it boots, however I get no console prompt using
xm console domU... I just see the kernel messages of the domU.

[...]
ReiserFS: sdb1: found reiserfs format "3.6" with standard journal
ReiserFS: sdb1: using ordered data mode
ReiserFS: sdb1: journal params: device sdb1, size 8192, journal first 
block 18, max trans len 1024, max batch 900, max commit age 30, max trans 
age 30
ReiserFS: sdb1: checking transaction log (sdb1)
ReiserFS: sdb1: Using r5 hash to sort names
fuse init (API version 7.7)
process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
[nothing else, no login prompt, no output from init.d, etc.]

I can ssh to the domU and it seems that every other things are working.
# uname -a
Linux linserver 2.6.18.8-xenU #2 SMP Sat Feb 14 15:44:35 CET 2009 i686 GNU/Linux

--
Zsolt

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users