[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Re: Xen-users Digest, Vol 8, Issue 61
- To: xen-users@xxxxxxxxxxxxxxxxxxx
- From: Sweekar Pinto <sweekarpinto@xxxxxxxxx>
- Date: Tue, 18 Oct 2005 10:22:40 +0530
- Cc: chapeaurouge@xxxxxxxxx
- Delivery-date: Tue, 18 Oct 2005 04:50:00 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=XoVpFuq89tVfdQ2lUuoF2U9zlk4dWyRMZ4GXzXxJ1EWJJhOd3AKL00hf7KqiJiBRwHTflrN2ti+spJ3ApSH8bChNLXuHESQy7JMRloJ/A3+sud0E/aLv6Ryp5SI0nYP2JI+t1AeqEgE2LnLdJKJeoDP+3wiSrhaGgLzRQLph5rQ=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Hi,
I'm not sure about this but shouldn't root be /dev/md0?
-Sweekar
Message: 7 Date: Mon, 17 Oct 2005 18:30:03 +0200 From: Fred Blaise <
chapeaurouge@xxxxxxxxx> Subject: [Xen-users] Xen3, domainU: kernel panic To: xen-users@xxxxxxxxxxxxxxxxxxx Message-ID: <
9cfa15020510170930i601801cbxb3749640943485e8@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1
Hello all
I am trying to launch:
kernel = "/boot/vmlinuz-2.6.12-xenU" memory = 512
name = "oes1" disk = [ 'phy:vgdata/lv_xen_oes1,md0,w' ] dhcp="dhcp" root = "/dev/md3 ro" extra = "4"
End result is: bicolor:~/hg-xen-unstable/xen-unstable.hg
# xm list Name ID Mem(MiB) CPU VCPUs State
Time(s) Domain-0
0
251 0 1 r----- 553.2 Zombie-oes1 1
0 1 1 ----cd 0.4 oes1 54
503 1 1 r----- 1.9
I get:
bicolor:/etc/xen # xm create oes1 -c Using config file "oes1". Started domain oes1 Linux version 2.6.12-xenU (root@bicolor) (gcc version 3.3.3 (SuSE
Linux)) #1 SMP Mon Oct 17 18:14:07 CEST 2005 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020000000 (usable) 0MB HIGHMEM available. 512MB LOWMEM available. IRQ lockup detection disabled
Built 1 zonelists Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/md3 ro 4 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 3065.790 MHz processor. Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) vmalloc area: e0800000-fb7fe000, maxmem 34000000 Memory: 514944k/524288k available (1911k kernel code, 9124k reserved, 584k data, 152k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok. Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... disabled CPU0: Intel(R) Xeon(TM) CPU 3.06GHz stepping 09 Total of 1 processors activated (6121.06 BogoMIPS). Brought up 1 CPUs
NET: Registered protocol family 16 xen_mem: Initialising balloon driver. Grant table initialized 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. xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver. md: linear personality registered as nr 1 md: raid0 personality registered as nr 2 md: raid1 personality registered as nr 3 md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse pIII_sse : 2389.200 MB/sec raid5: using function: pIII_sse (2389.200 MB/sec) md: multipath personality registered as nr 7 md: faulty personality registered as nr 10
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@xxxxxxxxxx NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 32Kbytes
TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 7, 786432 bytes) TCP: Hash tables configured (established 131072 bind 65536) NET: Registered protocol family 1
NET: Registered protocol family 17 IP-Config: Incomplete network configuration information. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "md3" 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)
While I can shutdown 'oes1', I cannot make Zombie-oes1 go away, even with xm destroy. A reboot makes it go away.
As you can see above, raid modules are loaded. What am I missing? which device is unknown-block(2,0) ?
Thanks for the help.
fred
------------------------------
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
End of Xen-users Digest, Vol 8, Issue 61 ****************************************
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|