[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] cannot boot domU


  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Stephan Böni <boeni@xxxxxx>
  • Date: Sun, 16 Oct 2005 16:38:30 +0200
  • Delivery-date: Sun, 16 Oct 2005 14:35:50 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXSX0bceuMVuAp6SduzWepP3QiqXg==
  • Thread-topic: cannot boot domU

I cannot boot domU:
 
# xm create inhouse
Using config file "inhouse".
Started domain inhouse
# xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       123    0      1  r-----     27.4
inhouse            8      2048    0      1  ------     11.4
# xm console inhouse
Linux version 2.6.12.6-xenU (root@xen1) (gcc version 4.0.2 20050901 (prerelease)
 (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005
kernel direct mapping tables upto 80000000 @ 7ba000-bbd000
Built 1 zonelists
Kernel command line:  root=/dev/sda1 3
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 3200.108 MHz processor.
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 2050304k/2097152k available (1682k kernel code, 46344k reserved, 561k da
ta, 136k init)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Hyper-Threading is disabled
Brought up 1 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(1129473172.510:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
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 8192 buckets, 128Kbytes
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
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 "sda1" 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)
#
cat inhouse | grep -v ^#
kernel = "/boot/vmlinuz-2.6.12.6-xenU"
memory = 2048
name = "inhouse"
disk = [ 'phy:xenvg/inhouse-root,sda1,w' ]
root = "/dev/sda1"
extra = "3"
 
Does anyone know what the problem is?
 
Stephan
 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.