[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] current qemu git does not work with win7 guest

From: Michael Tokarev
Subject: Re: [Qemu-devel] current qemu git does not work with win7 guest
Date: Mon, 07 May 2012 22:21:16 +0400
User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.3) Gecko/20120329 Icedove/10.0.3

On 07.05.2012 22:07, Jan Kiszka wrote:
> On 2012-05-07 14:48, Michael Tokarev wrote:
>> 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.
> You mean doing both at the same time, or also when you only apply one
> workaround? For me, disabling the vapic had _no_ impact, only disabling
> virtio allowed to boot at all.

One at a time - either vapic=off or virtio=>ide.  Both at once also works.
I just rechecked, -- yes indeed, any of the two is enought to make win
guest to reboot fine.  Sorry for being unclean.

> I suspect something is subtly broken in qemu, and it is not directly
> related to the vapic, maybe even not virtio.

Well, might be, in your case.. ;)

Yes I understand that you've hit different issue there.  Just like
me while trying to bisect it, -- I've hit the -vga std non-functioning
somewhere in between 1.0 and current ;)

The issue I'm hitting is quite "reliable", so to say.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]