From: Stefan Priebe <s.priebe@profihost.ag>
To: Igor Mammedov <imammedo@redhat.com>
Cc: "Bo Yang" <BoYang@suse.com>, "Bruce Rogers" <brogers@suse.com>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] CPU hotplug
Date: Thu, 30 Aug 2012 20:45:10 +0200 [thread overview]
Message-ID: <503FB4B6.3080107@profihost.ag> (raw)
In-Reply-To: <20120830204016.7fffb997@thinkpad.mammed.net>
Am 30.08.2012 20:40, schrieb Igor Mammedov:
>>>> Am 30.08.2012 um 17:41 schrieb Andreas Färber <afaerber@suse.de>:
>>>>
>>>>> Am 30.08.2012 11:06, schrieb Stefan Priebe:
>>>>>> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
>>>>>> just crashes when sending cpu_set X online through qm monitor.
>>>>>
>>>>> For SLES we're carrying a patch by Kamalesh Babulal that prevents this
>>>>> (BNC#747339).
>>>>
>>>> But this just disables CPU [hotplug] and does Not fix it?
>>>
>>> It fixes the crash. Hotplug needs to be implemented first, and this has
>>> been taking several months already (for x86, to be specific).
>>
>> Mhm RHEL 6.3 claims to support this?
> it's not officially supported, it's just tech-preview. That allows to play with
> hotplug and uncover possible guest issues early.
Yes, but does this mean that is doesn't work at RHEL too? i wasn't able
to get it working any guest or host at all.
Greets,
Stefan
next prev parent reply other threads:[~2012-08-30 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 9:06 [Qemu-devel] CPU hotplug Stefan Priebe
2012-08-30 9:17 ` Igor Mammedov
2012-08-30 15:41 ` Andreas Färber
2012-08-30 16:08 ` Michael Tokarev
2012-08-30 16:35 ` Stefan Priebe
2012-08-30 16:43 ` Andreas Färber
2012-08-30 17:23 ` Stefan Priebe
2012-08-30 18:40 ` Igor Mammedov
2012-08-30 18:45 ` Stefan Priebe [this message]
2012-08-30 18:56 ` Igor Mammedov
2012-08-30 18:59 ` Stefan Priebe
-- strict thread matches above, loose matches on Subject: below --
2016-02-01 5:35 David Gibson
2016-02-01 10:13 ` Christian Borntraeger
2016-02-02 18:33 ` Eduardo Habkost
2016-02-03 1:50 ` David Gibson
2016-02-03 18:12 ` Eduardo Habkost
2016-02-03 5:03 ` Bharata B Rao
2016-02-03 5:42 ` David Gibson
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=503FB4B6.3080107@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=BoYang@suse.com \
--cc=afaerber@suse.de \
--cc=brogers@suse.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).