Re: [libvirt-users] Descriptions of mdev types?
On Tue, Nov 19, 2019 at 05:38:54PM +0100, Milan Zamazal wrote: > Hi, when retrieving an mdev device info using `virsh nodedev-dumpxml' or > the libvirt API, something like the following is returned: > > > > GRID M60-2B4 > vfio-pci > 4 > > ... > > > Besides device_api, available_instances and (optional) `name', > `description' of the given mdev type may be optionally provided in > /sys/.../mdev_supported_types/... for each of the available mdev types. > I can see in the sources that libvirt doesn't try to retrieve it -- is > it intentionally or is it just an omission? If the latter, could it be > added, please? It looks like a useful piece of information for the user > to get an idea what the given mdev type means. The reasoning we had about not including the "description" attribute when we introduced mdevs to libvirt's nodedev driver was that there was no way for NVIDIA and Intel to agree on the values to be exposed by the attribute - especially the data NVIDIA puts in there (like you already said) is useful, but there was also no agreement on extracting the data into a different attribute (a set of attributes) and make them structured within the XML. Which brings me to the actual content of the "description" attribute, it contains unstructured free-form text and we didn't want to expose that kind of thing in the XML even though it just so happens that NVIDIA put some interesting data in it - since the attribute is optional and free-form, one day, you find the useful data you're interested in now, but tomorrow that may not be the case anymore and can easily change. I've got no problem with the idea of exposing some kind of description as part of the XML per se, the problem I see is that someone will try and start parsing the description field because of the potentially useful data and if it changes and I'm afraid complaints will head our way even though we cannot guarantee anything wrt to that specific field (I'm still open to a discussion though). Regards, Erik ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
[libvirt-users] Descriptions of mdev types?
Hi, when retrieving an mdev device info using `virsh nodedev-dumpxml' or the libvirt API, something like the following is returned: GRID M60-2B4 vfio-pci 4 ... Besides device_api, available_instances and (optional) `name', `description' of the given mdev type may be optionally provided in /sys/.../mdev_supported_types/... for each of the available mdev types. I can see in the sources that libvirt doesn't try to retrieve it -- is it intentionally or is it just an omission? If the latter, could it be added, please? It looks like a useful piece of information for the user to get an idea what the given mdev type means. Thanks, Milan ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
[libvirt-users] FYI mail problems for libvirt lists
It has come to our attention that many, possibly even all, people with non-redhat.com email addresses are unable to send mail to most libvirt mailing lists, receiving bounce messages saying the address doesn't exist eg Final-Recipient: rfc822; libvirt-users@redhat.com Action: failed Status: 5.0.0 Remote-MTA: dns; us-smtp-inbound-1.mimecast.com Diagnostic-Code: smtp; 550 Invalid Recipient - https://community.mimecast.com/docs/DOC-1369#550 [boadZMN8PrGodBBK6pzKWg.us309] In my testing, libvir-l...@redhat.com is the only list that is currently accepting incoming mail from non-redhat.com addresses. I see bounces from libvirt-users@redhat.com, libvirt...@redhat.com, libvirt-annou...@redhat.com and libvirt-secur...@redhat.com, as well as from the undocumented alias libvirt-l...@redhat.com We believe outgoing mail delivery is still working normally in all cases. The problems appear to be caused by some changes that Red Hat administrators made to the email infrastructure recently. We have a severity 1 ticket open for this issue and are taking all possible steps to escalate it & get it resolved at the soonest opportunity. In the mean time if any users need assistance with libvirt questions, please feel free to ignore our normal guidance and use the main development list libvir-l...@redhat.com for questions, as this appears to still be working. Alternatively you can use IRC #virt on irc.oftc.net If you need to report any security issues with libvirt, please try the libvirt-secur...@redhat.com list first, but if you get a bounce then email myself directly. Please accept our apologies for the disruption this is causing to the libvirt mailing lists. 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 :| ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
