From: Anthony Liguori <anthony@codemonkey.ws>
To: Jes Sorensen <jes@sgi.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v3
Date: Wed, 22 Jul 2009 10:10:59 -0500 [thread overview]
Message-ID: <4A672C03.8020205@codemonkey.ws> (raw)
In-Reply-To: <20090720144312.052887035@sgi.com>
Jes Sorensen wrote:
> Anthony,
>
> Here's an updated version of the maxcpus patch, which goes on top of
> the most recent QEMU. My older version was against a 2 week old
> version and I see you have applied some boot menu stuff since then
> which did clash with the FW_CFG magic number I used. I suspect that
> could have caused the problems.
>
> Just did a full fresh rebuild and this one works fine for me with the
> Ubuntu test image.
>
I didn't realize that you changed maxcpus == smpcpus by default so my
testing wasn't valid.
If I do the following:
x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img -snapshot -L
~/git/qemu/pc-bios -smp 1,maxcpus=16
I get 'Not responding' errors from an Ubuntu server guest.
You can pull http://repo.or.cz/w/qemu/aliguori-queue.git for-jes
To get my built version of bios.bin. Please try to reproduce this issue
with these bits and let me know if you have trouble with it.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-22 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 14:43 [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v3 Jes Sorensen
2009-07-20 14:43 ` [Qemu-devel] [PATCH 1/2] Introduce -smp , maxcpus= flag to specify maximum number of CPUS Jes Sorensen
2009-07-20 14:43 ` [Qemu-devel] [PATCH 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-07-22 15:10 ` Anthony Liguori [this message]
2009-07-23 10:22 ` [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v3 Jes Sorensen
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=4A672C03.8020205@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=jes@sgi.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 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).