Recently released version 5.0.4 includes these fixes: - Fix to support KVM dumpfiles created with "virsh dump" that create "cpu" header sections using a QEMU CPU_SAVE_VERSION version greater than the supported version of 9. Without the patch, the crash session fails during initialization with the error message "crash: qemu-load.c:501: cpu_init_load_64: Assertion `version_id >= 4 && version_id <= 9' failed." The patch now accepts CPU_VERSION_VERSION values up to 12.
- Fix for x86_64 KVM dumpfiles created with "virsh dump" whose kernels have a "_text" virtual address higher than __START_KERNEL_map. Without the patch, the physical base address calculation fails, making the dumpfile unusable. - Implemented a new "map" command that is seen only when running with KVM guest dumpfiles created with "virsh dump". The layout of this dumpfile format does not allow the access of system memory in a "random-access" manner. Therefore, during session initialization, a potentially time-consuming dumpfile scan procedure is required to create a physical-memory-to-file-offset memory map for use during the session. The new "map" command allows the user to either append the memory map to the end of the dumpfile, or to create a discrete memory map file. In either case, the dumpfile scan will not be required during subsequent sessions. The command's help page may be seen by entering "crash -h map". -- crash does not support recent qemu dump format https://bugs.launchpad.net/bugs/559219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
