Re: [Xen-users] about xm vcpu-set

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

Actually, Fajar, that's not correct.  In my config files, I have:

vcpus=2

maxvcpus=4

So, domU starts out with VCPUs = 2, and I can use xm vcpu-set <domain> 4 to bring it up to 4 vCPUs.  Works perfectly.

-Nick

>>> On 2009/05/28 at 11:27, "Fajar A. Nugraha" <fajar@xxxxxxxxx> wrote:

On Thu, May 28, 2009 at 6:52 PM, yassine ayachi
<ayachi.yassine@xxxxxxxxx> wrote:
> [root@localhost ~]# xm list
> Name                                      ID Mem(MiB) VCPUs   State
> Time(s)
> Domain-0                                 0     4035     4            r-----
>   29851.8
> domU                                       3     2047     1
> r-----   96114.6
>
> [root@localhost ~]# xm vcpu-set 3 2
>

That won't work. The maximum amount of CPU and memory for domU is
determined at domU creation. You can't simply add a CPU like that.

A workaround is to use something like this on domU config file
(old-style config):
#======================
memory = "500"
maxmem = "8000"

vcpus=8
vcpu_avail=1
#======================

that way domU will start with 500MB memory, but you'll be able to
expand it later up to 8000MB. As for CPU, it will actually start with
8 CPU but during kernel boot the other 7 will be hot-unplugged (you'll
see lots of "Breaking affinity for irq ..." message during domU boot.
It's normal). You can then hot-plug other CPUs as needed, up to a
maximum of 8.

Note that these work for xenified PV kernels only. It doesn't work
(yet) for pv_ops kernel or HVM guest.

--
Fajar

---

<br><hr>
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users