Bug 1594113
Summary: | Error returned after issue {"execute":"guest-fstrim"} cmd for win7-32/64 and win2008-32/64/r2 guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | xiagao |
Component: | virtio-win | Assignee: | Sameeh Jubran <sjubran> |
virtio-win sub component: | qemu-ga-win | QA Contact: | Virtualization Bugs <virt-bugs> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | ddepaula, vrozenfe |
Version: | 7.6 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: |
NO_DOCS
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 16:21:51 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
xiagao
2018-06-22 06:54:00 UTC
Can you please confirm that in this build the issue is fixed? https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16850812 (In reply to Sameeh Jubran from comment #2) > Can you please confirm that in this build the issue is fixed? > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16850812 yes, it is fixed. # nc -U /tmp/qga-win7 {"execute":"guest-fstrim"} {"error": {"class": "GenericError", "desc": "fstrim is only supported for Win8+"}} Verified this bug in build mingw-qemu-ga-win-7.6.0-2.el7ev. virtio-win-prewhql-156 win7-32 guest: {"execute":"guest-fstrim"} {"error": {"class": "GenericError", "desc": "fstrim is only supported for Win8+"}} win10-32 guest: {"execute":"guest-fstrim"} {"return": {"paths": [{"path": "C:\\"}, {"path": "S:\\"}]}} Can we have QA, PM and Release flags for this, please? 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:3413 |