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

Re: [Xen-users] RE: Trying to use Xen PV drivers for Windows (Release 0.

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] RE: Trying to use Xen PV drivers for Windows (Release 0.5.0)
From: Igor Chubin <igor@xxxxxxx>
Date: Sun, 23 Dec 2007 11:49:46 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 23 Dec 2007 01:49:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0131A5DC@trantor>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D0131A5AA@trantor> <20071222221935.GX5594@xxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0131A5DC@trantor>
Reply-to: Igor Chubin <igor@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.16 (2007-06-11)
...
> > 
> > Thank you for your any ideas.
> > And once again thank you for you work
> > 
> 
> Are you using Intel or AMD? What version of Xen?

Hello,
thank you for the answer.


There was information
about my system (xm info, xm dmesg and the windows 
domain config) at the previous letter
(at the and of the letter).

I use AMD, 
host system is Debian (32bit).
Hypervisor is 3.1.1 and Dom0 kernel is 2.6.18 from 
the Debian repo (PAE).



> 
> Can you use debugview from sysinternals to get the output of the crash
> dump? The procedure is basically:
> 


Thank you, 


> 1. Don't boot with /GPLPV
> 2. Make sure your system is set to write out a crash dump


I'm sorry, I don't know much about windows, so:

How can I be sure that system 
is set to write out crash dump?
Where should I look at to be sure?
It this boot.ini key or something alike
that make a system write dump?

> 3. Start DebugView
> 4. Do a block-attach to make it crash
> 5. Let the crash dump do it's thing
> 6. Boot the system again without /GPLPV
> 7. Start DebugView
> 8. Analyse the crash dump (C:\Windows\Memory.dmp probably)
> 9. Email the output to me
> 
> Thanks
> 
> James
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

-- 
WBR, i.m.chubin


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