[Xen-users] How to boot Ubuntu 9.04(Jaunty) or Debian Lenny (vmlinuz-2.6.26-2-686-bigmem) as domU under Lenny's vmlinuz-2.6.26-2-xen-686 as dom0. PVM's initrd issue

["Alexandr R. Ogurtzoff" <iscander@xxxxxxxxx>]

Hello, I guess it possible distro specific issue but is it resolvable?

I have one node(testing purpose) ganeti 2.0.1 cluster installed over
Debian5 Lenny. Almost everything from distro repositories. Only ganeti
2.0.1 and ganeti-debootstrap are from sources.  I have it successful
run with  vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686
from repositories. Both Dom0 and DomU are use the same kernel and
initrd. There are symlinks /boot/initrd-2.6-xenU and
/boot/vmlinuz-2.6-xenU pointing to the vmlinuz-2.6.26-2-xen-686 and
initrd.img-2.6.26-2-xen-686. My instance(PVM) run well with following
config generated by ganeti :
 node:/boot# cat /etc/xen/app.cluster.xen
# this is autogenerated by Ganeti, please do not edit
#
kernel = '/boot/vmlinuz-2.6-xenU'
ramdisk = '/boot/initrd-2.6-xenU'
memory = 128
vcpus = 1
name = 'app.cluster.xen'
vif = ['mac=aa:00:00:f4:c1:aa, bridge=br0']
disk = ['phy:/var/run/ganeti/instance-disks/app.cluster.xen:0,sda,w']
root = '/dev/sda1'
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = 'clocksource=jiffies'

Then I try to use Ubuntu 9.0.4 (Jaunty) kernel or even Debian's
vmlinuz-2.6.26-2-686-bigmem kernel to boot the instance. I got an
error.
Actually I setup them from repositories and change the symlinks:
  node:/boot# ls -l /boot/*xenU
lrwxrwxrwx 1 root root 30 Июн 22 16:25 /boot/initrd-2.6-xenU ->
initrd.img-2.6.26-2-686-bigmem
lrwxrwxrwx 1 root root 27 Июн 22 16:25 /boot/vmlinuz-2.6-xenU ->
vmlinuz-2.6.26-2-686-bigmem

So in this case, my instance bootup stops with following:

