qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
	Bug 1297651 <1297651@bugs.launchpad.net>,
	Laszlo Ersek <lersek@redhat.com>,
	qemu-devel@nongnu.org, robert.hu@intel.com
Subject: Re: [Qemu-devel] [Bug 1297651] [NEW] KVM create a win7 guest with Qemu, it boots up fail
Date: Wed, 26 Mar 2014 17:09:29 +0200	[thread overview]
Message-ID: <20140326150929.GA3511@redhat.com> (raw)
In-Reply-To: <20140326150638.GR2057@otherpad.lan.raisama.net>

On Wed, Mar 26, 2014 at 12:06:38PM -0300, Eduardo Habkost wrote:
> On Wed, Mar 26, 2014 at 04:54:31PM +0200, Michael S. Tsirkin wrote:
> > On Wed, Mar 26, 2014 at 02:48:29PM +0100, Igor Mammedov wrote:
> [...]
> > > more clean would be to abort if CPON index (i.e. APIC ID)
> > > is more than 255. That would affect small number of weird
> > > topologies but sould be fine for most usecases.
> > 
> > Any idea how to trigger this behaviour?
> 
> Set sockets and/or cores to a 2^n+1 value. It will use n+1 bits for the
> socket ID and core ID, making APIC ID larger than CPU index. You can get
> a very large APIC ID if you use, for example:
> 
>   -smp 1,cores=17,threads=17,maxcpus=200
> 
> There's code to limit the maximum APIC ID and abort if it is too large,
> already (so the above command-line will make QEMU abort).

Okay so how do you make this package size exactly 256?

> If we want to
> limit APIC IDs to <255 instead of <256, we just need to change
> ACPI_CPU_HOTPLUG_ID_LIMIT.
> 
> -- 
> Eduardo

  reply	other threads:[~2014-03-26 15:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  6:45 [Qemu-devel] [Bug 1297651] [NEW] KVM create a win7 guest with Qemu, it boots up fail Robert Hu
2014-03-26  7:10 ` Gonglei (Arei)
2014-03-26  7:16 ` Gonglei (Arei)
2014-03-26 10:45   ` Michael S. Tsirkin
2014-03-26  9:31 ` Stefan Hajnoczi
2014-03-26 10:31 ` Michael S. Tsirkin
2014-03-26 12:28   ` Laszlo Ersek
2014-03-26 12:58     ` Michael S. Tsirkin
2014-03-26 13:48       ` Igor Mammedov
2014-03-26 13:56         ` Michael S. Tsirkin
2014-03-26 14:54         ` Michael S. Tsirkin
2014-03-26 15:06           ` Eduardo Habkost
2014-03-26 15:09             ` Michael S. Tsirkin [this message]
2014-03-26 15:23               ` Eduardo Habkost
2014-03-26 16:28                 ` Laszlo Ersek
2014-03-26 15:52         ` Laszlo Ersek
2014-03-26 16:29           ` Michael S. Tsirkin
2014-03-26 13:56       ` Laszlo Ersek
2014-03-26 14:50         ` Michael S. Tsirkin
2014-03-27  5:19         ` Hu, Robert
2014-03-27  5:15   ` Hu, Robert
2014-03-27  5:22 ` [Qemu-devel] [Bug 1297651] " Robert Hu
2014-03-27 14:03   ` Serge Hallyn
2014-03-28  2:22 ` Robert Hu
2014-04-04  3:39 ` Serge Hallyn

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=20140326150929.GA3511@redhat.com \
    --to=mst@redhat.com \
    --cc=1297651@bugs.launchpad.net \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.hu@intel.com \
    /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).