[Spacewalk-list] Indentifying host type

[Brian Kosick]

That's caused by haldaemon not running...

service haldeamon start

HAL depends on messagebus so if it fails to start, do this...

service messagebus restart
service haldaemon restart

You should be OK...   Other than that, I'm relatively new to spacewalk
and rhnreg_ks as well and I can't answer the rest of your question...

Brian


On Mon, 2009-01-05 at 07:17 -0700, Gerhardus.Geldenhuis at gta-travel.com
wrote:
> Hi
> Can anyone comment on how the registration process using rhnreg_ks
> determines the system type. Eg how does it know whether the machine you
> are registering is a Virtual Guest, Virtual Host or a non-Virtual
> system. 
> 
> We have some Citrix xen servers:
> cat /etc/redhat-release
> XenServer release 4.1.0-7843p (xenenterprise)
> 
> that is not picked up as Virtual Host servers when we register them in
> spacewalk and instead are just registered as "Non-Virtual System"
> 
> I do get the following error when registering:
> Error reading hardware information: dbus_bindings.DBusException
> Error reading DMI information: dbus_bindings.DBusException
> 
> But I get that for other machines too when registering, and this error
> has not prevented spacewalk from correctly indentifying whether the
> machine is a xen guest or a physical server and thus I believe it is not
> related.
> 
> Regards
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list