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] pv_ops dom0 x86_32 logs

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] pv_ops dom0 x86_32 logs
From: "Marc - A. Dahlhaus" <mad@xxxxxx>
Date: Fri, 13 Mar 2009 23:17:44 +0100
Delivery-date: Fri, 13 Mar 2009 15:18:28 -0700
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
User-agent: Thunderbird (Windows/20081209)
Hello Jeremy,

did another boot test with latest xen/dom0/hackery <http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/dom0/hackery> today. I was a little bit less noisy than the last time but there are a few back traces left.
Xen log and dom0 dmesg attached.

Next steps on my list are booting a pv and a hvm domain as well as some stress testing in dom0.
Anything specific i could keep an eye on while testing?


Attachment: pv_ops_dom0_dmesg.log.gz
Description: GNU Zip compressed data

Attachment: pv_ops_dom0_xen.log.gz
Description: GNU Zip compressed data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] pv_ops dom0 x86_32 logs, Marc - A. Dahlhaus <=