Hi,
In fact it works fine .
The issue is the following :
Having a look to the source path , via Virtual Machine Manager , I got nothing
.
But if I dump the xml file , then I got the pts/x reference :
<channel type='pty'>
<source path='/dev/pts/2'/>
<target type='virtio' name='omnivision.virtio.serial.port.name'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
By using a newer stuff on my second host ( RHEL7 instead of RHEL5) , then , it’s correct also via Virtual Machine Manager.
Thx for help.
J.P.
-----Message d'origine-----
De : Daniel P. Berrange [mailto:berrange@redhat.com]
Envoyé : jeudi 27 août 2015 12:13
À : Jean-Pierre Ribeauville
Cc : libvirt-users@redhat.com
Objet : Re: [libvirt-users] Virtio serial exposition
On Wed, Aug 26, 2015 at 12:17:20PM +0000, Jean-Pierre Ribeauville wrote:
> Hi,
>
> I try to exchange datas between host and Guest by adding these lines in a guest .xml conf file :
>
> <channel type='pty'>
> <target type='virtio' name='arbitrary.virtio.serial.port.name'/>
> <address type='virtio-serial' controller='0' bus='0' port='1'/>
> </channel>
>
>
> Then /dev/virtio-ports/arbitrary.virtio.serial.port.name is exposed in the guest and a /dev/pts/x is seen as source path on the host.
>
> I checked that on two Linux hosts :
>
> 1)
>
> libvirt-daemon-driver-qemu-1.2.8-16.el7_1.3.x86_64
> qemu-kvm-1.5.3-86.el7_1.5.x86_64
> qemu-kvm-common-1.5.3-86.el7_1.5.x86_64
> qemu-guest-agent-2.1.0-4.el7.x86_64
> ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch
> qemu-img-1.5.3-86.el7_1.5.x86_64
> Linux sparring 3.10.0-229.el7.x86_64 #1 SMP Thu Jan 29 18:37:38 EST
> 2015 x86_64 x86_64 x86_64 GNU/Linux
>
>
> 2)
>
> qemu-img-0.12.1.2-2.415.el6.x86_64
> qemu-kvm-0.12.1.2-2.415.el6.x86_64
> gpxe-roms-qemu-0.9.7-6.10.el6.noarch
>
>
> Linux orion 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013
> x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> The device is only exposed on the guest of the first host .
>
> Is it due to a too old version of qemu and/or Linux on the second
> host or some packages missing on this second host ?
Libvirt should tell you if qemu / host is too old, so sounds like a guest issue instead. Perhaps the guest kernel-module has not been loaded for the second guest ?
Regards,
Daniel
--
|: http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o-
http://virt-manager.org :|
|: http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|