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/
Home Products Support Community News


[Xen-devel] Unable to find root device. domU??

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Unable to find root device. domU??
From: Nicholas Lee <emptysands@xxxxxxxxx>
Date: Thu, 13 Oct 2005 15:20:19 +1300
Delivery-date: Thu, 13 Oct 2005 02:17:42 +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=Up0FhkjZ1047FaSTB713JkaT4a3VJdoO5i+DyFMWe2FSanN9eQmHjWvZQ0aPYtblFPfEd+BHjInYwo1yDLVbCLWDIPsxZAd7KZu5CW0xpCDtQElpYviKABSLLh/1DWRCDsnD8YNk9mFQfBfJ/nabgOS6uNU0q3Vh8vHdvE8QEqk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo xm create breezy -c
Using config file "/etc/xen/breezy".
Started domain breezy
Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian
1:3.3.5-13)) #3 SMP Thu Oct 13 14:56:20 NZDT 2005
kernel direct mapping tables upto 10000000 @ 568000-5ea000
Built 1 zonelists
Kernel command line:  root=/dev/sda1 ro 4 lockd.udpport=32768
Unknown boot option `lockd.udpport=32768': ignoring
Unknown boot option `lockd.tcpport=32768': ignoring
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 2194.794 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 251904k/262144k available (2569k kernel code, 9752k reserved,
814k data, 160k init)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
Booting processor 1/1 rip ffffffff80100008 rsp ffff8800014f5f58
Initializing CPU#1
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
AMD Opteron(tm) Processor 248 stepping 01
Brought up 2 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: System does not support PCI
PCI: System does not support PCI
TC classifier action (bugs to netdev@xxxxxxxxxxxxxxx cc hadi@xxxxxxxxxx)
Grant table initialized
IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
SGI XFS with ACLs, security attributes, large block/inode numbers, no
debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
Failed to obtain physical IRQ 8
Real Time Clock Driver v1.12
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
WARNING: Failed to register Xen virtual console driver as 'tty1'
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda1" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

nic@wuwei:/usr/src/xen/xen-unstable.hg$ hg tip
changeset:   7353:29db5bded574

nic@wuwei:/etc/xen$ cat breezy
kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 256
name = "breezy"
vcpus = 2
vif = [ "mac=aa:00:00:88:02:40, bridge=xen-br0" ]
disk = [ 'phy:ww/breezy-fs,sda1,w', 'phy:ww/breezy-swap,sda2,w' ]

root = "/dev/sda1 ro"
extra = "4 lockd.udpport=32768 lockd.tcpport=32768"
restart = 'onreboot'

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo lvdisplay ww/breezy-fs
  --- Logical volume ---
  LV Name                /dev/ww/breezy-fs
  VG Name                ww

Can someone explain what I might be missing here.  Note I previously
got domU booting, but had problems with the net device. Now it looks
like the net device is initialising but the block device is having

Nicholas Lee
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Attachment: config
Description: Binary data

Xen-devel mailing list