[libvirt-users] Windows guest and virtio serial port
I'm not sure, if it's correct mailing list to post this problem to. I'm having problems with Windows guest and virtio serial port. According to this manual: http://www.spice-space.org/page/Whiteboard/AgentProtocol I should get a named pipe on my guest VM after I create VirtIO sedial device and spicevmc channel. This works without any problems on Linux guest: ls /dev/virtio-ports/ com.redhat.spice.0 But on Windows guest I can see no such pipe: PipeList v1.01 by Mark Russinovich http://www.sysinternals.com Pipe Name Instances Max Instances --------- --------- -------- ----- InitShutdown 3 -1 lsass 4 -1 ntsvcs 3 -1 scerpc 3 -1 Winsock2\CatalogChangeListener-2b8-0 1 1 epmapper 3 -1 Winsock2\CatalogChangeListener-1ac-0 1 1 LSM_API_service 3 -1 TermSrv_API_service 3 -1 Ctx_WinStation_API_service 3 -1 eventlog 3 -1 Winsock2\CatalogChangeListener-174-0 1 1 atsvc 3 -1 wkssvc 6 -1 Winsock2\CatalogChangeListener-16c-0 1 1 SessEnvPublicRpc 3 -1 spoolss 3 -1 Winsock2\CatalogChangeListener-550-0 1 1 trkwks 3 -1 NlaSvcTask 1 -1 srvsvc 5 -1 browser 3 -1 Winsock2\CatalogChangeListener-710-0 1 1 Winsock2\CatalogChangeListener-228-0 1 1 Winsock2\CatalogChangeListener-230-0 1 1 HPUPDMon 1 1 MsFteWds 2 -1 PIPE_EVENTROOT\CIMV2SCM EVENT PROVIDER 1 -1 TDLN-3772-41 1 2 TDLN-3216-41 1 2 virtio serial drivers are installed on Windows guest VM. What I am missing here? Thank you.
On Thu, Jun 30, 2016 at 11:39:48AM +0300, Tadas wrote:
I'm not sure, if it's correct mailing list to post this problem to.
I'm having problems with Windows guest and virtio serial port. According to this manual: http://www.spice-space.org/page/Whiteboard/AgentProtocol I should get a named pipe on my guest VM after I create VirtIO sedial device and spicevmc channel. This works without any problems on Linux guest:
ls /dev/virtio-ports/ com.redhat.spice.0
But on Windows guest I can see no such pipe:
I have no idea how that should look like in Win guest. My guess is that you have installed all the drivers that are needed, right? In that case it might be some bug in QEMU. Although it seems more likely that drivers are missing (or buggy).
Thank you for reply. According to spicce-space.org, named pipe should look like this: \\\\.\\Global\\com.redhat.spice.0 As for drivers, i've used stable virtio drivers from https://fedoraproject.org/wiki/Windows_Virtio_Drivers Will try to use latest ones. I can see "VirtIO Serial Driver" in device manager of VM machine. Also there are no "Unknown" devices. This problem happens on Debian stable and unstable hypervisor, also on Fedora 23 hypervisor. -----Original Message----- From: Martin Kletzander Sent: Thursday, June 30, 2016 4:36 PM To: Tadas Cc: libvirt-users Subject: Re: [libvirt-users] Windows guest and virtio serial port
Okay, I've updated virtio serial drivers to latest ones. This did not help. Afterwards I've enabled "Show hidden devices" in Device manager of a guest os.In the "Other devices" section I can see two virtio serial ports with question marks (i did configure guest with 2 virtio channels). Is this a normal behaviour? Screenshot: https://cloud.ring.lt/index.php/s/YCgnuc8ncPo18dP Any ideas would be appreciated. Thank you. On Thu, 2016-06-30 at 11:39 +0300, Tadas wrote:
I'm not sure, if it's correct mailing list to post this problem to.
I'm having problems with Windows guest and virtio serial port. According to this manual: http://www.spice-space.org/page/Whiteboard/AgentProtocol I should get a named pipe on my guest VM after I create VirtIO sedial device and spicevmc channel. This works without any problems on Linux guest:
ls /dev/virtio-ports/ com.redhat.spice.0
But on Windows guest I can see no such pipe:
PipeList v1.01 by Mark Russinovich http://www.sysinternals.com
Pipe Name Instances Max Instances --------- --------- -------- ----- InitShutdown 3 -1 lsass 4 -1 ntsvcs 3 -1 scerpc 3 -1 Winsock2\CatalogChangeListener-2b8-0 1 1 epmapper 3 -1 Winsock2\CatalogChangeListener-1ac-0 1 1 LSM_API_service 3 -1 TermSrv_API_service 3 -1 Ctx_WinStation_API_service 3 -1 eventlog 3 -1 Winsock2\CatalogChangeListener-174-0 1 1 atsvc 3 -1 wkssvc 6 -1 Winsock2\CatalogChangeListener-16c-0 1 1 SessEnvPublicRpc 3 -1 spoolss 3 -1 Winsock2\CatalogChangeListener-550-0 1 1 trkwks 3 -1 NlaSvcTask 1 -1 srvsvc 5 -1 browser 3 -1 Winsock2\CatalogChangeListener-710-0 1 1 Winsock2\CatalogChangeListener-228-0 1 1 Winsock2\CatalogChangeListener-230-0 1 1 HPUPDMon 1 1 MsFteWds 2 -1 PIPE_EVENTROOT\CIMV2SCM EVENT PROVIDER 1 -1 TDLN-3772-41 1 2 TDLN-3216-41 1 2
virtio serial drivers are installed on Windows guest VM. What I am missing here? Thank you.
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Okay, it seems that \\.\\Global\ named pipes are not liested via pipelis.exe nor via powershell. Named pipes are created though. On Fri, 2016-07-01 at 09:09 +0300, Tadas wrote:
Okay, I've updated virtio serial drivers to latest ones. This did not help. Afterwards I've enabled "Show hidden devices" in Device manager of a guest os.In the "Other devices" section I can see two virtio serial ports with question marks (i did configure guest with 2 virtio channels). Is this a normal behaviour? Screenshot: https://cloud.ring.lt/index.php/s/YCgnuc8ncPo18dP
Any ideas would be appreciated. Thank you.
On Thu, 2016-06-30 at 11:39 +0300, Tadas wrote:
I'm not sure, if it's correct mailing list to post this problem to.
I'm having problems with Windows guest and virtio serial port. According to this manual: http://www.spice-space.org/page/Whiteboard/AgentProtocol I should get a named pipe on my guest VM after I create VirtIO sedial device and spicevmc channel. This works without any problems on Linux guest:
ls /dev/virtio-ports/ com.redhat.spice.0
But on Windows guest I can see no such pipe:
PipeList v1.01 by Mark Russinovich http://www.sysinternals.com
Pipe Name Instances Max Instances --------- --------- ---- ---- ----- InitShutdown 3 - 1 lsass 4 - 1 ntsvcs 3 - 1 scerpc 3 - 1 Winsock2\CatalogChangeListener-2b8- 0 1 1 epmapper 3 - 1 Winsock2\CatalogChangeListener-1ac- 0 1 1 LSM_API_service 3 - 1 TermSrv_API_service 3 - 1 Ctx_WinStation_API_service 3 - 1 eventlog 3 - 1 Winsock2\CatalogChangeListener-174- 0 1 1 atsvc 3 - 1 wkssvc 6 - 1 Winsock2\CatalogChangeListener-16c- 0 1 1 SessEnvPublicRpc 3 - 1 spoolss 3 - 1 Winsock2\CatalogChangeListener-550- 0 1 1 trkwks 3 - 1 NlaSvcTask 1 - 1 srvsvc 5 - 1 browser 3 - 1 Winsock2\CatalogChangeListener-710- 0 1 1 Winsock2\CatalogChangeListener-228- 0 1 1 Winsock2\CatalogChangeListener-230- 0 1 1 HPUPDMon 1 1 MsFteWds 2 - 1 PIPE_EVENTROOT\CIMV2SCM EVENT PROVIDER 1 - 1 TDLN-3772- 41 1 2 TDLN-3216- 41 1 2
virtio serial drivers are installed on Windows guest VM. What I am missing here? Thank you.
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
participants (2)
-
Martin Kletzander -
Tadas