[libvirt] list vsock cids allocated to VMs? - Devel - Libvirt List Archives

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

December

[libvirt] list vsock cids allocated to VMs?

[libvirt] [PATCH 0/7] Add support...

[libvirt] [PATCH 00/11] qemu:...

Brian Kroth

Tuesday, 29 January 2019 Tue, 29 Jan '19

10:07 a.m.

Other than dumping and parsing the config for all running VMs, is there a way to get the current map of vsock cids allocated to their VM domains? Thanks, Brian

Reply

Show replies by date

Daniel P. Berrangé

Wednesday, 30 January Wed, 30 Jan

8:36 a.m.

On Tue, Jan 29, 2019 at 10:07:16AM -0600, Brian Kroth wrote:

Other than dumping and parsing the config for all running VMs, is there a way to get the current map of vsock cids allocated to their VM domains?

What you describe is the only supported approach from libvirt's POV. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

Reply

Brian Kroth

11:25 a.m.

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. Thanks, Brian On Wed, Jan 30, 2019, 08:36 Daniel P. Berrangé <berrange(a)redhat.com> wrote:

On Tue, Jan 29, 2019 at 10:07:16AM -0600, Brian Kroth wrote: > Other than dumping and parsing the config for all running VMs, is > there a way to get the current map of vsock cids allocated to their VM > domains? What you describe is the only supported approach from libvirt's POV. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

Reply

Daniel P. Berrangé

11:33 a.m.

On Wed, Jan 30, 2019 at 11:25:25AM -0600, Brian Kroth wrote:

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.

No libvirt doesn't keep any list. When allocating one automatically it just iterates over IDs, trying to acquire exclusive access to one from the kernel until it succeeds. IOW the kernel has the authoritative list Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

Reply

2123

days inactive

2124

days old

devel@lists.libvirt.org

Manage subscription

3 comments

2 participants

tags (0)

participants (2)

Brian Kroth
Daniel P. Berrangé