Hi! I have a strange problem with Xen VMs in SLES11 SP2 that looks like two VMs on a host are fine, while a third VM causes trouble (that the Xen RA does not detect):
All VMs have the same structure: 512-1024MB RAM, 2 CPUs, 1 disk via tap:aio on OCFS2, 1 CD-ROM also via tap:aio on OCFS2, 4 NICs In the recent past I saw the third VM on a hast having trouble with the (virtual) CD-ROM (which is the second of the two disks). Yesterday I discoved this problem with all the current updates (kernel 3.0.42-0.7-xen) being applied: [...] [ 0.236715] registered taskstats version 1 [ 0.236740] Magic number: 1:252:3141 [ 0.236755] XENBUS: Device with no driver: device/vbd/51712 [ 0.236758] XENBUS: Device with no driver: device/vbd/51728 [ 0.236762] XENBUS: Device with no driver: device/vif/0 [ 0.236766] XENBUS: Device with no driver: device/vif/1 [ 0.236769] XENBUS: Device with no driver: device/vif/2 [ 0.236772] XENBUS: Device with no driver: device/vif/3 [ 0.236971] Freeing unused kernel memory: 424k freed [ 0.237257] Write protecting the kernel read-only data: 6856k doing fast boot [ 5.440077] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s... [...] The VM would not be able to boot due to lack of a boot disk. All three VMs on a specific node had the very same problem after being rebooted (through OS, not Xen RA). Interestingly, when restarting the VM through the Xen RA (on another node), the VMs bootet without problem as before: [...] [ 0.240411] Registering the dns_resolver key type [ 0.240504] registered taskstats version 1 [ 0.240531] Magic number: 1:252:3141 [ 0.240546] XENBUS: Device with no driver: device/vbd/51712 [ 0.240550] XENBUS: Device with no driver: device/vbd/51728 [ 0.240554] XENBUS: Device with no driver: device/vif/0 [ 0.240557] XENBUS: Device with no driver: device/vif/1 [ 0.240561] XENBUS: Device with no driver: device/vif/2 [ 0.240564] XENBUS: Device with no driver: device/vif/3 [ 0.240773] Freeing unused kernel memory: 424k freed [ 0.241015] Write protecting the kernel read-only data: 6856k doing fast boot [ 0.354810] xen-vbd: registered block device major 202 [ 0.354856] blkfront: xvda: barrier: enabled [ 0.377958] xvda: unknown partition table [ 0.378260] Setting capacity to 6564928 [ 0.378266] xvda: detected capacity change from 0 to 3361243136 [ 0.378882] blkfront: xvdb: barrier: enabled [ 0.380274] xvdb: xvdb1 xvdb2 [ 0.380815] Setting capacity to 16777216 [ 0.380823] xvdb: detected capacity change from 0 to 8589934592 [ 0.461618] netfront: Initialising virtual ethernet driver. [ 0.588629] SCSI subsystem initialized [ 0.589338] emc: device handler registered [ 0.601508] hp_sw: device handler registered [ 0.613676] alua: device handler registered [ 0.625868] rdac: device handler registered Creating device nodes with udev [ 0.631636] udev: starting version 147 mount: devpts already mounted or /dev/pts busy mount: according to mtab, devpts is already mounted on /dev/pts Boot logging started on /dev/tty1(/dev/console) at Wed Oct 24 13:26:11 2012 Trying manual resume from /dev/xvdb1 Trying manual resume from /dev/xvdb1 Waiting for device /dev/xvdb2 to appear: ok fsck from util-linux 2.19.1 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/xvdb2 /dev/xvdb2: clean, 101647/453376 files, 643443/1811968 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/xvdb2 [...] Specifically I observed the problems described if the VM had been live-migrated before being rebooted. Does this make any sense to anyone, or is it a known problem? Regards, Ulrich _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
