From: "Jan Beulich" <JBeulich@suse.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: "xl vcpu-set" not persistent across reboot?
Date: Fri, 03 Jun 2016 08:42:11 -0600 [thread overview]
Message-ID: <5751B36302000078000F1A67@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20160603134106.GJ14588@citrix.com>
>>> On 03.06.16 at 15:41, <wei.liu2@citrix.com> wrote:
> On Fri, Jun 03, 2016 at 02:29:12AM -0600, Jan Beulich wrote:
>> Ian, Wei,
>>
>> is it intentional that rebooting a (HVM) guest after having altered its
>> vCPU count will reset it back to the vCPU count it was originally
>> started with? That doesn't seem very natural - if one hotplugs a CPU
>> into a physical system and then reboots, that CPU will remain there.
>>
>
> This is probably an oversight.
>
> I've added this to my list of things to look at after the release.
Thanks!
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-03 14:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 8:29 "xl vcpu-set" not persistent across reboot? Jan Beulich
2016-06-03 13:41 ` Wei Liu
2016-06-03 14:42 ` Jan Beulich [this message]
2016-06-03 16:35 ` Wei Liu
2016-06-06 8:58 ` Jan Beulich
2016-06-06 17:18 ` Wei Liu
2016-06-06 17:20 ` Wei Liu
2016-06-06 17:34 ` Andrew Cooper
2016-06-07 8:30 ` Wei Liu
2016-06-14 16:34 ` Ian Jackson
2016-06-14 16:39 ` Wei Liu
2016-06-14 16:57 ` Ian Jackson
2016-06-14 16:59 ` Andrew Cooper
2016-06-14 17:06 ` Wei Liu
2016-06-14 17:03 ` Wei Liu
2016-06-14 17:23 ` Wei Liu
2016-06-14 17:35 ` Anthony PERARD
2016-06-07 6:38 ` Jan Beulich
2016-06-07 8:27 ` Wei Liu
2016-06-06 9:04 Jan Beulich
2016-06-06 13:07 ` Stefano Stabellini
2016-06-06 13:42 ` Wei Liu
2016-06-06 14:00 ` Stefano Stabellini
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=5751B36302000078000F1A67@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).