oh… the reason it failed is stupid indeed… I omitted to start kdsrv : )) I somehow expected Hyper-V to have something already there, perhaps to start running at boot when it detects debug=on.
It doesn’t work yet… in windbg, it says “parameter is incorrect”:
for VS running normally (no VM)
"Could not start kernel debugging using kdsrv:server=@{com:Port=\.\com1,Baud=115200,Server=HVSERVER},trans=@{com:port=\.\pipe\com_1,baud=115200,pipe,reconnect} parameters, Win32 error 0n87
The parameter is incorrect."
For VS running in VM:
"Could not start kernel debugging using kdsrv:server=@{com:Port=\.\com1,Baud=115200,Server=HVSERVER},trans=@{com:port=\.\com1,baud=115200,reconnect} parameters, Win32 error 0n87
The parameter is incorrect."
Attempting from VS does not give you any error message. It’s only “waiting to connect”.
Does anybody have any idea what I can do?
From: Sam .
To: Kernel Debugging Interest List
Sent: Friday, June 21, 2013 11:27 AM
Subject: Re: [windbg] “Debuggee not connected” when attempting kernel debug on Hyper-V Server
by the way,
does anybody have an idea why the WinDBG executable has for serial, a port (for named pipe) and baud rate, while VS has named pipe baud rate and target port? The WinDBG always uses com1 as the “target port”, or? or, shouldn’t it be either named pipe or com port?
From: Sam .
To: Kernel Debugging Interest List
Sent: Friday, June 21, 2013 10:29 AM
Subject: Re: [windbg] “Debuggee not connected” when attempting kernel debug on Hyper-V Server
about my laptop & my pc: on my laptop, I checked, and I don’t have a COM1. Perhaps only with a specific cable that works.
With “net” option (provisioning / host ip + key), the laptop and the PC are connected through a router.
From: Sam .
To: Kernel Debugging Interest List
Sent: Friday, June 21, 2013 10:24 AM
Subject: Re: [windbg] “Debuggee not connected” when attempting kernel debug on Hyper-V Server
Yes.
I had also tried this:
I had installed Hyper-V Server on my laptop, where my VS was running on my PC (non-VM). I have checked the models of the network adapters of both the PC and laptop, and both are written about in the section about VS provisioning. I had tried that few-steps provisioning, but didn’t work that way either - error in VS after rebooting Hyper-V Server, where the log does not say (or I did not see?) anything specific. I had tried writing the host ip & port myself, but that had caused my laptop (running Hyper-V Server) not to recognize the network adapter after restart. strange. I did not try with serial port - perhaps I need to connect some specific cable directly from my laptop to my pc for that.
I have also tried with 2 VMs:
One running Hyper-V Server and the other Win8 Pro. By serial port. Still not working. I have redirected Hyper-V Server’s serial port to a file. It seems things are being written only at startup (once you get to the login page, it ceases). And it’s not all ASCII. I will try the same for the VM that runs Win8 - redirect to a file, and see if some info is being written or not. The named pipe name for Win8 Pro matches name pipe name of Hyper-V Server, Hyper-V was set as “this end is the server, the other is a VM”, on Win8 VM it was “this end is the client, the other is a VM”.
btw, I once found this article:
http://en.community.dell.com/techcenter/virtualization/w/wiki/3029.aspx?PostSortBy=MostComments&PageIndex=3
can anybody tell me when / why I should use vmdemux?
I tried that, it found odd that remote /s is on the server, and it must call windbg (thought I shouldn’t have a debugger on Hyper-V Server). Either way, my attempt with vmdemux / remote did not work.
I had also found this sentence there:
"On the hyper-v debug session, load the hvexts.dll so that you can run hyper-v related debug commands. "
Do I need to copy certain files from somewhere (I did not find about hvexts.dll in msdn) in the Hyper-V Server machine? or other files?
Is there something else I need to configure as well?
________________________________
From: Jan Bottorff
To: Kernel Debugging Interest List
Sent: Friday, June 21, 2013 4:27 AM
Subject: RE: [windbg] “Debuggee not connected” when attempting kernel debug on Hyper-V Server
Are you saying you’re running Hyper-V in a VMWare VM? I was not aware you could run a hypervisor in a VM.
Jan
From:xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Sam .
Sent: Thursday, June 20, 2013 5:21 AM
To: Kernel Debugging Interest List
Subject: [windbg] “Debuggee not connected” when attempting kernel debug on Hyper-V Server
Hello,
I’ve been trying this for almost a week. Can anybody PLEASE help me?
I’m having a Windows 8 host computer, and the target computer is in a VMWare virtual machine, running Hyper-V Server 2012.
I read lots of articles of how it’s done, but none worked.
I don’t have Windows 8 Pro, so I can’t use Hyper-V Manager.
—
WINDBG is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
WINDBG is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
WINDBG is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer