Thank you.
I checked both the “HVM Manager” and other Linux virtual machines.
The QEMU guest agent seems to be working properly, and the Morpheus agent is also installed.
I have some concerns about the shutdown process for HVM virtual machines.
At the very least, when shutting down the “HVM Manager,” I do not use the Web UI and instead manually execute “virsh shutdown” on the host.
I’m concerned that “virsh destroy” is being executed only about 10 seconds after “virsh shutdown” — such a very short amount of time.
I am only including partial logs.
----------------------------------------------------
Guest 1: Ubuntu Server 24.04
■Host
・journalctl
May 02 03:09:08 vme-iscsi3 sudo[340011]: morpheus-node : PWD=/tmp ; USER=root ; COMMAND=/usr/bin/virsh shutdown esxi-ubuntu
May 02 03:09:13 vme-iscsi3 systemd-machined[903]: Machine qemu-2-esxi-ubuntu terminated.
May 02 03:09:19 vme-iscsi3 sudo[340114]: morpheus-node : PWD=/tmp ; USER=root ; COMMAND=/usr/bin/virsh destroy esxi-ubuntu
・QEMU Guest Agent check
# virsh domifaddr esxi-ubuntu --source agent
Name MAC address Protocol Address
-------------------------------------------------------------------------------
lo 00:00:00:00:00:00 ipv4 127.0.0.1/8
- - ipv6 ::1/128
enp3s0 52:54:00:4b:f5:16 ipv4 172.16.1.222/24
- - ipv6 fe80::5054:ff:fe4b:f516/64
#
# virsh qemu-agent-command esxi-ubuntu '{"execute":"guest-exec", "arguments":{"path":"/bin/ls"}}' --pretty
{
"return": {
"pid": 1582
}
}
#
■Guest
・journalctl
May 02 03:09:08 esxi-ubuntu systemd-logind[742]: System is powering down (hypervisor initiated shutdown).
May 02 03:09:11 esxi-ubuntu systemd-journald[346]: Journal stopped
■Observations
・The QEMU Guest Agent in the guest appears to be working normally.
・virsh shutdown is executed on the host, and the shutdown process starts in the guest.
・The guest’s journal ends with "Journal stopped".
・About 11 seconds after running virsh shutdown, virsh destroy is executed on the host (after the systemd-machined VM termination log).
----------------------------------------------------
----------------------------------------------------
Guest 3: Ubuntu Server 24.04 (HVM manager)
■Host
・journalctl
May 02 05:34:25 vme-iscsi1 sudo[8056]: morpheus-node : PWD=/tmp ; USER=root ; COMMAND=/usr/bin/virsh shutdown vme-iscsi-manager
May 02 05:34:36 vme-iscsi1 sudo[8076]: morpheus-node : PWD=/tmp ; USER=root ; COMMAND=/usr/bin/virsh destroy vme-iscsi-manager
May 02 05:34:38 vme-iscsi1 systemd-machined[911]: Machine qemu-1-vme-iscsi-manager terminated.
・QEMU Guest Agent check
# virsh domifaddr vme-iscsi-manager --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:61:51:37 ipv4 172.16.2.100/24
- - ipv6 fe80::5054:ff:fe61:5137/64
#
# virsh qemu-agent-command vme-iscsi-manager '{"execute":"guest-exec", "arguments":{"path":"/bin/ls"}}' --pretty
{
"return": {
"pid": 58454
}
}
#
■Guest
・journalctl
May 02 05:34:25 vme-iscsi-manager systemd-logind[683]: System is powering down (hypervisor initiated shutdown).
May 02 05:34:28 vme-iscsi-manager systemd[1]: Stopped finalrd.service - Create final runtime dir for shutdown pivot root.
■Observations
・The QEMU Guest Agent appears to be working normally.
・virsh shutdown is executed on the host, and shutdown starts in the guest.
・Unlike Guest 1, there is no "Journal stopped" message at the end of the guest logs (last log is at 05:34:28).
・About 11 seconds after virsh shutdown, virsh destroy is executed (before the systemd-machined termination log).
・It appears that the guest was terminated by virsh destroy.
----------------------------------------------------
