Unable to find root device. domU

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to find root device. domU

Ted Kaczmarek
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=322


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: Unable to find root device. domU

Nicholas Lee
On 10/13/05, Ted Kaczmarek <[hidden email]> wrote:
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=322

No good for me.  I can't even get one domU going.

Trying to revert back down the tree until I find a changeset that
works.  Taking time though to do recompile at each set.

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: Unable to find root device. domU

Nicholas Lee
On 10/13/05, Ted Kaczmarek <[hidden email]> wrote:
>
> Make sure that the domU's fstab does not use any /dev that exists on the
> dom0.

Unfortunately it seems that this doesn't work for me either.  sda is a
fusion (LSI1030) based hw RAID1 device.  There is no sdb devices.

nic@wuwei:~/sys/xen$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: LSILOGIC Model: 1030 IM       IM Rev: 1000
  Type:   Direct-Access                    ANSI SCSI revision: 02


nic@wuwei:/etc/xen$ sudo xm create breezy -c
Using config file "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 17:25:19 NZDT 2005
kernel direct mapping tables upto 10000000 @ 4be000-540000
Built 1 zonelists
Kernel command line:  root=/dev/sdb1 ro 4 lockd.udpport=32768
lockd.tcpport=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.674 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 252416k/262144k available (2117k kernel code, 9072k reserved,
660k data, 136k 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 ffff8800014d5f58
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.
Grant table initialized
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1129183325.777:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SGI XFS with ACLs, security attributes, large block/inode numbers, no
debug enabled
SGI XFS Quota Management subsystem
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 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
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)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sdb1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Still have the same issue with when reverting to 7309. I'll see if I
can find the spot it stops working.

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel