OK, I was expecting it to maintain a list internally (at least for the things it knows about) so that the auto property in the domxml can work nicely, but I suppose it would still need to fallback to letting the kernel reject an already taken cid number anyways (eg: due to a manually executed qemu outside of libvirt), so either way the list would not be authoritative.<div><br></div><div>Thanks,</div><div>Brian<br><div dir="auto"><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 30, 2019, 08:36 Daniel P. Berrangé <<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jan 29, 2019 at 10:07:16AM -0600, Brian Kroth wrote:<br>
> Other than dumping and parsing the config for all running VMs, is<br>
> there a way to get the current map of vsock cids allocated to their VM<br>
> domains?<br>
<br>
What you describe is the only supported approach from libvirt's POV.<br>
<br>
Regards,<br>
Daniel<br>
-- <br>
|: <a href="https://berrange.com" rel="noreferrer" target="_blank">https://berrange.com</a>      -o-    <a href="https://www.flickr.com/photos/dberrange" rel="noreferrer" target="_blank">https://www.flickr.com/photos/dberrange</a> :|<br>
|: <a href="https://libvirt.org" rel="noreferrer" target="_blank">https://libvirt.org</a>         -o-            <a href="https://fstop138.berrange.com" rel="noreferrer" target="_blank">https://fstop138.berrange.com</a> :|<br>
|: <a href="https://entangle-photo.org" rel="noreferrer" target="_blank">https://entangle-photo.org</a>    -o-    <a href="https://www.instagram.com/dberrange" rel="noreferrer" target="_blank">https://www.instagram.com/dberrange</a> :|<br>
</blockquote></div></div></div>