| Summary: | [virtio-win][balloon]need create a win2k8R2 folder for balloon driver in virtio-win-1.6.7-2 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | lijin <lijin> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5 | CC: | bcao, bsarathy, chayang, jkurik, juzhang, lveyde, michen, mikeb, pm-rhel, rbalakri, rhod, vrozenfe |
| Target Milestone: | rc | Keywords: | Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virtio-win-1.6.8-4.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: in the previous version of virtio-win package
Balloon driver has no win2k8R2 folder
Consequence: This fact creates some sort of layout inconsistency between Balloon and the rest of virtio-win drivers.
Fix: Add missing folder.
Result: Now all virtio-win drivers have the same, uniform layout.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 08:20:48 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1079901 | ||
|
Description
lijin
2013-10-30 10:05:46 UTC
Verified this issue on virtio-win-1.6.8-2.el6,win2k8R2 driver folder for balloon does exist. Based on above ,this issue has been fixed already. Request for PM_ACK and backport to rhel6.5.z , unluckily I have no persmission to raise rhel6.5.z flag ,anyone can make it ? Thanks, referring to comment #11 Verified this issue on virtio-win-1.6.8-5.el7.noarch [root@dhcp-9-181 Balloon]# ls 2k12 2k12R2 2k3 2k8 2k8R2 w7 w8 w8.1 xp Based on above ,this issue has been fixed ald PM ,pls help to grant pm ack flag 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. http://rhn.redhat.com/errata/RHBA-2014-1592.html |