I enabled all logging levels from libvirtd. I can see at 15:21:31, the domain from process-b getting undefined (virsh undefine (domain-name)), the virt-install from process-a is launched at 15:21:30, so it seems like the undefine of the process-b domain, confuses the virt-install for process-A's domain/guest, it fails to instantiate the process-A domain/guest. --Joe From: libvirt-users-bounces(a)redhat.com [mailto:libvirt-users-bounces@redhat.com] On Behalf Of DeVincentis, Joseph Sent: Wednesday, September 02, 2015 9:21 AM To: &#39;libvirt-users(a)redhat.com&#39; <libvirt-users(a)redhat.com&gt; Subject: [libvirt-users] Error during virt-install, error is not for the guest being instantiated Hi, I have two processes spinning up independent sets of guests, letting the guests run for a while, and tearing them down. The two processes are generally giving their set of guests a different "run-period", so the guest spin-up/tear-down will happen during different cycles/phases. Call these processes A and B, each is currently managing 32 guests. I am seeing an issue, where when process A is spinning guests up, and process B is tearing them down, where on process A, a virt-install will fail, but the error identifies a recently terminated guest which is managed by process B. The guest being instantiated does not get instantiated. "ERROR Error: --network default: Domain not found: no domain with matching uuid 'd39587cb-a2e8-4989-8dce-12a12eb2815e' (process-B-guest-name)" This message is logged by my script at 3:29:23PM. This message is in /var/log/messages; Sep 1 15:29:21 splat04 systemd-machined: Machine qemu-process-B-guest-name terminated. Seems to me that there is some sort of mixup going on, process-B-guest-name is terminated during the virt-install for process-A-guest-name. Any thoughts on this? Like hints on what to look for? This is on Centos7, the version of libvirt is 1.2.8, virt-install is 1.1.0 Thanks - Joe