On 07.05.2012 19:32, Jan Kiszka wrote:
> On 2012-05-07 11:45, Michael Tokarev wrote:
[]
>> $ ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -drive
>> file=w7x32sp1.raw,if=virtio,snapshot=on -m 1G -net none -machine
>> accel=kvm,kernel_irqchip=on
>
> Can you check if -global apic.vapic=off makes any difference in the
> broken case? I'm facing general issues in that setup once I enable
> virtio-block - independent of vapic on/off or in-kernel/userspace. The
> boot freezes, and qemu can only be terminated via kill -9. So, retrying
> with IDE as block interface would also be interesting.
Both switching from virtio to ide and disabling vapic fixes the reboot
issue, so win guests starts rebooting fine.
On 07.05.2012 20:06, Avi Kivity wrote:
> Something that is different in a reboot, is that patching the ROM is
> skipped. Please try removing the following lines from hw/kvmvapic.c's
> update_rom_mapping():
>
> /* fixup addresses in ROM if needed */
> if (rom_state_vaddr == le32_to_cpu(s->rom_state.vaddr)) {
> return 0;
> }
>
And commenting out this code does not change anything -- with virtio-blk
the guest does not reboot with STOP 0x5c code as before.
Thanks!
/mjt
