Re: serial=pty in HVM guests broken?

[Dustin Marquess <dmarquess%gmail.com@localhost>]

On Sun, Jun 28, 2009 at 8:52 AM, Jean-Yves
Migeon<jeanyves.migeon%free.fr@localhost> wrote:
> Dustin Marquess wrote:
>>
>> All,
>>
>> I've been trying to run WinDBG against a Windows HVM domU to debug the
>> GPLPV drivers.  After spending an hour wondering why it wasn't
>> working, I figured I'd try a simple test.
>>
>> On the NetBSD server I ran 'xm console win2k3'.  In the domU, I loaded
>> up Tera Term and set it to use COM1 @ 115200.
>>
>> Anything I typed in the xm console window showed up fine in Tera Term,
>> however NOTHING I typed in Tera Term showed up in the xm console
>> window.  Tried changing the baud rates, and that didn't seem to matter
>> (doubt it would, since xmc->TT worked no matter what).
>>
>> Is this a known issue?
>
> I have personally never tried that, but I remember mails on xen-devel@ where
> third party programs were used to create virtual COM ports in Windows,
> without using the original ones found in the HVM domU.
>
> Sorry, can't help you that much :/ Maybe try from a XenSource Linux dom0,
> and report if that works. If that is the case, something is clearly missing
> in NetBSD dom0, or the qemu-dm part.

The problem is when debugging the Windows kernel remotely using
WinDBG, software COM ports don't work :).

I know serial=pty works in Linux.  The problem is GPLPV also works in
Linux.  I was trying to debug why it isn't working on a NetBSD dom0
:).

Thanks though!
-Dustin