[Xen-devel] Passthrough of Serial port /dev/ttyS0 to PV and HVM domains problems

["Linux@xxxxxxxxxxxxxx" <linux@xxxxxxxxxxxxxx>]

I'm trying to get the following working:

Serial port (/dev/ttyS0) passthrough to a PV or HVM domain, together with
xenfb and usb passthrough.

passthrough of the serial port works fine in a PV without xenfb (and so
without qemu) by using the following lines in the config:

        irq = [4]
        ioports = ["3f8-3ff"]

by using
        vfb = [ 'vnc=1,vnclisten=0.0.0.0,vncunused=1' ]
it will use qemu, so the lines above don't work anymore.

Now it uses qemu which is the same for HVM and PVM


using   serial='/dev/ttyS0' in the config files doesn't work, although it 
should according to
the qemu manpages.
using:
    echo "test" > /dev/ttyS0
on the host,and
    cat /dev/ttyS0
on the guest, to test it, it shows nothing on the guest





when using serial=pty in the config file, and using
using:
    echo "test" > /dev/pts/0
on the host,and
    cat /dev/ttyS0
on the guest, to test it, it shows the test string on the guest


using:
socat /dev/ttyS0 /dev/pts/0 works passing through the hardware serial port
to the guest, but it's not very elegant since the pts/0 could change.






Questions:
- Shouldn't the serial='/dev/ttyS0' config option work in the first place
for the qemu domains (PV or HVM) ?

- is xenfb and thus x11 support indeed only available on PV's using qemu ?

- is there any other way to get sdl/vnc graphics in a domU together with
serial port passthrough, without using external tools as socat ?

- wouldn't it be nice to have some sort of standardization in all the
available passthrough options, or at least an overview in Dom0 of what is
passthrouged to what in the different guest domains.
There are quite a few variables at the moment:
          -xend-PV or qemu-PV/HVM.
          -PCI or USB or serial or parport passthrough.
          -with or without VT-D/iommu support.
And it is difficult to find out the status (working/partially/not-working)
of all these options it leads to. It also means there is not much
documentation around.


I hope anyone can help ...


Regards,

Sander Eikelenboom






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel