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 869496 - screendump wont save PPM image file if qemu-kvm booted with '-S'
Summary: screendump wont save PPM image file if qemu-kvm booted with '-S'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Amos Kong
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-24 05:34 UTC by Xiaoqing Wei
Modified: 2015-05-25 00:06 UTC (History)
15 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.361.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 05:54:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1553 0 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2013-11-20 21:40:29 UTC

Description Xiaoqing Wei 2012-10-24 05:34:19 UTC 
Description of problem:

screendump wont save PPM image file if qemu-kvm booted with '-S'

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.330.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot a guest w/ '-S' option, then do screendump
[root@rhel6xwei virtlab_logs]# ls /home/hello
ls: cannot access /home/hello: No such file or directory
[root@rhel6xwei virtlab_logs]# qemu-kvm -monitor stdio -S -M rhel6.4.0
VNC server running on `::1:5900'
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) screendump /home/hello
(qemu) q
[root@rhel6xwei virtlab_logs]# ls /home/hello
ls: cannot access /home/hello: No such file or directory
[root@rhel6xwei virtlab_logs]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.330.el6.x86_64

Actual results:
PPM image file did't saved.

Expected results:
PPM image file saved.

Additional info:

1) Tried same steps w/ upstream qemu-kvm, PPM image file saved.
[root@localhost ~]# ls /home/hello 
ls: cannot access /home/hello: No such file or directory
[root@localhost ~]# qemu-system-x86_64 -monitor stdio -M pc-1.3 -S
VNC server running on `::1:5900'
QEMU 1.2.50 monitor - type 'help' for more information
(qemu) screendump /home/hello
(qemu) q
[root@localhost ~]# ls /home/hello 
/home/hello


2) If 'cont' then 'stop', then try 'screendump', file will be saved.
[root@rhel6xwei virtlab_logs]# ls /home/hello
ls: cannot access /home/hello: No such file or directory
[root@rhel6xwei virtlab_logs]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.330.el6.x86_64
[root@rhel6xwei virtlab_logs]# ls /home/hello
ls: cannot access /home/hello: No such file or directory
[root@rhel6xwei virtlab_logs]# qemu-kvm -monitor stdio -S -M rhel6.4.0
VNC server running on `::1:5900'
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) cont
(qemu) stop
(qemu) info status 
VM status: paused
(qemu) screendump /home/hello
(qemu) q
[root@rhel6xwei virtlab_logs]# ls /home/hello
/home/hello
Comment 2 Amos Kong 2012-10-31 09:14:30 UTC 
It's not a common usage. Upstream fixed this bug by the commit 9a51f5b0, I tried to backport to qemu-kvm-rhel6, problem can be resolved.

commit 9a51f5b0677381ed87d413e969ea72adf1f17f5f
Author: Gerd Hoffmann <kraxel>
Date:   Fri Feb 24 12:43:43 2012 +0100

    vga: simplify screendump
    
    The displaychangelistener isn't needed at all, we can simply save the
    image when vga_hw_update is done instead of hooking into the update
    process.
    
    Signed-off-by: Anthony Liguori <aliguori.com>

--
Assign this bug to myself.
Comment 3 Amos Kong 2012-10-31 09:44:13 UTC 
Xwei tested with qemu-kvm-0.12.1.2-2.295.el6.x86_64 (rhel-6.3 ga), bug also exists. We are late in 6.4, and it is not a regression, so postpone it.
Comment 11 langfang 2013-06-24 09:25:15 UTC 
Reproduce this bug as following version:
Host
# uname -r 
2.6.32-389.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.356.el6.x86_64


Steps:
1.Boot guest 
# /usr/libexec/qemu-kvm -S -M rhel6.4.0 -cpu Opteron_G4 -monitor stdio

2.Do screendump
...
VNC server running on `::1:5900'
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) screendump /home/hello


Results: the screendump file did't saved.


Verify this bug as following version:
Host
# uname -r
2.6.32-389.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.376.el6.x86_64

Steps as same as reproduce 

Results:The screendump file saved.

According to above test ,this bug fixed.
Comment 16 errata-xmlrpc 2013-11-21 05:54:36 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.

http://rhn.redhat.com/errata/RHSA-2013-1553.html
Note You need to log in before you can comment on or make changes to this bug.