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-users

RE: [Xen-users] W2k3 HVM domain QEMU drivers

To: "Jonathan Anderson" <jonathan.b.andersonr@xxxxxxxxx>
Subject: RE: [Xen-users] W2k3 HVM domain QEMU drivers
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 3 May 2009 19:16:05 +1000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 03 May 2009 02:16:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <80520740905030036s7a0439bdtc44efe0d013ec04@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <80520740905022131u29329eflcc8508d3dc1216e9@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0162D35F@trantor> <80520740905030036s7a0439bdtc44efe0d013ec04@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnLwfHxjx16/DcARgCORWk/P43fXAADaXLw
Thread-topic: [Xen-users] W2k3 HVM domain QEMU drivers
> 
> On Sun, May 3, 2009 at 12:45 AM, James Harper
> <james.harper@xxxxxxxxxxxxxxxx> wrote:
> >> documented somewhere, as the machine ended up bluescreening and I
had
> > to use
> >> /NOGPLPV to get it to boot again so I could upgrade it to SP2.
> >
> > I don't remember having any problems with w2k3sp1.
> 
> I don't think it was even SP1 when I was having the problem.  But in
> googling for an explanation for why it was bluescreening, I found a
> post saying that the drivers used a system call which was only added
> in SP2.

Could it have been referring to XPsp2 and not W2K3sp2? I think there was
a problem with XPsp1 and lower but I think I worked around that (I could
be wrong though).

James

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

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