Thank you for your answer.  I realize my first post wasn't clear.  I want a total of 2 serial ports, with port0 used for console, and 1/2 used for standard serial communication.  I only get COM1 and COM2 in Win7, COM3 is missing.

Migrating to F19 isn't possible as we aim to port this work on RHEL7 when it comes out, so we'd like to stick to F18.

Regards,

Eric Viseur


2013/7/9 Cole Robinson <crobinso@redhat.com>
On 07/04/2013 04:02 AM, Eric Viseur wrote:
> Hi,
>
> I'm having another problem with my KVM setup, using Fedora 18.  For debugging
> pruposes, I added two serial ports to my virtual machines, like this :
>
> <serial type="pty">
> <target port="1 (or 2)" />
> </serial>
>
> On the Linux guest, everything works fine.  On the Windows 7 guest, I only get
> one of the two ports.  The one showing up works well, but I don't understand
> why the second one doesn't show up.  libvirt reports the creation of the char
> devices on the logs, without any error.
>

I just tried on F19 and it works for me with a windows 7 VM. The device XML is:

    <serial type='pty'>
      <target port='0'/>
    </serial>
    <serial type='pty'>
      <target port='1'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>

The relevant command line bits in /var/log/libvirt/qemu/win7.log were:

-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
-chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1

No virtio-win drivers or anything FWIW.

If that roughly matches what you are seeing, it's likely an F18 qemu bug. You
can file it against F18 but my main recommendation would be to update to F19
since it will be more actively supported going forward.

- Cole