[Xen-users] Re: is my initramdisk right? also getting 'Error opening /dev/console' error

[Jayesh Salvi <jayeshsalvi@xxxxxxxxx>]

Am I supposed to put the vmlinuz and initrd images in /boot of the root file system of domU? But I verified that putting them on domU's root or dom0's root doesn't make much difference.

However my /dev/hda9 which I use as my domU's root file system, was clean. When I manually create /dev directory on it, the error with /dev/console no longer appears. But it fails at a later point. Here is the trace:

......
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Creating root device
Mounting root filesystem
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Switching to new root
unmounting old /proc
unmounting old /sys
WARNING: can't access (null)
exec of init ((null)) failed!!!: 14
Kernel panic - not syncing: Attempted to kill init!

If 14 is the errno for exec sys call then, it stands for:
 14 EFAULT       +Bad address
ok! null is a bad address indeed. 
Any more ideas, which init function is this?

On 12/13/05, Jayesh Salvi <jayeshsalvi@xxxxxxxxx> wrote:

Looking at the error message again "ERROR opening /dev/console!!!!: 2"

I guess that 2 is the value of errno after open() fails on /dev/console. And I found in linux errno=2 stands for

  2 ENOENT       +No such file or directory

My xm file has this root line:
root = "/dev/hda9 ro"

Does that mean I am installing the root file system ReadOnly and hence it cannot open /dev/console?

LMK
Jayesh

On 12/13/05, Jayesh Salvi <jayeshsalvi@xxxxxxxxx> wrote:

Hello,

I am getting kernel panic while trying to xm create a domU.

Xen version 3.0
Linux kernel 2.6.12.6

Grub entry for dom0:
title Xen 3.0 / XenLinux 2.6
        kernel /boot/xen- 3.0.gz console=vga
        module /boot/vmlinuz-2.6-xen0 root=LABEL=/ ro console=tty0
        module /boot/initrd-2.6.12.6-xen0.img

For domU, my xm file contains:
kernel = "/boot/vmlinuz-2.6.12.6-xenU "

My root is an ext3 file system on /dev/hda9

I am not sure about the ramdisk. I created a ramdisk by first doing the depmod and then using the mkinitrd command as given in the README file. I use that initramdisk for dom0. Should I use another ramdisk for domU?

From README, the mkinitrd commands goes like:
# mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.12.6-xen.img 2.6.12.6-xen

Will it make a difference if I change the kernel-version 2.6.12.6-xen to 2.6.12.6-xenU ? The man page of mkinitrd doesn't tell much about the kernel-version.

I however created different ramdisks using different kernel versions. 2.6.12.6-xen, 2.6.12.6-xen0, 2.6.12.6-xenU. Each time I however get the following common error:

ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
unmounting old /proc
unmounting old /sys
WARNING: can't access (null)
exec of init ((null)) failed!!!: 14
Kernel panic - not syncing: Attempted to kill init!

With initrd image 2.6.12.6-xenU, I get the following complete trace:

[root@orion ~]# xm create -c mydomain vmid=1
Using config file "/etc/xen/mydomain".
Started domain MyDomain
Linux version 2.6.12.6-xenU (root@Machine) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #2 SMP Sat Dec 10 20:19:56 CST 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004000000 (usable)
0MB HIGHMEM available.
72MB LOWMEM available.
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  root=/dev/hda9 ro 4
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 1295.792 MHz processor.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
vmalloc area: c5000000-fb7fe000, maxmem 34000000
Memory: 59460k/73728k available (1817k kernel code, 5920k reserved, 478k data, 136k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 2166k freed
NET: Registered protocol family 16
Brought up 1 CPUs
xen_mem: Initialising balloon driver.
Grant table initialized

  ***************************************************************
  ***************************************************************
  ** WARNING: Currently emulating unsupported memory accesses  **
  **          in /lib/tls glibc libraries. The emulation is    **
  **          slow. To ensure full performance you should      **
  **          install a 'xen-friendly' (nosegneg) version of   **
  **          the library, or disable tls support by executing **
  **          the following as root:                           **
  **          mv /lib/tls /lib/tls.disabled                    **
  ** Offending process: hotplug (pid=23)                       **
  ***************************************************************
  ***************************************************************

Continuing...

Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
NET: Registered protocol family 2
Registering block device major 3
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 136k freed
Red Hat nash version 4.2.15 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Creating root device
Mounting root filesystem
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Switching to new root
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
unmounting old /proc
unmounting old /sys
WARNING: can't access (null)
exec of init ((null)) failed!!!: 14
Kernel panic - not syncing: Attempted to kill init!


I found a couple of references for the error 'ERROR opening /dev/console!!!!: 2', but they were not deterministically resolved ('yum update' solve the problem in one case - I am not using yum with xen). I also remember reading 'it might be a udev' problem. Not sure what it is.

Can anyone suggest any solution? And could you tell about which initramdisk should be used for domUs.

Thanks.
--
Jayesh

--
Jayesh

-- 
Jayesh

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