From: Gleb Natapov <gleb@redhat.com>
To: Ryota Ozaki <ozaki.ryota@gmail.com>
Cc: dbareiro@gmx.net, kvm@vger.kernel.org
Subject: Re: CPU hotplug add seems broken
Date: Sun, 10 Jan 2010 10:43:53 +0200 [thread overview]
Message-ID: <20100110084353.GI4905@redhat.com> (raw)
In-Reply-To: <5e93dcec1001100033tdb930eqcaf48a36ee36b335@mail.gmail.com>
On Sun, Jan 10, 2010 at 05:33:02PM +0900, Ryota Ozaki wrote:
> On Sun, Jan 10, 2010 at 3:39 PM, Gleb Natapov <gleb@redhat.com> wrote:
> > On Sat, Jan 09, 2010 at 04:30:11PM -0300, Daniel Bareiro wrote:
> >> On Friday, 08 January 2010 19:35:04 +0900,
> >> Ryota Ozaki wrote:
> >>
> >> > Hi all,
> >>
> >> Hi, Ryota.
> >>
> >> > I've tried CPU hotplug with latest qemu-kvm.git code,
> >> > and got segmentation fault.
> >>
> >> I'm also having this problem but with Linux 2.6.32.2 + qemu-kvm-0.12.1.1
> >> in the host:
> >>
> >> Jan 9 16:11:11 ubuntu kernel: [758479.480219] qemu-system-x86[29330]:
> >> segfault at 90 ip 00007f5816bf3990 sp 00007fff9258fc88 error 4 in
> >> libpthread-2.7.so[7f5816be8000+16000]
> >>
> >> I've guest with one cpu in which I try to add one more. For this I
> >> execute the following in qemu monitor and here it is where I got
> >> segmentation fault:
> >>
> >> (qemu) cpu_set 1 online
> >> Connection closed by foreign host.
> >>
> >>
> >> I'm not sure if the procedure that I'm following is the correct one. I
> >> tried as much without using additional parameters when boots guest like
> >> using -smp 1,maxcpus=2, but I reach the same result.
> >>
> >> The Kernel of guest has checked the "Support for hot-pluggable CPUs"
> >> option, in case it is necessary.
> >>
> > CPU host-plug is not supported on qemu-kvm-0.12. It shouldn't segfault
> > obviously,
>
> I see. Anyway I think we need some workaround to avoid segfault.
>
Disabling cpu_set command for qemu-kvm-0.12 is good enough workaround.
> > but ACPI code that handles CPU host-plug was not ported to
> > SeaBIOS when it replaces BOCH BIOS.
>
> Yeah, I confirmed it during memory hotplug work...
>
> So I'd like to know when cpu hotplug comes back? I didn't see
> it in qemu-0.13 feature requests.
>
May I ask what do you need it for? The problem is that there is no standard
way to hotplug CPUs in a PC. Linux implements the way UNISYS happen to do
it, but no other system do it like that. Windows implements it
differently and in the way that conflicts with Linux, so you can't
have working Linux implementation and pass Microsoft SVVP test at the
same time for instance.
--
Gleb.
next prev parent reply other threads:[~2010-01-10 8:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 10:35 CPU hotplug add seems broken Ryota Ozaki
2010-01-09 19:30 ` Daniel Bareiro
2010-01-10 6:39 ` Gleb Natapov
2010-01-10 8:33 ` Ryota Ozaki
2010-01-10 8:43 ` Gleb Natapov [this message]
2010-01-11 9:24 ` Ryota Ozaki
2010-01-11 9:32 ` Gleb Natapov
2010-01-11 10:21 ` Ryota Ozaki
2010-01-11 10:23 ` Avi Kivity
2010-01-11 10:24 ` Gleb Natapov
2010-01-11 10:25 ` Avi Kivity
2010-01-11 10:42 ` Gleb Natapov
2010-01-11 10:50 ` Avi Kivity
2010-01-11 10:53 ` Gleb Natapov
2010-01-11 10:58 ` Avi Kivity
2010-01-11 11:03 ` Gleb Natapov
2010-01-11 11:06 ` Avi Kivity
2010-01-11 12:18 ` Gleb Natapov
2010-01-11 13:57 ` Anthony Liguori
2010-01-11 14:32 ` Avi Kivity
2010-01-11 10:30 ` Ryota Ozaki
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=20100110084353.GI4905@redhat.com \
--to=gleb@redhat.com \
--cc=dbareiro@gmx.net \
--cc=kvm@vger.kernel.org \
--cc=ozaki.ryota@gmail.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).