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: kernelAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.0CC: 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
Description of problem:
Started with DF* jobs failed because WIN7-32 and Win7-64 guest hang if guests rebooting during test stage
Version-Release number of selected component (if applicable):
build 75
kernel-3.10.0-111.el7.x86_64
qemu-kvm-rhev-1.5.3-53.el7.x86_64
How reproducible:
3 times
Steps to Reproduce:
1.boot up guest with 
  /usr/libexec/qemu-kvm -M pc -m 2G -smp 2 -cpu Nehalem,+x2apic,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic,hv_time -usb -device usb-tablet -drive file=win7-32.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup1 -device e1000,netdev=hostnet0,mac=00:42:45:38:44:12,id=net0 -uuid 3122984b-7e74-4afa-8dc0-66cecf65aea4 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=a,path=/tmp/monitor-win7-32-serial,server,nowait -mon chardev=a,mode=readline -name win732-serial -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 -chardev pty,id=channel0 -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0 -vnc :1 -vga cirrus -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=0 -monitor stdio
2.submit the job 
  for example,
   win7-64,DF-PNP Rebalance Request New Resources Device Test...
   Win7-32,DF-PNP Stop ...
3.

Actual results:
The guest could not boot up correctly and it hang up so the following jobs could not continue.
-cpu Nehalem,+x2apic,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic,hv_time - *reproduce
-cpu Nehalem,+x2apic,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic, - *not reproduce


Expected results:
The job could pass with hv_time flag.

Additional info:

Comment 2 Ronen Hod 2014-03-19 08:40:44 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).

Comment 4 Min Deng 2014-11-14 05:26:56 UTC
  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.

Comment 5 Ronen Hod 2014-11-19 16:12:53 UTC
Since it is already solved, Moving back to 7.1, ON_QA

Comment 6 juzhang 2014-11-24 01:45:44 UTC
According to comment4, set this bz as verified.

Comment 8 errata-xmlrpc 2015-03-05 05:33:52 UTC
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