Timeline for Kernel debugging between two virtual machines not working
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 19, 2021 at 15:34 | comment | added | 0xC0000022L♦ | VirtualKD is practially abandoned, but there's a fork VirtualKD-Redux someplace on Github. Also note that for many operations the speed is more than sufficient. But there are plenty of scenarios where you with to have a faster connection (such as Firewire in the past) and then the VirtuakKD method is very handy (driver development is sped up by transferring new builds over the KD connection during boot). Also keep in mind that Windows since 8.1 should support KD over network. Although I never tested it with VMs. | |
| Nov 22, 2015 at 21:45 | vote | accept | 0xAK | ||
| Nov 22, 2015 at 11:34 | answer | added | 0xAK | timeline score: 3 | |
| Nov 21, 2015 at 16:03 | history | edited | 0xAK | CC BY-SA 3.0 |
adding machine info
|
| Nov 21, 2015 at 15:22 | comment | added | 0xAK | Well thanks but this is not what i need, and my host to vm already works with no problem | |
| Nov 21, 2015 at 14:16 | comment | added | tmr232 | No. It is host-to-vm debugging. After installation, it usually works out of the box. | |
| Nov 21, 2015 at 13:29 | comment | added | 0xAK | @tmr232, I dont understand.. isnt your method just an improvement to a vm-to-vm debugging? as in to make it faster? | |
| Nov 21, 2015 at 10:02 | comment | added | tmr232 | I understand. In my experience it is a lot easier to set it up, compared to the vm-to-vm debugging. | |
| Nov 20, 2015 at 22:55 | comment | added | 0xAK | @tmr232, Thanks you very much for the option, but right now im just trying to generally kernel-debug and not interested at the moment in improving any speed. But i will look into it in the future if ill be able to get it done | |
| Nov 20, 2015 at 20:27 | comment | added | tmr232 | Since you are using VMWare Workstation, I would recommend the use of VirtualKD. It is really easy to set up, and is extremely fast. | |
| Nov 20, 2015 at 18:34 | comment | added | 0xAK | @JasonGeffner, communities.vmware.com/message/2557171#2557171 I gave it a try.. lets see if ill get any luck there | |
| Nov 20, 2015 at 18:17 | comment | added | 0xAK | @JasonGeffner, yes they are both connected | |
| Nov 20, 2015 at 18:13 | comment | added | Jason Geffner | Sorry, link should have been pubs.vmware.com/workstation-10/… | |
| Nov 20, 2015 at 18:01 | comment | added | 0xAK |
@JasonGeffner, i dont see any unique explanation on that link you sent me. But under the configuration settings in both VMs. the serial port on both is on connected state and both has the same Pipe Name of \\.\pipe\com_1
|
|
| Nov 20, 2015 at 18:00 | comment | added | Jason Geffner | And if that isn't the problem, you may want to ask on communities.vmware.com/community/vmtn/workstation/content | |
| Nov 20, 2015 at 17:58 | comment | added | Jason Geffner | As per pubs.vmware.com/workstation-10/topic/com.vmware.ws.using.doc/…, are you sure the serial port is connected in both VMs? | |
| Nov 20, 2015 at 17:54 | comment | added | 0xAK |
@JasonGeffner, It does look a little different than my setup, yet its still not working. The difference is (Between what i thought is correct): They put on the Debugged vm The other end is an application when the other side is a VM that is supposed to debug it. Also on the windbg, the pipe name they use is \\.\com1 instead of \\.\pipe\com_1 which is what i did. Nonetheless its still not working even with their setup
|
|
| Nov 20, 2015 at 17:32 | comment | added | Jason Geffner | Are all your settings the same as described in ndis.com/ndis-debugging/virtual/vmwaresetup.htm ? | |
| Nov 20, 2015 at 15:57 | history | asked | 0xAK | CC BY-SA 3.0 |