WARNING - OLD ARCHIVES

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

xen-users

[Xen-users] Help! Kernel Panic on DomU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Help! Kernel Panic on DomU
From: W <jazzbearz@xxxxxxxxx>
Date: Sun, 17 Jan 2010 10:14:15 +0900
Delivery-date: Sat, 16 Jan 2010 17:14:59 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=X7go3CI16VkIEoyH3WIZWNsCBgD5a+cj3biB5Lo4p44=; b=qM1LFKHypKYlRvhFBBNtcOAYZD6sKZWSVGfs6ssiroWYag+3QKD1FSILoGpHJGphl2 FmNzZzAAwvGLIWbYbayF84iZeQ5SX2QogMhV4HhU/j2iAxdmjnh9dNBj4aJoWl4nM7zC YAun7nr3AP82WT450pZs4Khr/bK5cTx2uE+bw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=f7JIvFpWzeVQ8BMGE480pt7vIZWGxD3E4OVgamZ86GlP9eMww6aWPBmQ9gp02aqVg6 t/sqOge75trq0+RhyOCU1HkIjhZQg196Uvu+qxl5KLubkfAoJHShIFSzRQkwZzR7Il/R diKMtHT3ThGS3r/OD5PAUAe8wwUd7wQjDw3hw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <91bee2201001161536y27c29298r1f044dc31f3bc58b@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <91bee2201001161536y27c29298r1f044dc31f3bc58b@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Previous mail was sent with wrong address, I'm resending this.
To add, I couldn't find any logs on mounted drives, e2fsck with clean results.
Just xend logs show:

[2010-01-17 01:08:30 4302] INFO (XendDomain:1182) Domain push.vm (13) unpaused.
[2010-01-17 01:08:52 4302] WARNING (XendDomainInfo:1886) Domain has
crashed: name=push.vm id=13.
[2010-01-17 01:08:52 4302] ERROR (XendDomainInfo:2020) VM push.vm
restarting too fast (Elapsed time: 21.823400 seconds). Refusing to
restart to avoid loops.
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2732)
XendDomainInfo.destroy: domid=13
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2207) Destroying device model
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2214) Releasing devices
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2227) Removing vif/0
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2227) Removing vbd/2049
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2227) Removing vbd/2050
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2227) Removing console/0
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device =
console/0
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2212) No device model
[2010-01-17 01:08:52 4302] DEBUG (XendDomainInfo:2214) Releasing devices

I was running regular update on domUs and dom0 using centos 5.4 with
custom compiled 3.4.1 kernel.
the updated changed my boot.lst to centos's default kernel, so I
changed it back.

after I reboot the system, it had problems with acm-policy file.  So,
I recompiled the kernel with 3.4.2, then set the boot directory,
modified sysconfig/xendomains to shutdown not migrate and finally
rebooted.
then, now xen seems running fine.  however, the domUs are shutting
down with kernel panic messages.

this is running server and I'm panicked as well.  Any help is appreciated.

Here's the console message

Linux version 2.6.18.8-xen (root@#####.com) (gcc version 4.1.2
20080704 (Red Hat 4.1.2-46)) #1 SMP Sat Jan 16 21:30:23 EST 2010
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000080800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 519140
Kernel command line: root=/dev/sda1 ro
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2673.298 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Software IO TLB disabled
Memory: 2046208k/2105344k available (2047k kernel code, 50636k
reserved, 895k data, 180k init)
Calibrating delay using timer specific routine.. 5347.83 BogoMIPS (lpj=26739174)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 8192K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
SMP alternatives: switching to UP code
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 6320k freed
NET: Registered protocol family 16
SMP alternatives: switching to SMP code
Initializing CPU#1
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 8192K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
migration_cost=29
migration_cost=29
Initializing CPU#2
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 8192K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
migration_cost=29
Initializing CPU#3
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 8192K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
migration_cost=Initializing CPU#4
29
Brought up 5 CPUs
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 256K
CPU: L3 cache: 8192K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
PCI: Fatal: No config space access function found
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
suspend: event channel 18
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
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)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@xxxxxxxxxxx>
audit: initializing netlink socket (disabled)
audit(1263701549.207:1): 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 (default)
Non-volatile memory driver v1.2
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
blktap_device_init: blktap device major 254
blktap_ring_init: blktap ring major: 253
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
PCI IO multiplexer device installed.
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
blkfront: sda2: barriers enabled
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
Freeing unused kernel memory: 180k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
3ware 9000 Storage Controller device driver for Linux v2.26.02.007.
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic - not syncing: Attempted to kill init!

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>