Bug 1016433

Summary: win8 64 guest s3 fails
Product: Red Hat Enterprise Linux 7 Reporter: Shaolong Hu <shu>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: acathrow, bcao, bsarathy, juzhang, lersek, mdeng, michen, mkenneth, mkrcmari, qzhang, rhod, vbenes, virt-bugs, virt-maint
Target Milestone: rc   
Target Release: 7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-11 13:08:10 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: 923626    

Description Shaolong Hu 2013-10-08 07:36:56 UTC
Description of problem:
-------------------------
win8 64 guest fails to enter s3 status, info status shows guest still running.


Version-Release number of selected component (if applicable):
-----------------------------------------------------------------
virtio-win-1.6.6-1.el6
qxlwddm-0.2-1
qemu-kvm-rhev-0.12.1.2-2.406.el6.x86_64


How reproducible:
---------------------
100%


Steps to Reproduce:
---------------------
1.CMD:

/usr/libexec/qemu-kvm -enable-kvm -M rhel6.5.0 -smp 4 -m 4G -name rhel6.3-64 -uuid 3f2ea5cd-3d29-48ff-aab2-23df1b6ae213 -drive file=win8-64-virtio.qcow2,cache=none,if=none,rerror=stop,werror=stop,id=drive-virtio-disk0,format=qcow2,aio=native -device virtio-blk-pci,drive=drive-virtio-disk0,id=device-virtio-disk0,bootindex=1 -netdev tap,script=/etc/qemu-ifup,id=netdev0 -device virtio-net-pci,netdev=netdev0,id=device-net0,mac=aa:54:00:11:22:33 -boot order=cd -monitor stdio -readconfig ich9-ehci-uhci.cfg -device usb-tablet,id=input0 -chardev socket,id=s1,path=/tmp/s1,server,nowait -device isa-serial,chardev=s1 -monitor tcp::1234,server,nowait -device usb-hub,id=hub -device usb-storage,drive=drive-usb1,id=device-usb1,removable=on -drive  file=disk1,if=none,id=drive-usb1,media=disk,format=qcow2,cache=none,aio=threads -device usb-kbd,id=usb-kbd -device usb-mouse,id=usb-mouse -vga qxl -global qxl-vga.revision=3 -spice port=5920,disable-ticketing -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0

2. choose behavior of close computer button to "sleep"

3. 
(qemu) system_powerdown 


Actual results:
-----------------
guest hangs, black screen, info status shows guest always in running status.

Comment 2 Qunfang Zhang 2013-10-08 08:23:08 UTC
We are using qxlwddm-0.2-1 for the guest qxl driver, please help change component if it's driver issue.

Comment 3 Ademar Reis 2013-10-08 13:48:24 UTC
See also Bug 1016429

Comment 5 Laszlo Ersek 2014-01-02 14:48:22 UTC
There's some more data that could help identify the problem: under QXL KMDOD properties / Details, I have:
- Status = DN_HAS_PROBLEM | DN_DISABLEABLE | DN_NT_ENUMERATOR | DN_NT_DRVIER
- Problem Code = 0x2B
- Problem Status = 0x0

Comment 6 Laszlo Ersek 2014-01-02 20:38:55 UTC
I think I have at least one good reason why the most recent (0.3) driver won't work on a basic OVMF build. The source contains calls to x86BiosCall() on the driver/device initialization path.

OVMF (and UEFI firmware in general) doesn't need to provide a VGA BIOS. It can, optionally, with a CSM (Compatibility Support Module), but it's not required.

Version 0.2 of qxlwddm was apparently not tied to a VGA BIOS. Is the new dependency in 0.3 unavoidable? Thank you.

Comment 7 Vadim Rozenfeld 2014-01-02 22:03:29 UTC
(In reply to Laszlo Ersek from comment #6)
> I think I have at least one good reason why the most recent (0.3) driver
> won't work on a basic OVMF build. The source contains calls to x86BiosCall()
> on the driver/device initialization path.
> 
> OVMF (and UEFI firmware in general) doesn't need to provide a VGA BIOS. It
> can, optionally, with a CSM (Compatibility Support Module), but it's not
> required.
> 
> Version 0.2 of qxlwddm was apparently not tied to a VGA BIOS. Is the new
> dependency in 0.3 unavoidable? Thank you.

Unfortunately yes, in VGA mode I don't have any other options to restore the resolution
after returning from S3 either then calling Int10 or any appropriated ACPI method.
This problem will be fixed after adding support for QXL mode.

Comment 8 Vadim Rozenfeld 2014-01-02 22:08:20 UTC
Changing the status. The driver is available at https://brewweb.devel.redhat.com/buildinfo?buildID=323507

It is not required to specify qxl-vga.revision=3 anymore.

Thanks,
Vadim.

Comment 10 Min Deng 2014-02-21 05:03:08 UTC
(In reply to Vadim Rozenfeld from comment #8)
> Changing the status. The driver is available at
> https://brewweb.devel.redhat.com/buildinfo?buildID=323507
> 
> It is not required to specify qxl-vga.revision=3 anymore.
> 
> Thanks,
> Vadim.

Hi Vadim,
   I still hit the same issue on win8-32 guest could you please double check ? 
Thanks
Min

Comment 11 Vadim Rozenfeld 2014-02-21 10:48:02 UTC
(In reply to dengmin from comment #10)
> (In reply to Vadim Rozenfeld from comment #8)
> > Changing the status. The driver is available at
> > https://brewweb.devel.redhat.com/buildinfo?buildID=323507
> > 
> > It is not required to specify qxl-vga.revision=3 anymore.
> > 
> > Thanks,
> > Vadim.
> 
> Hi Vadim,
>    I still hit the same issue on win8-32 guest could you please double check
> ? 

Hi Min,
Do you mean that that you cannot enter S3 on win8-32 guest even with qxl driver installed?

Thanks,
Vadim.

> Thanks
> Min

Comment 13 Ronen Hod 2014-08-07 08:00:54 UTC
QE,
Vadim will build a new driver in a week or so. Can you retest

Comment 15 Mike Cao 2014-08-11 13:08:10 UTC

*** This bug has been marked as a duplicate of bug 1035963 ***