qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip
Date: Wed, 02 Feb 2011 12:58:47 +0100	[thread overview]
Message-ID: <4D4946F7.1070702@siemens.com> (raw)
In-Reply-To: <20110202115537.GE14984@redhat.com>

On 2011-02-02 12:55, Gleb Natapov wrote:
> On Tue, Feb 01, 2011 at 07:02:03PM +0100, Jan Kiszka wrote:
>> Hi,
>>
>> testing my KVM patches, I noticed that none of the 64-bit Windows
>> versions I have around (early Win7 & 2003 server) boot in KVM mode when
>> using 2 or more VCPUs and the user space irqchip. This applies to both
>> upstream KVM and qemu-kvm, with our without any of my current patches. A
>> subtle difference in the APIC/IOAPIC emulation?
>>
>> Can anyone confirm this?
>>
> Just booted windows7-64 on qemu-kvm -no-kvm-irqchip + latest kernel here.

Strange. -smp 2?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-02-02 14:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 18:02 [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip Jan Kiszka
2011-02-02 11:55 ` Gleb Natapov
2011-02-02 11:58   ` Jan Kiszka [this message]
2011-02-02 12:35     ` Gleb Natapov
2011-02-02 12:50       ` Jan Kiszka
2011-02-02 13:05         ` Avi Kivity
2011-02-02 13:09           ` Jan Kiszka
2011-02-02 13:11             ` Gleb Natapov
2011-02-02 13:14               ` Avi Kivity
2011-02-02 13:18                 ` Gleb Natapov
2011-02-02 14:30           ` Jan Kiszka
2011-02-02 14:35             ` Avi Kivity
2011-02-02 14:43               ` Jan Kiszka
2011-02-02 14:52                 ` Jan Kiszka
2011-02-02 15:09                   ` Avi Kivity
2011-02-02 15:35                     ` Jan Kiszka
2011-02-02 15:44                       ` Avi Kivity
2011-02-02 15:46                       ` Gleb Natapov
2011-02-02 15:52                         ` Jan Kiszka
2011-02-02 16:29                           ` Gleb Natapov
2011-02-02 16:36                             ` Jan Kiszka
2011-02-02 16:39                               ` Gleb Natapov
2011-02-02 16:51                                 ` Jan Kiszka
2011-02-03  7:42                                   ` Gleb Natapov
2011-02-03  9:31                                     ` Jan Kiszka
2011-02-03  8:18                           ` Avi Kivity
2011-02-03  9:32                             ` Jan Kiszka
2011-02-03 10:01                               ` Avi Kivity
2011-02-03 10:14                                 ` Jan Kiszka
2011-02-03 10:04                               ` Marcelo Tosatti
2011-02-03 10:11                                 ` Jan Kiszka
2011-02-03 14:15                                   ` Gleb Natapov
2011-02-03 14:27                                     ` Jan Kiszka
2011-02-06 10:26                                     ` Avi Kivity
2011-02-06 10:28                                       ` Gleb Natapov

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=4D4946F7.1070702@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).