All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] current qemu git does not work with win7 guest
Date: Mon, 07 May 2012 22:21:16 +0400	[thread overview]
Message-ID: <4FA8129C.2080609@msgid.tls.msk.ru> (raw)
In-Reply-To: <4FA80F55.9030604@siemens.com>

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.

Thanks,

/mjt

  reply	other threads:[~2012-05-07 18:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 19:03 [Qemu-devel] current qemu git does not work with win7 guest Michael Tokarev
2012-05-07  6:06 ` Michael Tokarev
2012-05-07  7:45   ` Gleb Natapov
2012-05-07  8:01     ` Michael Tokarev
2012-05-07  8:06       ` Gleb Natapov
2012-05-07  8:37         ` Michael Tokarev
2012-05-07  9:54         ` Michael Tokarev
2012-05-07 10:16           ` Gleb Natapov
2012-05-07 10:26             ` Michael Tokarev
2012-05-07 13:51   ` Michael Tokarev
2012-05-07 14:18     ` Jan Kiszka
2012-05-07 14:35       ` Michael Tokarev
2012-05-07 14:40         ` Jan Kiszka
2012-05-07 14:45         ` Michael Tokarev
2012-05-07 15:32           ` Jan Kiszka
2012-05-07 17:48             ` Michael Tokarev
2012-05-07 18:07               ` Jan Kiszka
2012-05-07 18:21                 ` Michael Tokarev [this message]
2012-05-07 16:06     ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA8129C.2080609@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.