------- Comment From [email protected] 2025-07-17 03:08 EDT------- Hello Frank,
Sorry for the confusion with the long logs. Let me brief it. When the LPAR is running in "KVM Capable" mode, we are not seeing any issue regardless of what is the domain type used in the guest's xml. Hence no patch is required here. But if the same LPAR is not in "KVM Capable" mode, we are seeing the "invalid kernel virtual address" error like below with the distro provided crash tool. root@ltcden6-lp3:~# virsh dump Ubuntu NonKVMFormat1 --memory-only --format=kdump-zlib Domain 'Ubuntu' dumped to NonKVMFormat1 root@ltcden6-lp3:~# crash /usr/lib/debug/boot/vmlinux-6.14.0-23-generic ./NonKVMFormat1 crash 8.0.6 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) 10.2 Copyright (C) 2021 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"... crash: invalid kernel virtual address: 3ce2ffefe8410020 type: "first vmlist addr" Errors like the one above typically occur when the kernel and memory source do not match. These are the files being used: KERNEL: /usr/lib/debug/boot/vmlinux-6.14.0-23-generic The above issue when the LPAR is not in "KVM Capable" mode is getting fixed with the provided patch. Hence the patch is required to fix this case. As you rightly mentioned, the patch is not upstream accepted yet. We will have to wait for the upstream acceptance and once the patch is part of upstream and there by Ubuntu's crash tool, I will be verifying the scenarios again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2117099 Title: "invalid kernel virtual address" error while analysing virsh dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2117099/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
