<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Don't you have to install the rhn-virtualization-host package? <br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">Date: Thu, 11 Apr 2013 09:35:44 +0200<br>From: jma@schaubroeck.be<br>To: spacewalk-list@redhat.com<br>Subject: Re: [Spacewalk-list] Re-registering clients causing problem with client-type identification<br><br>
<div class="ecxmoz-cite-prefix">Op 10/04/2013 21:18, Michal Bruncko
schreef:<br>
</div>
<blockquote cite="mid:5165BB02.8000902@zssos.sk">Hello
again,
<br>
<br>
I will try to formulate my question another way: how the client is
detecting that if it is the virtual guest or standalone station?
As I can see from VM properties within Spacewalk, this system
contain virtualization and UUID fields. From which system resource
is this information provided from client to server?
<br>
</blockquote>
Are you talking about the icon? I've also noticed that depending on
where you view the system it might not display the right icon. I
have a bunch of VM's all with the correct Virtualization info, that
have the right icon in the "All" systems view and get listed
correctly in the "Virtual Systems" list.<br>
<br>
When I look at the systems list of a group however they all show the
"physical machine" icon. I've never really paid further attention to
it but that might be a bug.<br>
<br>
<blockquote cite="mid:5165BB02.8000902@zssos.sk">I
remember that I had similar problem once I've used 1.2 or 1.3
version of Spacewalk satellite.
<br>
<br>
thanks
<br>
<br>
michal
<br>
<br>
On 31. 3. 2013 20:37, Michal Bruncko wrote:
<br>
<blockquote>Hello list,
<br>
<br>
I am in following situation:
<br>
- I've successfully installed and using spacewalk 1.9 with ~20
clients for some time
<br>
- I've decided to rename one of spacewalk client
(paravirtualized guest on XenServer) following way:
<br>
-- delete system entry from Spacewalk server (using classic
system deletion)
<br>
-- rename hostname (editing /etc/sysconfig/network, /etc/hosts
file) followed with restart
<br>
-- and try to re-register with spacewalk using "--foce"
parameter to rhnreg_ks
<br>
</blockquote>
</blockquote>
I'm wondering why you would delete a system only to have a hostname
change correctly shown in spacewalk? You can get the client to
update its system info (hostname, hardware, etc) by running the <b>rhn-profile-sync</b>
command. The spacewalk profile name (separate from the hostname) can
be changed in the webui or via spacecmd.<br>
<br>
Regards,<br>
Jeremy<br>
**** DISCLAIMER ****<br><a href="http://www.schaubroeck.be/maildisclaimer.htm" target="_blank">http://www.schaubroeck.be/maildisclaimer.htm</a><BR>
<br>_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list</div> </div></body>
</html>