Windows guest cannot connect to COM1 (virtual serial port)
Posted: 11. Jun 2010, 14:34
To be clear, and to differentiate from all the other posts on the forum, I am NOT using any sort of USB to serial device. I'm just talking about setting up a plain jane virtual serial port, which I want to use to try and do kernel debugging between two windows VMs (I've successfully done this in the past with various versions of VMWare, and now I want to stop using that on a PC and start using virtualbox on my mac.)
Before starting up the Windows guest, I go to the configuration, and select serial ports.
I check "Enable serial port" and select Port Number COM1 with it's default options. The port mode is set to "Host Pipe" and I check the box "Create Pipe". I then set the pipe path to be /Users/kestrel/bla. When I start up the VM, I can see it IS creating the pipe on the host system ("srwxr-xr-x 1 kestrel staff 0 Jun 10 13:21 bla")
When the system is booted, I right click on My Computer and select Manage. Then I select Device Manager. Under "Ports (COM & LPT)", it lists only LPT 1. It should also be listing COM1, but it isn't.
I right click on ports, and select "Scan for hardware changes" but nothing changes. I then go to Control Panels and select Add Hardware. Since there's no COM port option, I select the last, generic, option: "Add new hardware device." I then select "Install the hardware that I manually select from a list". I then select "Ports (COM & LPT)" and then "Communications port". It subsequently says "The software for this device is now installed, but may not work correctly. Windows cannot determine the settings for this device. Consult the documentation that came with this device and use the Resource tab to set the configuration. (Code 34)"
I then go back to Device Manager, and see COM3 listed, but it has a little yellow "!" icon displayed, indicating it's probably still having problems.
When I then open up WinDbg, and try to connect to any port, com1, com2, or com3, in all cases it says it can't find the port.
I also tried going back out and reconfiguring the virtualbox settings for the VM to tell it to use COM3, but I was still unable to connect to it with windbg.
Has anyone set up a virtual serial port such that it can be connected to from within the Windows guest?
Thanks
Kestrel
Before starting up the Windows guest, I go to the configuration, and select serial ports.
I check "Enable serial port" and select Port Number COM1 with it's default options. The port mode is set to "Host Pipe" and I check the box "Create Pipe". I then set the pipe path to be /Users/kestrel/bla. When I start up the VM, I can see it IS creating the pipe on the host system ("srwxr-xr-x 1 kestrel staff 0 Jun 10 13:21 bla")
When the system is booted, I right click on My Computer and select Manage. Then I select Device Manager. Under "Ports (COM & LPT)", it lists only LPT 1. It should also be listing COM1, but it isn't.
I right click on ports, and select "Scan for hardware changes" but nothing changes. I then go to Control Panels and select Add Hardware. Since there's no COM port option, I select the last, generic, option: "Add new hardware device." I then select "Install the hardware that I manually select from a list". I then select "Ports (COM & LPT)" and then "Communications port". It subsequently says "The software for this device is now installed, but may not work correctly. Windows cannot determine the settings for this device. Consult the documentation that came with this device and use the Resource tab to set the configuration. (Code 34)"
I then go back to Device Manager, and see COM3 listed, but it has a little yellow "!" icon displayed, indicating it's probably still having problems.
When I then open up WinDbg, and try to connect to any port, com1, com2, or com3, in all cases it says it can't find the port.
I also tried going back out and reconfiguring the virtualbox settings for the VM to tell it to use COM3, but I was still unable to connect to it with windbg.
Has anyone set up a virtual serial port such that it can be connected to from within the Windows guest?
Thanks
Kestrel