Bug 1269909 - RFE: Implement dump-guest-memory in qemu-system-aarch64
RFE: Implement dump-guest-memory in qemu-system-aarch64
Status: CLOSED DUPLICATE of bug 1299867
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev (Show other bugs)
7.3
aarch64 Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Andrew Jones
Virtualization Bugs
: FutureFeature
Depends On:
Blocks: 1173755
  Show dependency treegraph
 
Reported: 2015-10-08 09:16 EDT by Richard W.M. Jones
Modified: 2016-01-21 09:51 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-21 09:51:47 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2015-10-08 09:16:18 EDT
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 09:51:47 EST

*** 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.