Bug 584751
Summary: | Win7 guests: cannot enable disk caching on IDE disks | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Yaniv Kaul <ykaul> |
Component: | kvm | Assignee: | chellwig <chellwig> |
Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.5.z | CC: | jkt, kwolf, virt-maint, ykaul |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-05-07 10:41:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yaniv Kaul
2010-04-22 10:49:10 UTC
Note that you never could enabled/disable the write cache under qemu. While return success for the SETFEATURES calls, we never take any action. I suspect the difference is that Win7 issues an IDENTIFY call later to check if we actually advertize a cache now. Note that in recent qemu we will always advertize a write cache, Yaniv, is this serious in any way? Even implementing changing the caching settings is not a high priority, and backporting to RHEL5 certainly isn't. I'm tempted to close this as WONTFIX. I don't think it's serious, except for the user experience, where it appears he can do something, then gets a bit of an ugly error. If you don't want to fix it, close as WONTFIX. I guess there are more important bugs to fix. |