ubuntu18.04 - qemu segfaults when tries to dump-guest-memory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Low
|
Canonical Server | ||
qemu (Ubuntu) |
Fix Released
|
Low
|
Ubuntu on IBM Power Systems Bug Triage |
Bug Description
---Problem Description---
qemu segfaults when tried to dump-guest-memory
---uname output---
Linux ltc-boston122 4.13.0-12-generic #13-Ubuntu SMP Fri Sep 22 20:52:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = PowerNV 5104-22C
---Steps to Reproduce---
1. Run the following commands
# qemu-system-ppc64 -M none -nographic -m 256
QEMU 2.10.0 monitor - type 'help' for more information
(qemu) dump-guest-memory /dev/null
Segmentation fault
== Comment: #1 - NAGESWARA R. SASTRY <email address hidden> - 2017-10-08 23:06:29 ==
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64
Core was generated by `qemu-system-ppc64 -M none -nographic -m 256 '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000001cea97af410 in object_get_class ()
[Current thread is 1 (Thread 0x798c498ef7e0 (LWP 49591))]
(gdb) bt
#0 0x000001cea97af410 in object_get_class ()
#1 0x000001cea952ce30 in cpu_get_dump_info ()
#2 0x000001cea93c1d48 in qmp_dump_
#3 0x000001cea95afae8 in hmp_dump_
#4 0x000001cea93a5c98 in ?? ()
#5 0x000001cea93a60ec in ?? ()
#6 0x000001cea98f7388 in readline_
#7 0x000001cea93a5ff8 in ?? ()
#8 0x000001cea98541f0 in ?? ()
#9 0x000001cea984dc94 in qemu_chr_be_write ()
Backtrace stopped: frame did not save the PC
(gdb) i r
r0 0x1cea93c1d48 1987114179912
r1 0x7fffd5f06920 140736782690592
r2 0x1cea9c07900 1987122854144
r3 0x0 0
r4 0x1cea993c000 1987119923200
r5 0x1cea9942db8 1987119951288
r6 0xe3 227
r7 0x1cea9942d58 1987119951192
r8 0x10000000 268435456
r9 0x0 0
r10 0x0 0
r11 0x0 0
r12 0x4000 16384
r13 0x798c498f6f40 133643436519232
r14 0x6 6
r15 0x1cea99d37d0 1987120543696
r16 0x7fffd5f06de0 140736782691808
r17 0x1 1
r18 0x0 0
r19 0x1cea99fee28 1987120721448
r20 0x1cecf558b20 1987753380640
r21 0x1cea9c97900 1987123443968
r22 0x0 0
r23 0x1cea9c97900 1987123443968
r24 0x0 0
r25 0x1cea9c8fac0 1987123411648
r26 0x1cea9c8faf0 1987123411696
r27 0x0 0
r28 0x1cea9942d58 1987119951192
r29 0x1cea9942db8 1987119951288
r30 0x1cea993c000 1987119923200
r31 0x1cea9c8fad8 1987123411672
pc 0x1cea97af410 0x1cea97af410 <object_get_class>
msr 0x900000000000f033 103762935414616
cr 0x28024242 671236674
lr 0x1cea952ce30 0x1cea952ce30 <cpu_get_
ctr 0x798c49cb1a70 133643440429680
xer 0x0 0
orig_r3 0x1cea952ce2c 1987115666988
trap 0x300 768
== Comment: #3 - Vaishnavi Bhat <email address hidden> - 2017-10-09 05:48:09 ==
This issue is already fixed upstream:
https:/
The new behavior is to reject dump when you don't have a CPU:
(qemu) dump-guest-memory /dev/null
this feature or command is not currently supported
== Comment: #4 - Vaishnavi Bhat <email address hidden> - 2017-10-09 06:25:34 ==
Verified with the upstream qemu -
# ./qemu-system-ppc -M none -nographic -m 256
QEMU 2.10.50 monitor - type 'help' for more information
(qemu) dump-guest-memory /dev/null
this feature or command is not currently supported
(qemu)
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
assignee: | nobody → Canonical Server Team (canonical-server) |
tags: | added: triage-g |
Changed in ubuntu-power-systems: | |
status: | New → Triaged |
Changed in qemu (Ubuntu): | |
milestone: | none → ubuntu-18.04 |
summary: |
- ubuntu17.10 - qemu segfaults when tries to dump-guest-memory + ubuntu18.04 - qemu segfaults when tries to dump-guest-memory |
Changed in ubuntu-power-systems: | |
importance: | High → Low |
Changed in ubuntu-power-systems: | |
status: | Triaged → Fix Released |
tags: |
added: targetmilestone-inin1804 removed: targetmilestone-inin1710 |
Default Comment by Bridge