[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH] Fix xm create command for wrong scheduler parameters
Hi, When I tested the xm create command with wrong scheduler parameters, a domain existed with the paused state. Usually, if an error occurred by the xm create command, the domain isn't created. The xm start command also has same issue. # xm create /xen/vm1.conf cpu_weight=99999 Using config file "/xen/vm1.conf". Error: weight is out of range # xm create /xen/vm2.conf cpu_cap=999 Using config file "/xen/vm2.conf". Error: cap is out of range # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 491 2 r----- 594.5 vm1 6 256 1 --p--- 0.0 vm2 7 256 1 --p--- 0.0 This patch fixes the issue. If the xm create command fails with wrong scheduler parameters, it destroys the domain in the proceeding of xm create command. Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx> Best regards, Kan Attachment:
xm_create.patch _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |