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 1269909 - RFE: Implement dump-guest-memory in qemu-system-aarch64
Summary: RFE: Implement dump-guest-memory in qemu-system-aarch64
Keywords:
Status: CLOSED DUPLICATE of bug 1299867
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Andrew Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1173755
TreeView+ depends on / blocked
 
Reported: 2015-10-08 13:16 UTC by Richard W.M. Jones
Modified: 2016-01-21 14:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-21 14:51:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2015-10-08 13:16:18 UTC
Description of problem:

It's not possible to use the 'virsh dump --memory-only' option on
aarch64 at the moment.  It seems to rely on a qemu feature which is
not implemented (even upstream) on aarch64:

$ virsh dump --memory-only guestfs-b1rs92hpq4izkpvi /tmp/guestfs-b1rs92hpq4izkpvi.core
error: Failed to core dump domain guestfs-b1rs92hpq4izkpvi to
/tmp/guestfs-b1rs92hpq4izkpvi.core
error: internal error: unable to execute QEMU command 'dump-guest-memory': this
feature or command is not currently supported

It would be nice to have this on aarch64, since it's the recommended
way to collect a debugging core dump for Linux guest kernels which
have crashed.  (An alternative is to use kdump in the guest, but that
requires prior setup).

Version-Release number of selected component (if applicable):

I tested this in Rawhide:
qemu-2.4.0-2.fc24.aarch64

IIUC, the problem is that the function 'cpu_get_dump_info' is not
implemented for aarch64 (only for x86, ppc and s390x so far).

Comment 1 Andrew Jones 2016-01-21 14:51:47 UTC

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


Note You need to log in before you can comment on or make changes to this bug.