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


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

To: <wenche_chang@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Some VMs are crashed in xen 4.0.1
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Fri, 25 Feb 2011 08:00:22 +0000
Delivery-date: Fri, 25 Feb 2011 00:01:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=vJDyu/xbDTB20JE2mCVOF4hWG3K4zYArotdqx6XmU68=; b=rRlQxCYL/4mj4kepT1NkWtDiFOLR5yDLq5ppdT/NQQHuYIfegEN5PJeFusCy5TJqHv JjlEyGhUu3Slo/7PS8qlfOkyTJ7M1NuGz36I64O71sdGpLz2gepgkAFlrpBTbhKu6i1x XPKGJPcGd25FKD+gMpCT+hbDYXPGmq9Qekl7E=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=LDvsHQAAYRNeNz7x76yDZl15RYRw/rEAid/N0bnAJH4o8W7ZUDRrVDUX4HarugvVMI o97U7hJfWWPC/4PSrcIB9KIqlTON7IXVRqQdPEzUa3uuShEoNabF0HEx2Yd/hRVaNfsN fa1P7N3AmUWmQBVq0KHxhbvScJei6A0CyKUfk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43FEA041821E5247942BF0802912D93803DC0FB3@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/m7NzaSSqpcu76BfUbrQALSr/P
Thread-topic: [Xen-devel] Some VMs are crashed in xen 4.0.1
User-agent: Microsoft-Entourage/
On 25/02/2011 02:37, "wenche_chang@xxxxxxxxxxxx" <wenche_chang@xxxxxxxxxxxx>

> 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

Your qemu-dm processes are dying on SIGSEGV. You need to get a core dump
from one of these crashed processes and use gdb to get a backtrace.

 -- Keir

> The qemu-dm log is like this
> /var/log/xen/qemu-dm-1cf74c71-62c2-4411-abb2-1db0a2e45142.log
> 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-c
> onverted-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
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

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