This content has been marked as final. Show 4 replies
TWLinux wrote:Unfortunately, only firstname.lastname@example.org can see the ULN side of things, so they're your best bet for assistance. If you didn't get any response, just email them again.
I sent an email to the above listed email address and after some basic question answering never got another response.
If running on Xen:
1) Check /sys/hypervisor/uuid. If it exists, is non-zero, and is unreadable, you have hit a bug.
2) This condition is created by rebooting instead of stopping then starting.
3) A stop and start will correct the condition.
Long Version (with more details):
Attempted to run:
$ ulnreg_ks username <<acct>> password <<pass>> csi <<CSI>> profile <<profile name>>
System needs a non-empty identifier
Was told this means that the system can't find its uuid.
Digging deeper you can see the python code that does this under /usr/share/rhn/up2date_client/rhnreg.py.
Looking at the comments for get_virt_info():
This function returns the UUID and virtualization type of this system, if
it is a guest. Otherwise, it returns None. To figure this out, we'll
use a number of heuristics (list in order of precedence):
1. Check /proc/xen/xsd_port. If exists, we know the system is a
2. Check SMBIOS. If vendor='Xen' and UUID is non-zero, we know the
system is a fully-virt guest; exit.
3. Check /sys/hypervisor/uuid. If exists and is non-zero, we know
the system is a para-virt guest; exit.
4. If non of the above checks worked; we know we have a
non-xen-enabled system; exit.
My system is OEL 6.3 running on citrix xen 6.1.
1) False (is not a host)
2) False (no bios entrypoint; no data in dmidecode)
3) Found a bug with this one. File exists but is not-readable due to bug.
4) Exits this and ends up with no UUID even though it is a virtual system.
Cross referenced from https://answers.launchpad.net/nova/+question/214413.
A xen guest / host can get into a state where /sys/hypervisor/uuid is unreadable but exists.
It is triggered by rebooting the guest instead of halting and then starting.
Simple solution. Halt the system and then start it.
Code Fix: Unknown (It might have to be in kernel or xen hypversior not sure which)
Thanks for pointing me in the right direction. Hope this post might help someone a bit down the road.
Edited by: TWLinux on Jan 28, 2013 3:46 PM -- Typographical errors