Dmidecode - UUID Not Settable - RHEL5

[kylea]

HI I have installed ver 1.5 and have created a KVM for RHEL5.4.

The Install was ok, however I cannot connect to the Red Hat Network. The Red Hat support guys said the problem was because dmidecode is not reporting a valid UUID'

"As per the sosreport, from dmidecode we can see that "UUID: Not Settable". The UUID is needed to register the system on RHN. The virtualization software you are using do not provide "UUID" value. So you need to use the virtualization software which provides UUID value.

We recommend you to use Xen to create guests. Let us know if you need any help."

Not sure what that means exactly - but any suggestions gratefully accepted

 

[tom]

KVM is a Redhat project, so I am sure the Redhat support can help you here. (Redhat moves away from Xen, so I do not believe that they recommend Xen any more).

So I suggest you go ask again their support, as it looks you are a paying Redhat customer.

 

[kylea]

I agree - and I actually ran dmidecode and it did return a UUID.

I am doing the RHEL install again - maybe I made an error - then I'll chase up RHEL SUpport

Thanks for the quick reply.

 

[kylea]

I ran dmidecode inside the RHEL5.4 KVM machine and it does NOT report a UUID, its quite different to the output from inside the Debian Proxmox environment

So is this something Red Hat can help with?

 

[dietmar]

Maybe you need to spezify the uuid when starting kvm. You can use that 'args' option (see 'man qm')

args: -uuid %08x-%04x-%04x-%04x-%012x

Please can you test that?

 

[kylea]

Ok sounds like a plan - now for the dumb question -

Is there a file or config where I can add the argument to the startup string - I have been using the Web GUI

 

[kylea]

Bingo - that worked


I edited the file in /etc/qemu-server/101.conf

added

args: -uuid 53D1xxxxxxxxxxxxxxxxxxx

Worked perfectly - thanks