On 2012-05-07 11:45, Michael Tokarev wrote: > On 07.05.2012 18:35, Michael Tokarev wrote: >> On 07.05.2012 18:18, Jan Kiszka wrote: >> [] >>> I have a 32-bit WinXP here to test (but not a Win7-32) and will give it >> >> I just found out that a 32bit guest is not enough. The problem appears >> to be with 32bit userspace running under 64bit kernel only. I just >> booted a 32bit kernel here on host, and now all windows guests reboot >> fine, with and without kvmvapic.bin file. >> >>> a try later. What irritates me is that qemu.git has a problem here but >>> not latest qemu-kvm.git. Both are very similar now. Hmm, what is your >>> qemu.git command line again? Does it include "-machine >>> accel=kvm,kernel_irqchip=on" (to enable in-kernel irqchip)? >> >> Rebooting... ;) > > With kernel_irqchip=on it does not happen with qemu too, just like with > qemu-kvm. So only 32bit userspace on 64bit kernel, and only with > kernel_irqchip = OFF, and only with 32bit version of win7 or winXP. > > The kernel line is rather simple: > > $ ./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. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux
