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] domU crash by large disk operations on dom0

To: Matthias Ableitner <spam@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] domU crash by large disk operations on dom0
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 07 Aug 2007 13:08:53 +0100
Delivery-date: Tue, 07 Aug 2007 05:06:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46B85E38.2090302@xxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfY67ij9yYp7kTeEdyCkgAX8io7RQ==
Thread-topic: [Xen-devel] domU crash by large disk operations on dom0
User-agent: Microsoft-Entourage/
Almost certainly this is a jump at bm->dma_cb() == NULL. Possibly a DMA
control block has been queued up twice or something like that.

This whole area of code is rewritten in qemu 0.90, as used in xen-unstable.
You may have success using xen-unstable's qemu-0.90 on xen 3.1.

 -- Keir

On 7/8/07 12:57, "Matthias Ableitner" <spam@xxxxxxx> wrote:

> Hi,
> i've installed xen 3.1 as dom0 and windows 2003 as domU. While dom0 does
> big file operations, qemu-dm crashes with a segfault:
> qemu-dm[18802]: segfault at 0000000000000000 rip 0000000000000000 rsp
> 0000000041000c08 error 14
> This happened while dom0 was cloning a snapshot from the partion, where
> domU lives. I can reproduce the bug, so i made a backtrace:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1090525504 (LWP 7085)]
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x000000000042b2e3 in dma_thread_func (opaque=<value optimized out>)
>      at
> /var/tmp/portage/app-emulation/xen-tools-3.1.0/work/xen-3.1.0-src/tools/ioemu/
> hw/ide.c:2402
> #2  0x00002b044f6e1135 in start_thread () from /lib/libpthread.so.0
> #3  0x00002b044fd1562d in clone () from /lib/libc.so.6
> #4  0x0000000000000000 in ?? ()
> I've added this to bug #542 but i don't know, if it's the same bug.
> Others seems to have the problem too, but i couldn't find a solution. My
> solution is to avoid big file operations, or stop the domU...
> Others seems to have this problem too.
> Best regards,
> Matthias
> Ps.: more details are also on xen-users:
> http://lists.xensource.com/archives/html/xen-users/2007-08/msg00074.html
> _______________________________________________
> 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>