Agent VM issue

[cxs-user]

I have a problem; I have some VMs:

And I'd like to install the agent on them so I can report the IP addresses and such, but every time I try, it crashes, and I don't know why:

[browned]

Have you set the OS Type for the VM's?

I found that if the OS is not set, the agent install tries to install using an .sh script. A restore from Veeam created a machine that had an unknown or no OS set.

Also, if you go into Provising, Instances, select the VM, and then edit you cannot change the OS there. I have to go into the Infastructure, Compute, select the VM, then Edit and under advanced set the Operating System.

[cxs-user]

Originally, on an Ubuntu machine, I had set the operating system to “Linux,” but it didn't work. So I changed it to “Ubuntu 24.04 64-bit” instead of “Linux,” but it automatically changed back to “Linux,” so that's another error:

[browned]

If you download the agent install script for a machine, this should be an option under the install agent. You could test that it can access the VME Manager by copying the urls and testing the access from one of the machines.

Powershell tnc commands are useful. If it cannot download the agent then the install will fail. Also, on the machines, perhaps the try and run the script, elevate as admin, Might be a powershell execution policy issue.

Those are the only issues I have had with agent installs so far. 

[cxs-user]

I tried changing the OS on the ISO by replacing Linux with Ubuntu 24.04
I tried changing the OS on the VM the same way
Downloading the script and installing it manually works.
At first, I hadn’t installed SSH on the machine; after I downloaded it, it still didn’t work.
I also added a user and a password to the ISO (which corresponds to a user on the VM), and then set that user as root, but it still didn’t work.

[browned]

All of the VM's we manage have a Remote Host: x.x.x.x:xx item in the summary page. This Linux machine you list does not. Linux uses port 22 and Windows uses 5985. This is used for installing the agents apparently.

You might need to edit the machine and set the RPC Host. Also, make sure that SSH (Linux) or WINRM (Windows) are configured on the machines depending on OS.

[cxs-user]

Even when I enter the information you mentioned, it still doesn't work:

And since the VM, I've been able to access it just fine:

[dya]

*Please note that this is a machine translation; we apologize if it is difficult to understand.

First, since the “QEMU Guest Agent” is required to retrieve and display the guest OS's IP address, please refer to the information below to verify that the QEMU Guest Agent on the target guest is communicating properly with the host.
*Based on the screenshot, it appears to be a virtual machine deployed from a virtual image using VME. In that case, if you install the Morpheus agent from the virtual machine’s menu, I believe Ubuntu Server and Windows Server should be able to install it as long as that process completes successfully.
For Red Hat-based systems, there seem to be restrictions on QEMU agent commands by default, so you will likely need to relax those restrictions.

■ Virtual Machine (Guest OS: Ubuntu Server 24.04)
root@vme-iscsi3:~# virsh list
Id Name State
---------------------------------
9 hvm-temp-ubuntu running

■When the QEMU Guest Agent is running on the guest OS and communicating correctly with the host
root@vme-iscsi3:~# virsh domifaddr hvm-temp-ubuntu --source agent
Name MAC address Protocol Address
-------------------------- -----------------------------------------------------
lo 00:00:00:00:00:00 ipv4 127.0.0.1/8
- - ipv6 ::1/128
eth0 52:54:00:e1:06:5c ipv4 172.16.1.211/24
- - ipv6 fe80::5054:ff:fee1:65c/64

■If the QEMU guest agent is stopped on the guest OS and cannot communicate properly with the host
root@vme-iscsi3:~# virsh domifaddr hvm-temp-ubuntu --source agent
error: Failed to query for interfaces addresses
error: Guest agent is not responding: QEMU guest agent is not connected

[cxs-user]

Thank you so much for your help—that solved my problem. I had forgotten to install QEMU.