On Tue, Jul 21, 2020 at 08:46:55AM -0400, John Ferlan wrote: > > Upon further reflection and some memory jiggling... > > virsh -c storage:///system capabilities > <capabilities> > > <pool> > <enum name='type'> > <value>dir</value> > <value>fs</value> > <value>netfs</value> > <value>logical</value> > <value>iscsi</value> > <value>iscsi-direct</value> > <value>scsi</value> > <value>mpath</value> > <value>disk</value> > <value>rbd</value> > <value>sheepdog</value> > <value>gluster</value> > <value>zfs</value> > </enum> > </pool> > > </capabilities> > > But yeah, without the -c storage:///system one won't see the results > because 'npools == 0' when virCapabilitiesFormatStoragePoolXML is called > from virCapabilitiesFormatXML unless it's the storage driver URI. Err, don't you mean "virsh pool-capabilities". The "capabilities" command is exclusively for the virt driver usage, not storage. In the new modular daemon work, "capabilities" API will never be sent to the storage daemon. 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 :|
