Bug 1078089
Summary: | [hv_time][[WHQL]Started with DF jobs failed because WIN7-32 and Win7-64 guest hang if guests rebooting during test stage | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Min Deng <mdeng> |
Component: | kernel | Assignee: | Vadim Rozenfeld <vrozenfe> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 7.0 | CC: | bcao, hhuang, juzhang, knoel, mdeng, michen, pbonzini, rbalakri, virt-bugs, virt-maint, vrozenfe |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
WHQL cannot pass DF jobs on Windows 7 guest, because guest failed to resume when started with hv_time flag enabled.
Consequence:
Enabling hv_time flag prevent Windows 7 guest from successful resuming, when running WHQL DF jobs.
Fix:
Update kernel, qemu and virtio-win drivers with the most recent ones.
Update
Result:
DF jobs can be passed on Windows 7 guest with hv_time flag enabled.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-03-05 05:33:52 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: | |||
Bug Blocks: | 833649 |
Description
Min Deng
2014-03-19 07:17:08 UTC
Since we have the option not to use hv_time, and the default is that it is off, this is not a very urgent 7.0.0 blocker. Deferring to 7.1 (and 7.0.z for now). QE re-run the jobs on win7-32 and win7-64 guest for virtio serial build info, kernel-3.10.0-200.el7.x86_64 qemu-kvm-rhev-2.1.2-7.el7.x86_64 virtio-win-prewhql-0.1-93 All the jobs named by DF* have passed on win7-32/64 guest with flag '-cpu Nehalem,+x2apic,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic,hv_time' so the original issue has been fixed,thanks. Since it is already solved, Moving back to 7.1, ON_QA 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://rhn.redhat.com/errata/RHBA-2015-0289.html |