5.0.2 seems to fix this and has hit Maverick. Could a Maverick tester
please check that this has fixed it (I have no qemu dumps to test this
on)? For now I will mark this as fix released, however if this is still
a problem, please re-open the bug.
** Changed in: crash (Ubuntu)
Status: New =
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 w
** Patch added: "crude hacks"
http://launchpadlibrarian.net/43652512/559219.diff
--
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
Changing 9 to 10 in assert() call allows crash to proceed, but it then
segfaults after 'x86_64_get_active_set: runqueue vs. current_task' and
later exits with message 'foreach: cannot resolve: "jiffies"'.
One final workaround is to use "--machdep phys_base=0" argument, because
for some reason phys
