------- Comment From [email protected] 2026-04-13 06:19 EDT------- Hi team, I have tested the scenario in the latest Ubuntu2604 with crash version - 9.0.1. I am unable to reproduce the issue. Using the latest crash tool, I am able to analyse the vmcore dump generated using virsh dump.
Host and Guest OS: Ubuntu26.04 Host and Guest Kernel: 6.18.0-8-generic crash: crash 9.0.1 Status: Successful - Able to analyse the vmcore generated by virsh dump successfully using crash 9.0.1 provided in Ubuntu26.04 Thanks, Misbah Anjum N ============================ Logs ================================= # virsh dump ubuntu2604 vmcore-memonly901 --memory-only Domain 'ubuntu2604' dumped to vmcore-memonly901 # virsh dump ubuntu2604 vmcore-memonlyby901 --memory-only --bypass-cache Domain 'ubuntu2604' dumped to vmcore-memonlyby901 # virsh dump ubuntu2604 vmcore-memonlyzlib901 --memory-only --format=kdump-zlib Domain 'ubuntu2604' dumped to vmcore-memonlyzlib901 # crash /usr/lib/debug/boot/vmlinux-6.18.0-8-generic vmcore-memonly901 crash 9.0.1 Copyright (C) 2002-2025 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011, 2020-2024 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. Copyright (C) 2015, 2021 VMware, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter "help copying" to see the conditions. This program has absolutely no warranty. Enter "help warranty" for details. GNU gdb (GDB) 16.3 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "powerpc64le-unknown-linux-gnu". Type "show configuration" for configuration details. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... please wait... (gathering module symbol data) WARNING: cannot access vmalloc'd module memory KERNEL: /usr/lib/debug/boot/vmlinux-6.18.0-8-generic DUMPFILE: vmcore-memonly901 CPUS: 10 DATE: Thu Jan 1 00:00:00 UTC 1970 UPTIME: 00:01:33 LOAD AVERAGE: 0.00, 0.00, 0.00 TASKS: 292 NODENAME: localhost RELEASE: 6.18.0-8-generic VERSION: #8-Ubuntu SMP PREEMPT_DYNAMIC Wed Dec 17 15:52:06 UTC 2025 MACHINE: ppc64le (3450 Mhz) MEMORY: 19.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: c0000000038b1580 (1 of 10) [THREAD_INFO: c0000000038b1580] CPU: 0 STATE: TASK_RUNNING (ACTIVE) WARNING: panic task not found crash> bt PID: 0 TASK: c0000000038b1580 CPU: 0 COMMAND: "swapper/0" R0: 0000000044042888 R1: c000000003c77c60 R2: c00000000275a700 R3: 0000000000000000 R4: c000000003bd0600 R5: 0000000000000001 R6: 00000004ec8c0000 R7: 00000000d16fb804 R8: 0000000000000000 R9: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: c000000001ae5c70 R13: c000000003ec0000 R14: 0000000000000000 R15: 0000000000000000 R16: 000000000000000d R17: 0000000031ed68dc R18: 0000000000000000 R19: 0000000000000001 R20: 0000000000210000 R21: 0000000000000000 R22: 0000000000000000 R23: 00000000001c18f0 R24: 000000158fe2f9a4 R25: c000000000000000 R26: 0000000000000000 R27: 0000000000000001 R28: c000000003bd0600 R29: 0000000000000001 R30: c0000000031e20a0 R31: c0000000031e20a8 NIP: c0000000001e94d4 MSR: 800000000290a033 OR3: 0000000000000000 CTR: c000000001ae5c70 LR: c000000001ae5a58 XER: 0000000000000000 CCR: 0000000044042888 MQ: 0000000000000000 DAR: 0000000000000000 DSISR: 0000000000000000 Syscall Result: 0000000000000000 [NIP : plpar_hcall_norets_notrace+24] [LR : check_and_cede_processor+72] #0 [c000000003c77c60] init_thread_union at c000000003c77cd0 (unreliable) #1 [c000000003c77cc0] shared_cede_loop at c000000001ae5ce0 #2 [c000000003c77d00] cpuidle_enter_state at c000000001ae4e90 #3 [c000000003c77dd0] cpuidle_enter at c00000000157dac0 #4 [c000000003c77e10] call_cpuidle at c0000000003111e8 #5 [c000000003c77e30] cpuidle_idle_call at c000000000328c00 #6 [c000000003c77e90] do_idle at c000000000328df0 #7 [c000000003c77ed0] cpu_startup_entry at c0000000003291ac #8 [c000000003c77f00] rest_init at c0000000000117b8 #9 [c000000003c77f40] do_initcalls at c00000000300f150 #10 [c000000003c77fe0] start_here_common at c00000000000e998 crash> q =================================================================== ------- Comment From [email protected] 2026-04-13 06:27 EDT------- as per last comment, closing the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141507 Title: [Ubuntu2604] [FW1110] Unable to analyse vmcore generated via "virsh dump" using crash utility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2141507/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
