0002543: After yum update from 5.0 -> 5.1 xm create fails and xend crashes

CentOS Bug Tracker

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0002543

[CentOS-5] xen

crash

have not tried

2007-12-15 16:23

2008-02-06 11:46

Reporter

greggster

View Status

public

Assigned To

Priority

normal

Resolution

open

Status

new

Product Version

5.1

Summary

0002543: After yum update from 5.0 -> 5.1 xm create fails and xend crashes

Description

I was running 2 boxes identical hardware and software versions, etc.
CentOS 5.0 / Asus M2NPV-VM and while Dom0 and 2 DomU's were running did a yum update and got surprised by 200+ updates and installed them.

So for backup I stopped 2 DomU (16GB VBD) to make a backups. When trying to restart them with xm create I get...

NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Write protecting the kernel read-only data: 445k
USB Universal Host Controller Interface driver v3.0
XENBUS: Timeout connecting to device: device/vbd/51712 (state 3)
device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
Kernel panic - not syncing: Attempted to kill init!

So copy a VBD to Xen box#2, same thing

Box 2 - bring down a DomU to see if it was the DomU or the box - this one would not start either.

So xend - service xend restart looked ok but then:
[root@mocha vm]# service xend start
Starting xend: [ OK ]
[root@mocha vm]# xm list
Error: Unable to connect to xend: Connection refused. Is xend running?
[root@mocha vm]# xm list

So not sure what to do - tried many things - remove and install xen-related packages - for now stuck with non-working systems.

The second box is one that's always been yum updated/rpm and started with CentOS 5 - no upgrade, force, no-deps on this one - fresh install a few months ago.

Both boxes are:

[root sysconfig]# uname -a
Linux server0.somedomain.com 2.6.18-8.1.15.el5xen 0000001 SMP Mon Oct 22 09:01:12 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

Please advise.

Additional Information

[root@mocha vm]# xm create -c exodus
Using config file "/etc/xen/exodus".
Started domain exodus
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00)
Linux version 2.6.18-53.1.4.el5xen (mockbuild@builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) 0000001 SMP Fri Nov 30 01:21:23 EST 2007
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010200000 (usable)
No mptable found.
Built 1 zonelists. Total pages: 66048
Kernel command line: ro root=/dev/VolGroup00/LogVol00
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2204.592 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 238108k/264192k available (2357k kernel code, 17584k reserved, 1326k data, 172k init)
Calibrating delay using timer specific routine.. 5521.51 BogoMIPS (lpj=11043027)
Security Framework v1.0.0 initialized
SELinux: Initializing.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread DBC7A0 could not acquire Mutex [2] [20060707]
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread DBC7A0 could not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1197734494.843:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key BF23BF4D1917253
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Console: switching to colour frame buffer device 100x37
input: Xen Virtual Keyboard/Mouse as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
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
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Write protecting the kernel read-only data: 445k
USB Universal Host Controller Interface driver v3.0
XENBUS: Timeout connecting to device: device/vbd/51712 (state 3)
device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
Kernel panic - not syncing: Attempted to kill init!

Notes
(0006566) kaboom (reporter) 2007-12-17 19:05	I had the same issue If you look in your config file and change from the tap:aio to file: access method for your disk image, it should fix it

(0006824) nickyp (reporter) 2008-02-06 11:46	See issue 0002083 (xenU kernel RPM missing --with=xenblk for mkinitrd) for the cause. http://bugs.centos.org/view.php?id=2083 [^] Change tap:io into file: in your xen configs and boot the domU. remove or copy /boot/initrd-2.6.18-53.1.6.el5xen.img and run the following mkinitrd command: mkinitrd -v --with=xenblk --omit-scsi-modules --omit-raid-modules /boot/initrd-2.6.18-53.1.6.el5xen.img 2.6.18-53.1.6.el5xen

Issue History
Date Modified	Username	Field	Change
2007-12-15 16:23	greggster	New Issue
2007-12-15 16:23	greggster	Assigned To	=> kbsingh@karan.org
2007-12-17 19:05	kaboom	Note Added: 0006566
2008-02-06 11:46	nickyp	Note Added: 0006824

Relationships