If you destroy domain it will disappear or going to zombie state (no
memory, endless dying status). xapi will not able to detect this, so
destroying domain is very bad thing.
If you want to shutdown domain forcefully without waiting xapi to get
through it long task list, just send xc.shutdown_domain(domid,X) (X -
0,1 or 2). xenopsd will detect this and reacts accordingly.
18.04.2013 12:21, ?????@????? ?????:
Hello all,
I'm using XenServer 6.1 Java SDK to manage XCP 1.6.
When shutdowning a VM, I can use hardShutdown or cleanShutdown.
I known the differences of the two.
Following this article, I found there's another way to shutdown the
Pending VM.
http://support.citrix.com/article/CTX131421
My question is: what's the difference of hardShutdown and destroy the
control domain?
Are there any side effects or risks to destroy the control domain?
Both the pending and normal state.
If there're no risks, why doesn't XCP use this to implement the
hardshutdown function, since destroying the control domain won't be
stucked.
Any suggestions for use or not use destroying control domain to force
shutdown the VM?
Thanks.
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
