Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When do s4 on win7.32 guest,the spice window keeps black,and the qemu monitor stay active,when (qemu) info status,it displays:"VM status: running".
After quit in qemu monitor and boot the guest again,guest can *Resume* successfully,it seems that guest do s4 successfully.
Version-Release number of selected component (if applicable):
host:RHEL-7.0-20130306.0
kernel-3.8.0-0.40.el7.x86_64
qemu-kvm-1.4.0-1.el7.x86_64
virtio-win-1.6.3-3.el6.noarch
guest:win7.32
How reproducible:
always
Steps to Reproduce:
1.boot a guest with following command:
/usr/libexec/qemu-kvm -drive file=/home/whql-test/win7-32-virtio.qcow2,if=virtio,cache=writethrough,media=disk,format=qcow2,id=disk1 -netdev tap,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:56,bus=pci.0 -monitor stdio -boot menu=on -spice port=5902,disable-ticketing -vga qxl -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -usb -device usb-tablet,id=tablet1 -M pc-i440fx-1.4 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2 -m 2G -enable-kvm -fda /usr/share/virtio-win/virtio-win-1.6.3_x86.vfd -cdrom /usr/share/virtio-win/virtio-win-1.6.3.iso
2.do s4 on guest
3.resume guest
Actual results:
after step2,the spice window keep black screen,and (qemu) info status,it shows:VM status: running.Quit in qemu monitor and boot guest,it prompts "resuming windows".
Expected results:
guest do s4 and resume successfully
Additional info:
(In reply to comment #2)
> Hi lijin,
>
> What version is the qxl driver in the guest? it is visible in control
> center -> device manager, thanks.
>
> Alon
Hi,Alon
the driver version of Red Hat QXL GPU is 6.1.0.10016
Hit this issue w/ windows 7.32 guest,
Components:
qxl driver is from brewweb, and version is qxl-win-0.1-17
virtio-win-prewhql-58
After do S4, the guest can not finish the S4 state, and in host, found that the qemu-kvm process consumes lots cpu resources.
# top -p $pid_of_qemu
top - 13:28:31 up 19:06, 4 users, load average: 4.10, 3.80, 2.64
Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie
%Cpu(s): 20.1 us, 5.0 sy, 0.0 ni, 74.7 id, 0.0 wa, 0.1 hi, 0.1 si, 0.0 st
KiB Mem: 24393884 total, 14552832 used, 9841052 free, 1212 buffers
KiB Swap: 12328956 total, 0 used, 12328956 free, 10582092 cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
20754 root 20 0 8407756 3.095g 6900 S 398.9 13.30 40:54.14 qemu-kvm
Hope helpful.
*** Bug 954341 has been marked as a duplicate of this bug. ***
Comment 7RHEL Program Management
2014-03-22 06:56:51 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.