RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1535584 - [virtio-win] split floppy image to avoid the "no space left" error
Summary: [virtio-win] split floppy image to avoid the "no space left" error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Danilo de Paula
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-17 16:33 UTC by Danilo de Paula
Modified: 2018-04-10 06:34 UTC (History)
14 users (show)

Fixed In Version: virtio-win-1.9.4-2.el7
Doc Type: Bug Fix
Doc Text:
To be able to contain all necessary drivers, the Windows 10 floppy image has been split into two architecture-specific files: w10_amd64.vfd and w10_i386.vfd.
Clone Of:
Environment:
Last Closed: 2018-04-10 06:33:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0657 0 None None None 2018-04-10 06:34:32 UTC

Description Danilo de Paula 2018-01-17 16:33:34 UTC 
One floppy (~2.8MB) image was not enough to include all the drivers for amd64.

So each of the images were split into two:
One containing Windows10 drivers and another containing the others.

We're now shipping

virtio-win-1.9.4_amd64.vfd
virtio-win-1.9.4_w10_amd64.vfd


virtio-win-1.9.4_x86.vfd
virtio-win-1.9.4_w10_x86.vfd
Comment 3 lijin 2018-01-18 01:51:33 UTC 
There is no virtio-win-1.9.4_w10_amd64.vfd and virtio-win-1.9.4_w10_x86.vfd

# ll /usr/share/virtio-win/
total 289092
drwxr-xr-x 4 root root        31 Jan 17 20:54 drivers
drwxr-xr-x 2 root root        56 Jan 18 09:40 guest-agent
-rw-r--r-- 1 root root   2949120 Jan 18 09:41 virtio-win-1.9.4_amd64.vfd
-rw-r--r-- 1 root root 290131968 Jan 17 23:28 virtio-win-1.9.4.iso
-rw-r--r-- 1 root root   2949120 Jan 18 09:41 virtio-win-1.9.4_x86.vfd
lrwxrwxrwx 1 root root        26 Jan 18 09:40 virtio-win_amd64.vfd -> virtio-win-1.9.4_amd64.vfd
lrwxrwxrwx 1 root root        20 Jan 18 09:40 virtio-win.iso -> virtio-win-1.9.4.iso
lrwxrwxrwx 1 root root        24 Jan 18 09:40 virtio-win_x86.vfd -> virtio-win-1.9.4_x86.vfd


So re-assign this bug.
Comment 6 Danilo de Paula 2018-01-18 20:48:11 UTC 
(In reply to lijin from comment #3)
> There is no virtio-win-1.9.4_w10_amd64.vfd and virtio-win-1.9.4_w10_x86.vfd
> 
> # ll /usr/share/virtio-win/
> total 289092
> drwxr-xr-x 4 root root        31 Jan 17 20:54 drivers
> drwxr-xr-x 2 root root        56 Jan 18 09:40 guest-agent
> -rw-r--r-- 1 root root   2949120 Jan 18 09:41 virtio-win-1.9.4_amd64.vfd
> -rw-r--r-- 1 root root 290131968 Jan 17 23:28 virtio-win-1.9.4.iso
> -rw-r--r-- 1 root root   2949120 Jan 18 09:41 virtio-win-1.9.4_x86.vfd
> lrwxrwxrwx 1 root root        26 Jan 18 09:40 virtio-win_amd64.vfd ->
> virtio-win-1.9.4_amd64.vfd
> lrwxrwxrwx 1 root root        20 Jan 18 09:40 virtio-win.iso ->
> virtio-win-1.9.4.iso
> lrwxrwxrwx 1 root root        24 Jan 18 09:40 virtio-win_x86.vfd ->
> virtio-win-1.9.4_x86.vfd
> 
> 
> So re-assign this bug.

ops, fixed in virtio-win-1.9.4-2.el7
Comment 7 lijin 2018-01-19 02:17:29 UTC 
Check in virtio-win-1.9.4-2.el7, there are seprate floppy files for windows 10.

# ll /usr/share/virtio-win/
total 294852
drwxr-xr-x 4 root root        31 Jan 17 20:54 drivers
drwxr-xr-x 2 root root        56 Jan 19 10:01 guest-agent
-rw-r--r-- 1 root root   2949120 Jan 19 10:02 virtio-win-1.9.4_amd64.vfd
-rw-r--r-- 1 root root 290131968 Jan 19 03:59 virtio-win-1.9.4.iso
-rw-r--r-- 1 root root   2949120 Jan 19 10:15 virtio-win-1.9.4_w10_amd64.vfd
-rw-r--r-- 1 root root   2949120 Jan 19 10:15 virtio-win-1.9.4_w10_x86.vfd
-rw-r--r-- 1 root root   2949120 Jan 19 10:02 virtio-win-1.9.4_x86.vfd
lrwxrwxrwx 1 root root        26 Jan 19 10:01 virtio-win_amd64.vfd -> virtio-win-1.9.4_amd64.vfd
lrwxrwxrwx 1 root root        20 Jan 19 10:01 virtio-win.iso -> virtio-win-1.9.4.iso
lrwxrwxrwx 1 root root        30 Jan 19 10:01 virtio-win_w10_amd64.vfd -> virtio-win-1.9.4_w10_amd64.vfd
lrwxrwxrwx 1 root root        28 Jan 19 10:01 virtio-win_w10_x86.vfd -> virtio-win-1.9.4_w10_x86.vfd
lrwxrwxrwx 1 root root        24 Jan 19 10:01 virtio-win_x86.vfd -> virtio-win-1.9.4_x86.vfd

So change status to verified.
Comment 9 errata-xmlrpc 2018-04-10 06:33:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0657
Note You need to log in before you can comment on or make changes to this bug.