From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: Fahri Cihan Demirci <cihand@skyatlas.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: [Qemu-devel] VCPU Hot-Unplug Feature
Date: Mon, 18 May 2015 10:17:20 +0200 [thread overview]
Message-ID: <20150518081719.GA5439@vader> (raw)
In-Reply-To: <20150504183420.GA3127@caesium>
[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]
On Mon, May 04, 2015 at 09=34=21PM +0300, Fahri Cihan Demirci wrote:
> Hello Alexandre,
>
> Thank you for your response. I came upon that patch on the Libvirt mailing list, too. However, the following comment makes me think that it's not likely to be merged:
>
> https://www.redhat.com/archives/libvir-list/2015-February/msg00415.html
>
> Also, later in the thread, the author of the patch seems to confirm that the plan for hotplug in QEMU is not compatible with that patch:
>
> https://www.redhat.com/archives/libvir-list/2015-March/msg01169.html
>
> So, I think Libvirt developers have decided to wait until there is a generalized groundwork for VCPU hot-unplug in the QEMU code base. That's why I decided to inquire and offer help for QEMU developers, since the ball seems to be in their court now.
We're very interested in having this feature upstream as well. As Fahri
stated above, I also would like to offer help to get it pushed.
What's the current status?
Regards,
>
> Thanks a lot for your time.
>
>
> On Mon, May 04, 2015 at 07:49:08PM +0200, Alexandre DERUMIER wrote:
> > Hi,
> >
> > they are a lot of patches sent on the mailing list recently,
> >
> > cpu hotplug|unplug with device_add|del
> >
> > https://www.redhat.com/archives/libvir-list/2015-February/msg00084.html
> >
> >
> >
> > ----- Mail original -----
> > De: "Fahri Cihan Demirci" <cihand@skyatlas.com>
> > À: "qemu-devel" <qemu-devel@nongnu.org>
> > Envoyé: Lundi 4 Mai 2015 18:24:43
> > Objet: [Qemu-devel] VCPU Hot-Unplug Feature
> >
> > Hello,
> >
> > We are interested in being able to remove a VCPU from an active Libvirt domain running under QEMU/KVM. However, currently that does not seem to be possible because QEMU does not provide an interface for hot-unplugging a VCPU. The corresponding feature page [1] on the QEMU wiki mentions the cpu-add interface and the generalized device add/del interface. So, my question is, is there someone working on a cpu-remove interface or making progress in the generalized device add/del interface to hot-unplug VCPUS? If you are in any way interested in or planning such a feature, we may provide feedback, testing or help in the development effort. Any other input, guidance or corrections would be also most welcome. Thank you.
> >
> > [1] http://wiki.qemu.org/Features/CPUHotplug
> >
> >
> > Best regards,
> > Fahri Cihan Demirci
>
--
Eduardo Otubo
ProfitBricks GmbH
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-05-18 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 16:24 [Qemu-devel] VCPU Hot-Unplug Feature Fahri Cihan Demirci
2015-05-04 17:49 ` Alexandre DERUMIER
2015-05-04 18:34 ` Fahri Cihan Demirci
2015-05-18 8:17 ` Eduardo Otubo [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=20150518081719.GA5439@vader \
--to=eduardo.otubo@profitbricks.com \
--cc=aderumier@odiso.com \
--cc=cihand@skyatlas.com \
--cc=imammedo@redhat.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).