RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1035963 - [wddm-qxl]win8-32 do s3 fail and guest became black screen and it could not be resumed.
Summary: [wddm-qxl]win8-32 do s3 fail and guest became black screen and it could not b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1016433 (view as bug list)
Depends On:
Blocks: Virt-S3/S4-7.0
TreeView+ depends on / blocked
 
Reported: 2013-11-29 03:22 UTC by Min Deng
Modified: 2015-03-04 05:42 UTC (History)
18 users (show)

Fixed In Version: qxlwddm-0.1-6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-04 05:42:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
setupapilog (74.26 KB, text/plain)
2014-04-03 07:43 UTC, Min Deng 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1016433 0 medium CLOSED win8 64 guest s3 fails 2021-02-22 00:41:40 UTC

Internal Links: 1016433

Description Min Deng 2013-11-29 03:22:37 UTC 
Description of problem:
win8-32 do s3 fail and guest became black screen and it could not be resumed back.

Version-Release number of selected component (if applicable):
kernel-3.10.0-53.el7.x86_64
qemu-kvm-rhev-0.12.1.2-2.415.el6.x86_64
qxlwddm-0.2-1
seabios-bin-1.7.2.2-4.el7.noarch
How reproducible:
4 times

Steps to Reproduce:
1.boot up guest 
  /usr/libexec/qemu-kvm -M pc -cpu host -enable-kvm -m 4G -smp 2 -name win8-32-nerkvm -rtc base=localtime,clock=host,driftfix=slew -uuid 816c2e3d-e84f-4de9-b919-7d1cfd226b6d -monitor stdio -drive file=win8-32.qcow3,if=none,id=drive-data-disk2,format=qcow2,cache=none,werror=stop,rerror=stop -device ide-drive,drive=drive-data-disk2,id=systemos -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device virtio-net-pci,netdev=hostnet0,mac=00:32:52:41:31:31,id=net1,mq=on -cdrom /usr/share/virtio-win/virtio-win-1.6.7.iso -spice id=on,disable-ticketing,port=5931 -vga qxl -global qxl-vga.revision=3 -chardev socket,id=abc,path=/tmp/monitor-win8-64-scsi-73,server,nowait -mon chardev=abc,mode=readline
2.login guest and do S3
3.

Actual results:
The guest can do s3 and also can resume correctly.

Expected results:
After do s3 guest became black screen and user could not resume it successfully except that user execute "system_reset" in monitor.

Additional info:
Comment 4 Vadim Rozenfeld 2014-01-02 22:12:35 UTC 
Could you please give a try to a new driver, available at
https://brewweb.devel.redhat.com/buildinfo?buildID=323507

Thanks,
Vadim.
Comment 8 Ronen Hod 2014-03-25 11:03:38 UTC 
Vladimir Benes,
Please provide info, why you moved it to NEW? What do you see, how can it be reproduced ...
Comment 19 Mike Cao 2014-03-31 05:56:54 UTC 
mdeng ,pls help to verify it ,thanks
Comment 20 lijin 2014-04-03 05:53:09 UTC 
win2k12r2 hit the same issue when do s3 with qxlwddm-0.3-2

steps same as comment0,so this issue has not been fixed.
Comment 21 Mike Cao 2014-04-03 06:29:22 UTC 
Reassigned based on comment @20
Comment 22 Min Deng 2014-04-03 07:01:23 UTC 
 Re-test the bug on win8.1-32 guest and the issue still could be reproduced.
