Install Management Agent

[Kyle Hagborg]

Hello,

 

I got 2 freshly installed XenServer 7.6 hosts, fully updated.  I'm creating Ubuntu 18.04 VM's and despite installing xentools, under the General tab for each of these VM's the virtualization state reads "Install Management Agent". 

 

I've mounted the guest-tools.iso as root and ran the install.sh without error, yet all my Ubuntu VM's don't recognize this.  What am I missing here?

[Alan Lantz]

Thats a good question. Its really just running the script that installs the xe-guest-utilities. Do you see it unpacking,

processing, and prompting you to restart the VM ?

 

--Alan--

 

[Kyle Hagborg]

Yes, it unpacks, processes, and then prompts me to reboot. 

 

I don't think there is any performance hit, that I have accounted for at least yet, as it appears to be an erroneous status.  It is really just more of an annoyance.

[Tobias Kreidl]

Did XenTools actually get installed or not? If so, it's probably a cosmetic artifact.

 

-=Tobias

[Alan Lantz]

What concerns me is I have 18.04 Bionic Beaver with Xentools installed and mine says optimized (version 7.4 installed).

 

--Alan--

 

[Kyle Hagborg]

Yes, it is installed.  Guess it is just cosmetic then.

 

ls -ltr /opt/xensource/packages/iso/

-rw-r--r-- 1 root root 71335936 Aug 24 04:03 guest-tools-7.32.0-2.iso
-rw-r--r-- 1 root root 46180352 Aug 24 04:04 XenCenter.iso

 

 

[Alan Lantz]

That would show you the guest utilities available on XenServer, but not whats installed on the VM.

From Ubuntu run dpkg -l | grep "xe-guest-utilities" to see if its installed.

 

--Alan--

 

[Tobias Kreidl]

Or look in XenCenter and see if you see in the list of VMs on the server it's running on if it shows as being "non-optimized" or similar.

 

-=Tobias

[Damián DArrigo]

Same problem here with all my Ubuntu 18.04 servers.

[Alan Lantz]

If the management agent/XenTools isn't installed then right click the VM will only show force shutdown

and force reboot. If shutdown/restart are there as well then its just lying and the tools really are installed.

 

--Alan--

 

[Damián DArrigo]

Perfect. The shutdown and restart options are there. But why isn't it there the "used memory" tab?

[Alan Lantz]

I have a linux image I imported from a vendor that does the same thing. Near as I can tell its because under the 

general tab its running in PV mode instead of HVM like my other Ubuntu servers are.

 

--Alan--

 

 

[Kyle Hagborg]

Mine are running in HVM mode and have this issue.  As we've said earlier, just a cosmetic annoyance.  Maybe 7.7 will fix it?  Should be out soon I believe.  

[Alan Lantz]

Strange as mine shows Optimized on XenServer 7.6

 

 

 

 

--Alan--

 

[Kyle Hagborg]

Hmm, interesting.  I find it odd that it mine says "Not able to receive updates from Windows Update" for a Linux VM.

 

[Damián DArrigo]

Same here. We can only hope they fix this for 7.7.

[Alan Lantz]

That is weird that yours states it can't receive updates from Windows updates ! I did notice you aren't 

on 18.04.2 like I am, maybe thats the difference ?

 

--Alan--

 

[Damián DArrigo]

We still have this problem with our Ubuntu Servers, regarding the version. In one of them we have the following error when installing the tools:

[Konrad Ruess]

Hey guys,

I know, it's a bit late, but I had this issue with XenCenter stating "Management Agent not installed" after I switched an older Ubuntu 18.04 LTS from PV to HVM. All was well before the switch.

Comparing the metadata to a freshly built Ubuntu 18.04 from the latest Ubuntu template (16.04 in my case with XenServer 7.1), I stumbled over these settings that were different. Changing them accordingly on the guest did the trick:

xe vm-param-get uuid=<vm-uuid> param-name=platform

I've had to switch these ones after stopping the guest VM:

xe vm-param-set uuid=<vm-uuid> platform:nx=true
xe vm-param-set uuid=<vm-uuid> platform:viridian=false
xe vm-param-set uuid=<vm-uuid> platform:acpi=1
xe vm-param-set uuid=<vm-uuid> platform:device_id=0001

A boot later, all was just fine. ?

So, the problem most probably was that the guest VM contained some old settings form an ancient template used to create the VM in the beginning, that never changed to the more modern settings. I hope this helps others in the same situation.

BfN, Konrad