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-bugs] [Bug 1038] windows 2003 domU crash by large disk operations o

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1038] windows 2003 domU crash by large disk operations on dom0 (qemu-dm segfault)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 12 Aug 2008 03:10:28 -0700
Delivery-date: Tue, 12 Aug 2008 03:10:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1038-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

szazs@xxxxxxxxx changed:

           What    |Removed                     |Added
                 CC|                            |szazs@xxxxxxxxx

------- Comment #11 from szazs@xxxxxxxxx  2008-08-12 03:10 -------
Is this bug not related to the following issue:
http://bugzilla.kernel.org/show_bug.cgi?id=7372 ?

In dom0, everything slows down when I try 'xm save' a domU on a RAID1 + LVM
partition... Yesterday evening the whole staff freezed totally with load 22,
when tried tiobench on this partition. (There were 2 linux domain + 1 HVM
domain running, but without any special stress)

I have 4 AMD Opteron 8220 CPUs, kernel, hard disk partitions in
raid1 and LVM2...
Similar slow-down was experienced with a non-xen debian kernel
(2.6.18-4-amd64), but upgrading it to 2.6.24-etchnhalf.1-amd64 helped a lot
(which was expected according to the bugtrack mentioned above).

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

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