|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 105] New: domU kernel panic when starting domU
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=105
Summary: domU kernel panic when starting domU
Product: Xen
Version: unstable
Platform: Other
OS/Version: Linux-2.6
Status: NEW
Severity: normal
Priority: P2
Component: Hypervisor
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: lge@xxxxxxxxxx
CC: hohnbaum@xxxxxxxxxx
I have seen kernel panic when starting domU, but dom0 is still functional.
Here is the output:
Linux version 2.6.12-xenU (root@bl2-2) (gcc version 3.3.3 (SuSE Linux)) #1 Fri
Jul 15 05:10:47 CDT 2005
kernel direct mapping tables upto ffff880016400000 @ 800000-8b4000
Registering memory for bootmem: from a00000, size = 15a00000
Allocating PCI resources starting at 16400000 (gap: 16400000:e9c00000)
Built 1 zonelists
Kernel command line: root=/dev/sdb7 ro
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 3600.289 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 348160k/364544k available (1376k kernel code, 5848k reserved, 492k data,
92k init)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Intel(R) Xeon(TM) CPU 3.60GHz stepping 01
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(1121430280.260:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
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.
Blkif frontend is using grant tables.
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 4096 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 5, 131072 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.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,23)
I am still investigating. Will add more information later.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-bugs] [Bug 105] New: domU kernel panic when starting domU,
lge <=
|
|
|
|
|