From: Gleb Natapov <gleb@redhat.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: vcpu hotplug status
Date: Sat, 19 Mar 2011 16:28:14 +0200 [thread overview]
Message-ID: <20110319142814.GA9072@redhat.com> (raw)
In-Reply-To: <AANLkTi=wkSgK9SdzvXF4mne4d=wb39Jse14RKe+fbWb_@mail.gmail.com>
On Sat, Mar 19, 2011 at 12:25:38PM +0100, William Dauchy wrote:
> On Wed, Mar 16, 2011 at 11:17 AM, William Dauchy <wdauchy@gmail.com> wrote:
> > I wanted to test vcpu hotplug. When adding a cpu I'm getting
> > "qdev_create_from_info: Assertion `bus->allow_hotplug' failed."
> > I went through a discussion about the subject here
> > http://lists.nongnu.org/archive/html/qemu-devel/2010-08/msg00999.html
> > To make sure whether it was working, I hard-coded "allow_hotplug = 1";
> > the guest is now able to have more vpcus without any trouble (removing
> > vcpus did not seem to work though).
> > Since it definitively not a solution, I wanted to have a status about
> > the subject or if I was missing something in my configuration since it
> > works with a dirty workaround.
> > I would be also pleased to get some tips to fix the code.
>
> Any thoughts? Or perhaps my message was lost among patches...
>
Even patches are lost among patches those days. The problem you describe
is known. Both of them actually (non working vcpu remove is the second
one). I am not aware of any effort to fix them. I am more concern about
second problem though. bus->allow_hotplug is not fixed because of
laziness on developers part, but non working vcpu remove is caused by us not
understanding how cpu hot-plug works in Linux on x86.
--
Gleb.
prev parent reply other threads:[~2011-03-19 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 10:17 [Qemu-devel] vcpu hotplug status William Dauchy
2011-03-19 11:25 ` [Qemu-devel] " William Dauchy
2011-03-19 14:28 ` Gleb Natapov [this message]
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=20110319142814.GA9072@redhat.com \
--to=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wdauchy@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).