[Xen-devel] [PATCH] Fix xm vcpu-set command for when wrong number of VCPU is given

[Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>]

Hi,

The xm vcpu-set command is able to set zero to the number of 
VCPU of a domain. Therefore I think that it is a natural result 
that the xm start command fails. But I think that a xm vcpu-set 
command must fail usually. 

# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   942     2     r-----     75.2
vm1                                            256     2                 0.0
# xm vcpu-set vm1 0
# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   942     2     r-----     76.2
vm1                                            256     0                 0.0
# xm start vm1
Error: (1, 'Internal error', 'launch_vm: SETVCPUCONTEXT failed (rc=-1)\n')
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting it    


This patch checks the number of VCPU given by the xm vcpu-set 
command. 

# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   942     2     r-----     71.2
vm1                                            256     2                 0.0
# xm vcpu-set vm1 0
Error: Invalid VCPUs
Usage: xm vcpu-set <Domain> <vCPUs>

Set the number of active VCPUs for allowed for the domain.


Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,
 Kan

xm_vcpu-set.patch
Description: Binary data

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