build info,
qemu-kvm-rhev-1.5.3-53.el7.x86_64
kernel-3.10.0-113.el7.x86_64
qxlwddm-0.3-2
Comment 23 Vadim Rozenfeld 2014-04-03 07:16:22 UTC 
(In reply to dengmin from comment #22)
>  Re-test the bug on win8.1-32 guest and the issue still could be reproduced.
> build info,
> qemu-kvm-rhev-1.5.3-53.el7.x86_64
> kernel-3.10.0-113.el7.x86_64
> qxlwddm-0.3-2

Hi Min,
Could you please post the following information:
- seabios version,
- qemu command line,
- setupapi log file
- screen capture image.

Thanks,
Vadim.
Comment 25 Min Deng 2014-04-03 07:43:48 UTC 
Created attachment 882133 [details]
setupapilog
Comment 27 Vadim Rozenfeld 2014-04-03 10:41:02 UTC 
(In reply to dengmin from comment #25)
> Created attachment 882133 [details]
> setupapilog

Could you please upload setupapi.dev.log file as well?

thanks,
Vadim.
Comment 29 Ronen Hod 2014-08-07 08:02:41 UTC 
Probably a duplicate of bug 1016433
Comment 30 Mike Cao 2014-08-11 13:08:10 UTC 
*** Bug 1016433 has been marked as a duplicate of this bug. ***
Comment 32 Mike Cao 2014-08-25 02:36:17 UTC 
mdeng ,pls help to verify it
Comment 36 Qian Guo 2014-12-29 06:46:26 UTC 
Can reproduce this bug in an AMD host:
# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                16
On-line CPU(s) list:   0-15
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             2
NUMA node(s):          4
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 2
Model name:            AMD Opteron(tm) Processor 6320
Stepping:              0
CPU MHz:               2800.000
BogoMIPS:              5585.37
Virtualization:        AMD-V
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
L3 cache:              6144K
NUMA node0 CPU(s):     0,2,4,6
NUMA node1 CPU(s):     8,10,12,14
NUMA node2 CPU(s):     1,3,5,7
NUMA node3 CPU(s):     9,11,13,15




The cli I used like this:
# /usr/libexec/qemu-kvm -enable-kvm -cpu Opteron_G5,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_time -sandbox off -m 4G -smp 4 -name win2012  -boot menu=on -spice disable-ticketing,port=5910 -vga qxl -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -global qxl-vga.revision=3 -drive file=/home/win8.qcow2,format=qcow2,if=none,id=blk0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=blk0,id=dev-blk0 -monitor stdio -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,mac=00:11:29:2c:45:23,bus=pci.0,addr=0x9,id=net0 -qmp tcp:0:4444,server,nowait 

The netkvm and virtio-blk are installing driver :virtio-win-1.7.2-2.el6.noarch

install qxl driver qxlwddm-0.1-6 

Do s3 inside guest, guest access black window, and can not resume, after reboot, it resumed.

Addtional info:
Jin li helped test in an intel host, not hit such issue.
(qemu-kvm-rhev-2.1.2-17.el7.x86_64 and kenel-3.10.0-219.el7.x86_64)

Can reproduce it just with ide and e1000 network card.

THe

I will reopen this bug, feel free to change it and please leave a comment.

Thanks.
Comment 37 Vadim Rozenfeld 2014-12-29 07:45:49 UTC 
Could you try qxl-vga.revision=4 ?

Thanks,
Vadim.
Comment 38 Qian Guo 2014-12-29 08:25:21 UTC 
(In reply to Vadim Rozenfeld from comment #37)
> Could you try qxl-vga.revision=4 ?
> 
> Thanks,
> Vadim.
if use qxl-vga.revision=4 , it can resume back.

Thanks.
Comment 39 Vadim Rozenfeld 2014-12-29 08:41:11 UTC 
(In reply to Qian Guo from comment #38)
> (In reply to Vadim Rozenfeld from comment #37)
> > Could you try qxl-vga.revision=4 ?
> > 
> > Thanks,
> > Vadim.
> if use qxl-vga.revision=4 , it can resume back.
> 
> Thanks.

Thanks.
I will check why S3 doesn't work in VGA mode.
Does it happen with virtio drivers also?
Do you use the default screen resolution (1024x768) ?

Vadim.
Comment 40 Qian Guo 2014-12-29 08:58:13 UTC 
(In reply to Vadim Rozenfeld from comment #39)
> (In reply to Qian Guo from comment #38)
> > (In reply to Vadim Rozenfeld from comment #37)
> > > Could you try qxl-vga.revision=4 ?
> > > 
> > > Thanks,
> > > Vadim.
> > if use qxl-vga.revision=4 , it can resume back.
> > 
> > Thanks.
> 
> Thanks.
> I will check why S3 doesn't work in VGA mode.
> Does it happen with virtio drivers also?
Not exactly sure your meaning here~~~

I tested with virtio-net and virtio-blk combined and also ide and e1000, both hit

> Do you use the default screen resolution (1024x768) ?

Yes, I use the default resolution
> 
> Vadim.
Comment 41 Vadim Rozenfeld 2014-12-29 09:04:45 UTC 
(In reply to Qian Guo from comment #40)
> (In reply to Vadim Rozenfeld from comment #39)
> > (In reply to Qian Guo from comment #38)
> > > (In reply to Vadim Rozenfeld from comment #37)
> > > > Could you try qxl-vga.revision=4 ?
> > > > 
> > > > Thanks,
> > > > Vadim.
> > > if use qxl-vga.revision=4 , it can resume back.
> > > 
> > > Thanks.
> > 
> > Thanks.
> > I will check why S3 doesn't work in VGA mode.
> > Does it happen with virtio drivers also?
> Not exactly sure your meaning here~~~
> 
> I tested with virtio-net and virtio-blk combined and also ide and e1000,
> both hit

So, it happens with any combination of virtio and emulated
network and storage devices, right?

> 
> > Do you use the default screen resolution (1024x768) ?
> 
> Yes, I use the default resolution
> > 
> > Vadim.
Comment 42 Qian Guo 2014-12-29 09:12:39 UTC 
(In reply to Vadim Rozenfeld from comment #41)
> (In reply to Qian Guo from comment #40)
> > (In reply to Vadim Rozenfeld from comment #39)
> > > (In reply to Qian Guo from comment #38)
> > > > (In reply to Vadim Rozenfeld from comment #37)
> > > > > Could you try qxl-vga.revision=4 ?
> > > > > 
> > > > > Thanks,
> > > > > Vadim.
> > > > if use qxl-vga.revision=4 , it can resume back.
> > > > 
> > > > Thanks.
> > > 
> > > Thanks.
> > > I will check why S3 doesn't work in VGA mode.
> > > Does it happen with virtio drivers also?
> > Not exactly sure your meaning here~~~
> > 
> > I tested with virtio-net and virtio-blk combined and also ide and e1000,
> > both hit
> 
> So, it happens with any combination of virtio and emulated
> network and storage devices, right?

Yes according to comment 40

> 
> > 
> > > Do you use the default screen resolution (1024x768) ?
> > 
> > Yes, I use the default resolution
> > > 
> > > Vadim.
Note You need to log in before you can comment on or make changes to this bug.