From: Matt Wilson <msw@amazon.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2 Release Plan / TODO
Date: Tue, 26 Jun 2012 13:31:51 -0700 [thread overview]
Message-ID: <20120626203151.GA8676@US-SEA-R8XVZTX> (raw)
In-Reply-To: <1340699982.3832.28.camel@zakaz.uk.xensource.com>
On Tue, Jun 26, 2012 at 01:39:42AM -0700, Ian Campbell wrote:
> * [BUG] vcpu-set doesn't take effect on guest, reported by Intel:
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
This may be a problem with the guest, rather than a problem with Xen
or the toolstack. I tested on a domU running a 3.2.20-based Linux
kernel. The domU kernel didn't automatically enable the vCPUs after
calling "xl vcpu-set" to increase the allocation.
# xl list 2
Name ID Mem VCPUs State Time(s)
test 2 15360 1 -b---- 6617.6
# xl vcpu-set 2 4
# xl list 2
Name ID Mem VCPUs State Time(s)
test 2 15360 1 -b---- 6617.7
But when I hotplugged the CPUs on the domU side with
for online in /sys/devices/system/cpu/cpu*/online; do
echo 1 > $online
done
Now we see:
# xl list 2
Name ID Mem VCPUs State Time(s)
test 2 15360 4 -b---- 6617.8
I've added this as a comment to the bugzilla.
Matt
next prev parent reply other threads:[~2012-06-26 20:31 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 8:39 Xen 4.2 Release Plan / TODO Ian Campbell
2012-06-26 20:31 ` Matt Wilson [this message]
2012-06-26 21:09 ` Konrad Rzeszutek Wilk
2012-06-26 22:57 ` Matt Wilson
2012-06-27 8:41 ` Ian Campbell
2012-06-28 8:56 ` Ren, Yongjie
2012-06-27 13:12 ` Jan Beulich
2012-06-27 14:52 ` Ian Campbell
2012-06-27 14:57 ` Jan Beulich
2012-06-27 15:01 ` Ian Campbell
2012-06-27 15:36 ` Jan Beulich
2012-06-28 15:18 ` Tim Deegan
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 11:02 Ian Campbell
2012-07-03 7:52 ` Jan Beulich
2012-07-03 10:45 ` Anthony PERARD
2012-07-04 16:42 ` Dario Faggioli
2012-07-04 17:08 ` Roger Pau Monne
2012-07-13 9:55 ` Roger Pau Monne
2012-06-20 11:29 Ian Campbell
2012-06-20 11:43 ` Andrew Cooper
2012-06-20 13:07 ` Jan Beulich
2012-06-20 13:19 ` Andrew Cooper
2012-06-20 19:29 ` Andrew Cooper
2012-06-26 8:16 ` Ian Campbell
2012-04-10 10:24 Ian Campbell
2012-04-12 9:56 ` George Dunlap
2012-04-12 10:24 ` Dario Faggioli
2012-04-12 11:00 ` Ian Campbell
2012-04-02 10:26 Ian Campbell
2012-04-02 10:39 ` David Vrabel
2012-04-02 10:43 ` Ian Campbell
2012-04-02 11:17 ` George Dunlap
2012-04-02 14:41 ` Stefano Stabellini
2012-04-11 16:11 ` Ian Jackson
2012-04-11 16:13 ` Ian Jackson
2012-04-12 7:42 ` Ian Campbell
2012-04-12 7:35 ` Ian Campbell
2012-04-12 7:59 ` Ian Campbell
2012-04-12 16:37 ` Dan Magenheimer
2012-04-12 16:45 ` Ian Campbell
2012-04-13 15:28 ` Dan Magenheimer
2012-04-13 10:45 ` Ian Jackson
2012-04-13 19:45 ` Dan Magenheimer
2012-04-16 10:16 ` Ian Jackson
2012-04-12 8:16 ` Ian Campbell
2012-04-24 17:52 ` Ian Jackson
2012-03-27 9:34 Ian Campbell
2012-03-27 18:30 ` Shriram Rajagopalan
2012-03-19 10:57 Ian Campbell
2012-03-19 11:25 ` Jan Beulich
2012-03-19 11:33 ` Ian Campbell
2012-03-19 12:02 ` Jan Beulich
2012-03-19 12:13 ` Stefano Stabellini
2012-03-19 12:13 ` George Dunlap
2012-03-19 12:28 ` Ian Campbell
2012-03-20 5:19 ` Matt Wilson
2012-03-20 8:42 ` Ian Campbell
2012-03-22 9:21 ` Ian Campbell
2012-03-22 9:22 ` Ian Campbell
2012-03-22 10:22 ` Stefano Stabellini
2012-03-22 9:35 ` George Dunlap
2012-03-22 9:53 ` Ian Campbell
2012-03-22 10:08 ` George Dunlap
2012-03-22 10:19 ` Ian Campbell
2012-03-22 10:31 ` Keir Fraser
2012-03-22 10:34 ` George Dunlap
2012-03-22 10:38 ` Ian Campbell
2012-03-27 9:33 ` Ian Campbell
2012-03-27 10:19 ` George Dunlap
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=20120626203151.GA8676@US-SEA-R8XVZTX \
--to=msw@amazon.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.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).