On Tue, Jan 19, 2016 at 01:43:58PM +0000, Daniel P. Berrange wrote:
I don't think it does. Passing GRACEFUL flag means libvirt will
try
/less/ hard to kill QEMU, so it is /more/ likely that you will get
the
"Failed to terminate process 1275 with SIGTERM: Device or resource busy"
In general, that error message is something to be expected from the
virDomainDestroy() API, as we won't wait for death forever. If an
app wishes to wait forever, they should either re-issue the destroy
API call, or wait for an event notification of VIR_DOMAIN_EVENT_STOPPED
to arrive.
IIUC, we should trap this specific error, and then basically loop if
it happens? Is there a good way to trap specific errors without
trying to match error message text?
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW