search for: virnodedevicelookupbyname

Displaying 5 results from an estimated 5 matches for "virnodedevicelookupbyname".

2020 Mar 18
2
pointer to "spice" device by virNodeDeviceLookupByName
Is possible to get a pointer to «spice» by virNodeDeviceLookupByName API? What «name» I should use for? Thanks a lot!     -- Андрей Фокин
2020 Mar 18
0
Re: pointer to "spice" device by virNodeDeviceLookupByName
On Wed, Mar 18, 2020 at 01:10:41PM +0300, Андрей Фокин wrote: > > Is possible to get a pointer to «spice» by virNodeDeviceLookupByName API? > What «name» I should use for? The virNodeDevicePtr APIs are for getting information about physical devices on a host. spice is not a device, it is a remote framebuffer protocol used by QEMU So the question doesn't really make any sense. Regards, Daniel -- |: https://berrange.com...
2020 Mar 18
2
Re[2]: pointer to "spice" device by virNodeDeviceLookupByName
...ription for spice params, like it could be possible for physical devices?   >Среда, 18 марта 2020, 13:21 +03:00 от Daniel P. Berrangé <berrange@redhat.com>: >  >On Wed, Mar 18, 2020 at 01:10:41PM +0300, Андрей Фокин wrote: >> >> Is possible to get a pointer to «spice» by virNodeDeviceLookupByName API? >> What «name» I should use for? >The virNodeDevicePtr APIs are for getting information about physical >devices on a host. > >spice is not a device, it is a remote framebuffer protocol used by QEMU > >So the question doesn't really make any sense. > >Regards,...
2020 Mar 18
0
Re: pointer to "spice" device by virNodeDeviceLookupByName
On Wed, Mar 18, 2020 at 01:25:28PM +0300, Andrey Fokin wrote: > > Thanks, clear! > But may be is a method to get XML description for spice params, like it could be possible for physical devices? virDomainGetXMLDesc() will give you the XML config for the guest. You can get specific data from this using many common XML APIs. Regards, Daniel -- |: https://berrange.com -o-
2016 Mar 17
1
Questions regarding hostdev scsi
...between scsi_4_0_0_0 and scsi_generic_sg1. At this point, we present user with devices matching capability='scsi', therefore to get the information 2 additional parses of the tree would have to be done. Other way would be reporting 'scsi_generic' capability, where only 2 additional virNodeDeviceLookupByName calls would be required (to descend 2 levels). Is there anything *really* wrong with this approach? Are there any other options without dynamic ownershit? Seclabel doesn't seem to be available. I'm thankful for any hints. Regards, mpolednik