node:/boot# gnt-instance startup app (xm create app)
node:/boot# gnt-instance console app (xm console app)
c0] enabled
[    0.004000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.004000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.004000] Memory: 109308k/131072k available (1834k kernel code,
21348k reserved, 788k data, 256k init, 0k highmem)
[    0.004000] virtual kernel memory layout:
[    0.004000]     fixmap  : 0xf5611000 - 0xf57fd000   (1968 kB)
[    0.004000]     pkmap   : 0xf5200000 - 0xf5400000   (2048 kB)
[    0.004000]     vmalloc : 0xc8800000 - 0xf51fe000   ( 713 MB)
[    0.004000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.004000]       .init : 0xc0397000 - 0xc03d7000   ( 256 kB)
[    0.004000]       .data : 0xc02caabb - 0xc038fac0   ( 788 kB)
[    0.004000]       .text : 0xc0100000 - 0xc02caabb   (1834 kB)
[    0.004000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[    0.004000] installing Xen timer for CPU 0
[    0.080011] Calibrating delay using timer specific routine..
4166.22 BogoMIPS (lpj=8332443)
[    0.080146] Security Framework initialized
[    0.080169] SELinux:  Disabled at boot.
[    0.080188] Capability LSM initialized
[    0.080228] Mount-cache hash table entries: 512
[    0.080489] Initializing cgroup subsys ns
[    0.080510] Initializing cgroup subsys cpuacct
[    0.080532] Initializing cgroup subsys devices
[    0.080584] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[    0.080597] CPU: L2 Cache: 256K (64 bytes/line)
[    0.080950] SMP alternatives: switching to UP code
[    0.125151] Freeing SMP alternatives: 16k freed
[    0.125413] Brought up 1 CPUs
[    0.125818] net_namespace: 660 bytes
[    0.125832] Booting paravirtualized kernel on Xen
[    0.125840] Hypervisor signature: xen-3.0-x86_32p
[    0.126045] Grant table initialized
[    0.126118] NET: Registered protocol family 16
[    0.128514] PCI: Fatal: No config space access function found
[    0.128539] Setting up standard PCI resources
[    0.129993] ACPI: Interpreter disabled.
[    0.130011] Linux Plug and Play Support v0.97 (c) Adam Belay
[    0.130085] pnp: PnP ACPI: disabled
[    0.130094] PnPBIOS: Disabled
[    0.130221] xen_balloon: Initialising balloon driver.
[    0.207205] PCI: System does not support PCI
[    0.207228] PCI: System does not support PCI
[    0.208384] NET: Registered protocol family 2
[    0.208602] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.208864] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.208922] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.208976] TCP: Hash tables configured (established 4096 bind 4096)
[    0.208986] TCP reno registered
[    0.209099] NET: Registered protocol family 1
[    0.209291] checking if image is initramfs... it is
[    0.285431] Freeing initrd memory: 16368k freed
[    0.285960] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[    0.286811] audit: initializing netlink socket (disabled)
[    0.286865] type=2000 audit(1245677178.749:1): initialized
[    0.287064] Total HugeTLB memory allocated, 0
[    0.288050] VFS: Disk quotas dquot_6.5.1
[    0.288105] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.288179] msgmni has been set to 287
[    0.288369] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 253)
[    0.288383] io scheduler noop registered
[    0.288391] io scheduler anticipatory registered
[    0.288399] io scheduler deadline registered
[    0.288416] io scheduler cfq registered (default)
[    0.288971] isapnp: Write Data Register 0xa79 already used
[    0.294526] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports,
IRQ sharing enabled
[    0.297804] brd: module loaded
[    0.298074] PNP: No PS/2 controller found. Probing ports directly.
[    0.298863] i8042.c: No controller found.
[    0.299049] mice: PS/2 mouse device common for all mice
[    0.299299] rtc_cmos: probe of rtc_cmos failed with error -16
[    0.299487] cpuidle: using governor ladder
[    0.299496] cpuidle: using governor menu
[    0.299508] No iBFT detected.
[    0.300347] TCP cubic registered
[    0.300358] NET: Registered protocol family 17
[    0.300372] Using IPI No-Shortcut mode
[    0.301594] registered taskstats version 1
[    0.301629] XENBUS: Device with no driver: device/vbd/2048
[    0.301637] XENBUS: Device with no driver: device/vif/0
[    0.301646] XENBUS: Device with no driver: device/console/0
[    0.301676] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    0.302004] Freeing unused kernel memory: 256k freed
Loading, please wait...
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... FATAL: Error inserting fan
(/lib/modules/2.6.26-2-686-bigmem/kernel/drivers/acpi/fan.ko): No such
device
WARNING: Error inserting processor
(/lib/modules/2.6.26-2-686-bigmem/kernel/drivers/acpi/processor.ko):
No such device
[    0.482693] thermal: Unknown symbol acpi_processor_set_thermal_limit
FATAL: Error inserting thermal
(/lib/modules/2.6.26-2-686-bigmem/kernel/drivers/acpi/thermal.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
[    0.952603] blkfront: xvda: barriers enabled
[    0.952796]  xvda: xvda1
done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top
... [    1.165261] device-mapper: uevent: version 1.0.3
[    1.167396] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18)
initialised: dm-devel@xxxxxxxxxx
done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda1 does not exist. Dropping to a shell!


BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

It seems something miss in a initrd. How can I fix it? Should I
rebuild 'default' initrd - which way? Or add something to grub
configuration? Or what do I do wrong? Everything I want for now is to
boot instance with another kernel, and this is not handmade kernel but
kernel from distro repositories what officially noted as suporting
DomU:
  http://packages.debian.org/ru/squeeze/linux-image-2.6.26-2-vserver-686-bigmem
it is noted as:
"This kernel also runs on a Xen hypervisor. It supports only
unpriviledged (domU) operation."
  Xen is 3.2.1
for Jaunty I tried vmlinuz-2.6.28-11-server

Thank You in advance
-- 
My best wishes.
Alexandr Ogurtsov.

Linux is very friendly it is just picky who its friends are

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