Re: [libvirt] [libvirt PATCH] Port-profile ID support using IFLA_VF_PORT_PROFILE netlink msg
"Daniel P. Berrange" <berrange(a)redhat.com> wrote on 05/12/2010 08:48:58
AM:
On Sat, May 08, 2010 at 10:13:36PM -0400, Stefan Berger wrote:
> Scott Feldman <scofeldm(a)cisco.com> wrote on 05/08/2010 07:28:11 PM:
>
> > VSI Manager ID 1 octet
> > VSI Type ID 3 octets
> > VSI Type ID Version 1 octet
> > VSI Instance ID 16 octets <-- taken care of via
> dimdecode
The code can't rely on using dmidecode I'm afraid. Far too many
manufacturers / machines have SMBIOS UUID field filled with complete
garbage. eg my main server shows
# dmidecode |grep -i uuid
UUID: Not Settable
So if we need a host UUID, I think we need to be able to either set it
in
the XML, or have it set in a per host config for the QEMU driver in
libvirt.
I wouldn't make it QEMU specific. It should probably go into libvirt.conf,
but
then libvirt.conf would need to be modified on every machine when
installed.
How should the code react if no valid UUID is found in the config file?
Create a temporary one that changes with every restart of libvirt? Also
dmidecode
should probably be used on those machine where it returns a valid UUID.
Once that would be done, we could show the UUID via 'virsh capabilities'
so management software can find it.
If above doesn't sound right, then providing it via the XML in vsi is
probably
the way to go.
Stefan
Daniel
--
|: Red Hat, Engineering, London -o-
http://people.redhat.com/berrange/:|
|: http://libvirt.org -o- http://virt-manager.org -o-
http://deltacloud.org:|
|: http://autobuild.org -o-
http://search.cpan.org/~danberr/:|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742
7D3B
9505 :|
Attachments:
- attachment.html (text/html — 3.1 KB)