[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Xen 4.2 Release Plan / TODO
- To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
- From: Matt Wilson <msw@xxxxxxxxxx>
- Date: Tue, 26 Jun 2012 13:31:51 -0700
- Cc: xen-devel <xen-devel@xxxxxxxxxxxxx>
- Delivery-date: Tue, 26 Jun 2012 20:33:26 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=msw@xxxxxxxxxx; q=dns/txt; s=rte02; t=1340742743; x=1372278743; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=axR0Irmy4GFakXIjWr+EZ1gTBuEWxCLkwI1Rs6frL7E=; b=K/ZI+Xr662jKFFfrU9bxcPrCrQJbxIqnOmqEnZCGFxm1dyU/g26ludLD WntSZWRMU2E10sw6Ow7NUex4XA9Iqw==;
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel