WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] privcmd_fault with WinXP

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] privcmd_fault with WinXP
From: Michael David Crawford <mdc@xxxxxxxxx>
Date: Fri, 22 May 2009 05:22:22 -0700
Delivery-date: Fri, 22 May 2009 05:22:57 -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>
Organization: Prgmr.com
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
I'm getting a little better at figuring out problems on my own.

I'm using the 3.4.0 Xen kernel, but with the Linux git xen-tip/master sources. Are they expected to be compatible?

I'll give xen-tip/next a try.

I really want to be able to run a recent Linux because it has a driver for my 3ware 9690SA RAID. The 2.6.18 kernel doesn't. I took a stab at backporting it, but haven't gotten my backport to actually work yet.

So far I can start a WinXP SP3 HVM DomU. A window appears, turns grey, then disappears. Each time I try this, dmesg shows a line like these:

privcmd_fault: vma=ffff88008a971840 7fc99b128000-7fc99b228000, pgoff=0, uv=00007fc99b128000

privcmd_fault: vma=ffff8800919f2c60 7f8e7162e000-7f8e7172e000, pgoff=0, uv=00007f8e7162e000

privcmd_fault: vma=ffff88008a88a4d0 7ffe0da4e000-7ffe0db4e000, pgoff=0, uv=00007ffe0da4e000

If there's anything I could do to help debug this, just let me know.

There was a post about what I think is the same bug at:

http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00104.html

That post includes a call trace - my dmesg doesn't have one. My system doesn't crash - the DomU just exits but nothing else bad happens.

My box is a Core 2 Quad Xeon, e5420 or some such, 8 GB FB-DIMM, Supermicro X7DWA-N motherboard.

Hope This Helps!

Mike
--
Michael David Crawford
mdc@xxxxxxxxx

   prgmr.com - We Don't Assume You Are Stupid.

      Xen-Powered Virtual Private Servers: http://prgmr.com/xen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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