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


[Xen-devel] Some VMs are crashed in xen 4.0.1

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Some VMs are crashed in xen 4.0.1
From: <wenche_chang@xxxxxxxxxxxx>
Date: Fri, 25 Feb 2011 10:37:03 +0800
Delivery-date: Thu, 24 Feb 2011 18:38:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvUlOIwBb/m7NzaSSqpcu76BfUbrQ==
Thread-topic: Some VMs are crashed in xen 4.0.1

We Run 150 Fedora13 VMs on many hypervisor , images and xml are stored in DFS.


Some of the VMs will be crashed in 48 hours. Some of the VMs will remain.

(The VMs have some IO/CPU loading by start up a loading services.)

All the crashed VM has the same WARNING message in xend.log, for example:

[2011-02-18 10:42:36 3235] WARNING (image:552) domain 5ab73a3f-87da-48fd-9236-a2f752c16c76: device model failure: pid 11037: died due to signal 11; see /var/log/xen/qemu-dm-5ab73a3f-87da-48fd-9236-a2f752c16c76.log


The qemu-dm log is like this



domid: 35

config qemu network with xen bridge for  tap35.0 teprod

Using file /mnt/vm_depot/volume_pool/fd3e/47/fd3e4783-9c66-4313-b51a-8b737a792392 in read-write mode

Watching /local/domain/0/device-model/35/logdirty/cmd

Watching /local/domain/0/device-model/35/command

char device redirected to /dev/pts/2

qemu_map_cache_init nr_buckets = 10000 size 4194304

shared page at pfn feffd

buffered io page at pfn feffb

Guest uuid = 1cf74c71-62c2-4411-abb2-1db0a2e45142

Time offset set 0

populating video RAM at ff000000

mapping video RAM from ff000000

Register xen platform.

Done register platform.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

xs_read(/local/domain/0/device-model/35/xen_extended_power_mgmt): read error

xs_read(): vncpasswd get error. /vm/1cf74c71-62c2-4411-abb2-1db0a2e45142/vncpasswd.

Log-dirty: no command yet.

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

xs_read(/local/domain/35/log-throttling): read error

qemu: ignoring not-understood drive `/local/domain/35/log-throttling'

medium change watch on `/local/domain/35/log-throttling' - unknown device, ignored

cirrus vga map change while on lfb mode

mapping vram to f0000000 - f0400000

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.




I found a mail last year in http://xen.1045712.n5.nabble.com/PATCH-0-2-Fix-could-not-boot-vm-image-which-converted-from-phy-partition-td2548812.html

, but it’s XEN 3.4.0, and we use XEN 4.0.1 RELEASE.


It’s a bug of XEN or something else?

The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>