Yes, memory corruption in guest explains the unaligned/out of range
pointer error (issued when grub2 releases a block of memory, and grub
uses dynamic allocation quite a lot) and the boot loop. This corruption
most likely originates in the vga code fixed in revision 2470 as
reported in Bug #717445.
Note: this is already marked as FIXME in kvm-all.c:
if (run->internal.suberror == KVM_INTERNAL_ERROR_EMULATION) {
fprintf(stderr, "emulation failure\n");
if (!kvm_arch_stop_on_emulation_error(env)) {
cpu_dump_state(env, stderr, fprintf, CPU_DUMP_CODE);
r
It turns out that my previous attempt to reproduce the vga crash using
an image generated by grub-mkrescue (which is easier to work with than
dealing with a full Ubuntu image) is invalid due to bad instrumentation
in the "normal" module init and a stack overflow produced similar
results including t
Did a clean XP install and could not reproduce with current git qemu-
kvm.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/498035
Title:
qemu hangs on shutdown or reboot (XP guest)
Status in QEMU:
Some notes of interest:
- the unaligned pointer error also seems to happen in real systems with certain
ATI cards.
- rebuilding grub with mm-debug makes Ubuntu boot without unaligned/out of
range pointer messages with -vga std.
- adding debug messages (with grub_printf()) to grub memalign/free f
