<br><tt><font size=2>"Daniel P. Berrange" <berrange@redhat.com>
wrote on 05/12/2010 10:09:41 AM:<br>
<br>
> > <br>
> > I wouldn't make it QEMU specific. It should probably go into
libvirt.conf, <br>
> > but<br>
> > then libvirt.conf would need to be modified on every machine
when <br>
> > installed.<br>
> > How should the code react if no valid UUID is found in the config
file?<br>
> > Create a temporary one that changes with every restart of libvirt?
Also <br>
> > dmidecode<br>
> > should probably be used on those machine where it returns a valid
UUID.<br>
> <br>
> How do we decide that dmidecode is showing a valid UUID though. Is
a<br>
> UUID of all 0's, all 1's or all F's valid ? </font></tt>
<br>
<br><tt><font size=2>With high probability, 32 hex chars that are the same
can probably be considered 'wrong'.</font></tt>
<br>
<br><tt><font size=2>Some details on how one could handle the different
cases of valid/invalid UUIDs:</font></tt>
<br>
<br><tt><font size=2> libvirtd.conf
dmidecode
handling</font></tt>
<br>
<br><tt><font size=2> valid UUID
valid UUID libvirtd.conf
UUID overrides dmidecode's UUID</font></tt>
<br><tt><font size=2> invalid UUID
invalid UUID generate a
temporary one; new one after libvirtd restart</font></tt>
<br><tt><font size=2> valid UUID
invalid UUID use valid UUID</font></tt>
<br><tt><font size=2> invalid UUID
valid UUID use valid UUID</font></tt>
<br>
<br><tt><font size=2> Stefan</font></tt>
<br>