Bug 1428332 - serial driver for virtio-win seems missing
Summary: serial driver for virtio-win seems missing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Yash Mankad
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-02 10:26 UTC by Eduard Barrera
Modified: 2020-04-15 15:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-07 06:24:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eduard Barrera 2017-03-02 10:26:25 UTC
Description of problem:

Serial driver seems missing in virtio-win downstream package:

This is an extract of the content of  https://access.redhat.com/downloads/content/virtio-win/1.9.0-3.el7

/usr/share/virtio-win/drivers/amd64/Win2008R2/
/usr/share/virtio-win/drivers/amd64/Win2008R2/qxl.cat
/usr/share/virtio-win/drivers/amd64/Win2008R2/qxl.inf
/usr/share/virtio-win/drivers/amd64/Win2008R2/qxl.sys
/usr/share/virtio-win/drivers/amd64/Win2008R2/qxldd.dll
/usr/share/virtio-win/drivers/amd64/Win2008R2/netkvm.cat
/usr/share/virtio-win/drivers/amd64/Win2008R2/netkvm.inf
/usr/share/virtio-win/drivers/amd64/Win2008R2/netkvm.sys
/usr/share/virtio-win/drivers/amd64/Win2008R2/vioscsi.cat
/usr/share/virtio-win/drivers/amd64/Win2008R2/vioscsi.inf
/usr/share/virtio-win/drivers/amd64/Win2008R2/vioscsi.sys
/usr/share/virtio-win/drivers/amd64/Win2008R2/viostor.cat
/usr/share/virtio-win/drivers/amd64/Win2008R2/viostor.inf
/usr/share/virtio-win/drivers/amd64/Win2008R2/viostor.sys

    An this is an extract of the files in the upstream package https://launchpad.net/kvm-guest-drivers-windows/+download
     
    ./serial/server_2008
    ./serial/server_2008/amd64
    ./serial/server_2008/amd64/trans.tbl
    ./serial/server_2008/amd64/vioser.cat
    ./serial/server_2008/amd64/vioser.inf
    ./serial/server_2008/amd64/vioser.sys
    ./serial/server_2008/amd64/vioser_test.exe
    ./serial/server_2008/amd64/wdfcoinstaller01009.dll
    ./serial/server_2008/trans.tbl
    ./serial/server_2008/x86
    ./serial/server_2008/x86/trans.tbl
    ./serial/server_2008/x86/vioser.cat
    ./serial/server_2008/x86/vioser.inf
    ./serial/server_2008/x86/vioser.sys
    ./serial/server_2008/x86/vioser_test.exe
    ./serial/server_2008/x86/wdfcoinstaller01009.dll
     
     
vioser is missing in downstream package

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Download the specified packages
2. compare it
3.

Actual results:
vioser is missing

Expected results:
vioser present, its necessary to install qemu-guest-agent-win

Comment 2 Ladi Prosek 2017-03-03 08:52:36 UTC
Hi,

(In reply to Eduard Barrera from comment #0)
>     An this is an extract of the files in the upstream package
> https://launchpad.net/kvm-guest-drivers-windows/+download

It looks like the author of this package decided to include the vioserial driver directly. The RHEL package does this only for NetKVM, QXL, vioscsi and viostor, everything else is available in the .ISO. The rationale is that all but boot-critical drivers are expected to be installed by attaching the .ISO to the VM anyway.

If you need to extract the vioserial driver on the host, you can do so by running:

$ sudo mount -o loop /usr/share/virtio-win/virtio-win.iso /mnt/myiso
mount: /dev/loop0 is write-protected, mounting read-only
$ ls -l /mnt/myiso/vioserial/2k8R2/amd64/
total 3094
-r--r--r--.  2 root root   10260 Aug 30  2016 vioser.cat
-r-xr-xr-x.  2 root root    3070 Aug 11  2016 vioser.inf
-r-xr-xr-x.  2 root root 1363968 Aug 11  2016 vioser.pdb
-r-xr-xr-x.  2 root root   68168 Aug 11  2016 vioser.sys
-r-xr-xr-x. 14 root root 1721576 Mar 30  2015 WdfCoInstaller01009.dll

Comment 3 lijin 2017-03-07 06:24:28 UTC
close this bug as this is by design(comment#2)


Note You need to log in before you can comment on or make changes to this bug.