All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Tokarev <mjt@tls.msk.ru>
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 12:32:53 -0300	[thread overview]
Message-ID: <4FA7EB25.9010009@siemens.com> (raw)
In-Reply-To: <4FA7E00E.5090305@msgid.tls.msk.ru>

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

  reply	other threads:[~2012-05-07 15:33 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 [this message]
2012-05-07 17:48             ` Michael Tokarev
2012-05-07 18:07               ` Jan Kiszka
2012-05-07 18:21                 ` Michael Tokarev
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=4FA7EB25.9010009@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gleb@redhat.com \
    --cc=mjt@tls.msk.ru \
    --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.