[libvirt] [PATCH] qemu: undefine is not allowed during domain starting up

Peter Krempa pkrempa at redhat.com
Mon Jul 24 08:06:09 UTC 2017


On Sat, Jul 22, 2017 at 04:55:49 -0400, Yi Wang wrote:
> Start a domain whilst undefine it, if starting failed duing ProcessLaunch,
> on which period qemu exited unexpectedly, the operation will lead to failure
> of undefine the domain until libvirtd restarted. The reason is that libvirtd
> will unlock vm during qemuProcessStart, qemuDomainUndefineFlags can get the
> lock and set vm->persistent 0 but not remove the "active" domain.

Shouldn't the startup code handle that? It definitely works when
starting a transient domain, so making it transient while the startup
code is executed should be the same case.

Since we copy the definition prior to startup, there really should not
be any problem in making the VM transient while it's being started.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20170724/eb7d2070/attachment-0001.sig>


More information about the libvir-list mailing list