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.
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/RHBA-2011-1513.html
Description of problem: # In the following code, replace "database" with the name # of any running 64 bit guest: perl -MSys::Virt -MSys::Virt::Domain -e ' $vmm = Sys::Virt->new(); $dom = $vmm->get_domain_by_name ("database"); $data = $dom->memory_peek ("0xffffffff81000000", 65536, 1); ' Version-Release number of selected component (if applicable): libvirt-0.8.7-18.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Run the above Perl code. 2. 3. Actual results: libvirt error code: 1, message: internal error unable to execute QEMU command 'memsave': Could not open '/var/cache/libvirt/qemu/qemu.mem.aDwa3V' Expected results: It should be able to run the command. Additional info: Fixed upstream with: http://libvirt.org/git/?p=libvirt.git;a=commit;h=bb12a63909a85c7bf7dac20fb593b6786c78d455 http://libvirt.org/git/?p=libvirt.git;a=commit;h=aa6e7fb40861c6583534179822db1f32800cdfd5 http://libvirt.org/git/?p=libvirt.git;a=commit;h=ee9ceb3295e8e68da4c5838c57cc3c1e3a5dccfb