Bug 1411092
| Summary: | 4K virtual drives broken on Windows | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vadim Rozenfeld <vrozenfe> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | unspecified | CC: | ailan, apagan, chayang, ghammer, juzhang, lijin, lmiksik, lprosek, michen, phou, virt-bugs, virt-maint, vrozenfe, wyu, xiagao, yvugenfi |
| Version: | 7.4 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The viostor driver stores the wrong value in the driver extension for the last LBA.
Consequence: Windows is unable to format 4k-sector virtual disk.
Fix: The viostor driver correctly populates the last LBA driver extension field.
Result: Windows can work with 4k-sector virtual disks.
|
Story Points: | --- |
| Clone Of: | 1410964 | Environment: | |
| Last Closed: | 2017-08-01 12:55:38 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: | |||
| Bug Depends On: | 1410964 | ||
| Bug Blocks: | |||
|
Description
Vadim Rozenfeld
2017-01-08 10:49:37 UTC
Please try drivers from build130 http://download.eng.bos.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/130/win/virtio-win-prewhql-0.1.zip QE can reproduce this issue according to https://bugzilla.redhat.com/show_bug.cgi?id=1410964#c3 Verify this issue with virtio-win-prewhql-130 on win2012R2,disks can be formatted correctly with 4k logical_block_size. So this issue has been fixed,change status to verified. Hi Amnon, Could you help to ack? Thanks 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-2017:2341 |