[Ovirt-devel] [PATCH]: Rewrite the ovirt-identify-node in bash

[Daniel P. Berrange]

On Wed, Jun 11, 2008 at 03:22:16PM +0200, Chris Lalancette wrote:
> Alan Pevec wrote:
> > ACK for 1:1 replacement
> > 
> > just one thing:
> > 
> >> +# gather our information
> >> +uuid=`hostname -f`
> > 
> > This matches the current behavior, but ideally we'd use HAL here:
> > hal-get-property --udi /org/freedesktop/Hal/devices/computer --key system.hardware.uuid
> > 
> > Problem is that hal RPM has lot of deps, so it would not help shrinking effort.
> > Any ideas about a portable, but w/o HAL, way to get hardware UUID?
> 
> In theory we could use dmidecode; the problem is that, as far as I can tell, KVM
> guests all have exactly the same UUID.  This is probably a bug we should address
> in KVM itself, but until that is fixed, I don't think we can rely on it for much
> of anything.

Nope, KVM guests don't have any UUID at all - as far as the guest can
see it at least.

Someone really badly needs to implement  SMBIOS support for QEMU so we can
expose the UUID.  Upstream QEMU is about to get a -uuid command line flag,
but its only exposing the UUID via  VMWare's backdoor. SMBIOS is what
Xen HVM has & HAL will 'just work' if we add SMBIOS

Dan.
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|