Re: [win-pv-devel] OpenXT, Windows 10 guest and Windbg question

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-
> bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Steven Meisner
> Sent: 19 November 2015 16:28
> To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [win-pv-devel] OpenXT, Windows 10 guest and Windbg question
> 
> I am new to the list, but have been doing Windows Xen PV driver
> development for quite some time. I am trying to use a Windows 10 x64 guest
> to develop a new driver and am having problems connecting Windbg. BTW, I
> am working on OpenXT.
> 
> This is what I've done so far:
> 
> - Disabled SELinux
> - Disabled stub domains (to allow the guest to indirectly connect out to the
> debugger)
> - Run sockpipe on the debugger system to allow the guest to connect (via a
> QEMU emulated COM port) over a local pipe
> - In the guest:
>   o bcdedit /copy {current} /d "Debugger Enabled"
>   o bcdedit /debug {UUID} on
>   o bcdedit /set {UUID} testsigning on
>   o bcdedit /set {UUID} recoveryenabled off
> Also tried:
>   o bcdedit /set {UUID} loadoptions DDISABLE_INTEGRITY_CHECK
> 
> On OpenXT platform, setup QEMU to connect to sockpipe on the debug
> system:
> - xec-vm -n win10 set extra-xenvm "serial=tcp:192.168.2.60:7204,nodelay"
> 
> When I start the guest, QEMU creates the virtual com port and connects to
> sockpipe. Then the Win10 starts in the VM and attempts to connect, but it
> just halts after Windbg issues a reset (which is normal).
> 
> I have tested the serial comms.and it works fine. I have also tried Win10 32-
> bit.did not work. I tried Win7 and Win8 targets .they work fine in the same
> environment.
> 
> So my questions;
> 1. Is there any problem using Windbg (version 10.0.10240.9) with Windows 10
> as a target? Did the protocol change and the latest Windbg is not compatible?

Steve,

I've not had any problem using the Win 8 WDK version of Windbg against my 
64-bit win10 VM running on my upstream (Xen + dom0) test host.

> 2. Are there any settings I missed in the bcdedit settings?

I don't think so. I guess you may want to check the default serial settings to 
see if there's any difference that may conflict with your QEMU UART device 
model.

> 3. Any other things to try?
> 

Try connecting the other way round? (I.e. set up Sockpipe in passive open and 
have your QEMU connect to it).

  Paul

> Thanks,
> Steve
> 
> 
> 
> Steve Meisner
> Assured Information Security, Inc.
> 50 Burlington Mall Road Road
> Burlington, MA 01805
> Cell: (603) 305-3539
> 
> 
> _______________________________________________
> win-pv-devel mailing list
> win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel