Bug 1535584
Summary: | [virtio-win] split floppy image to avoid the "no space left" error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Danilo de Paula <ddepaula> |
Component: | virtio-win | Assignee: | Danilo de Paula <ddepaula> |
virtio-win sub component: | distribution | QA Contact: | Virtualization Bugs <virt-bugs> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | ailan, crobinso, jen, jherrman, juzhang, lijin, lmiksik, lveyde, michal.skrivanek, mpoledni, mtessun, sbonazzo, virt-bugs, vrozenfe |
Version: | 7.5 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 06:33:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Danilo de Paula
2018-01-17 16:33:34 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. (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 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. 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 |