From mboxrd@z Thu Jan 1 00:00:00 1970 From: Igor Chubin Subject: Re: RE: Trying to use Xen PV drivers for Windows (Release 0.5.0) Date: Sun, 23 Dec 2007 11:49:46 +0200 Message-ID: <20071223094946.GC5594@chub.in> References: <20071222221935.GX5594@chub.in> Reply-To: Igor Chubin Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: James Harper Cc: xen-devel , xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org ... > > > > 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@lists.xensource.com > http://lists.xensource.com/xen-users -- WBR, i.m.chubin