WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] is my initramdisk right? also getting 'Error opening /dev/co

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] is my initramdisk right? also getting 'Error opening /dev/console' error
From: Jayesh Salvi <jayeshsalvi@xxxxxxxxx>
Date: Wed, 14 Dec 2005 00:47:35 +1800
Delivery-date: Tue, 13 Dec 2005 06:49:17 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=CYKrRiNL8To9qolOqm106NcWBk9Olx2KcD6raDKtU7KF4jfAL9oBA4fw7ju5hD1ToQDrEp2P30CbCicsQXPX0QVwmdMEHxB25eo450B9pYBMCCpVUh0ualHqBZWe1/haIK1NPl2oQorj4QA87gtXikTMytL7/WIvW+fVNzmVS0s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>