- No graphics hardware, beyond the basic console; no gui
- All DomU's tested are based on a single LVM volume as the root filesystem and another as swap.
- All use bridged LANs, some connected to a real nic, some not.
- the DomU system I have not upgraded has a pci passthrough for the USB controller.
- hardware i5-9600K, Z390 chipset, 16GB ram
I cannot get a system to shutdown either by a shutdown/reboot command within the VM, nor by "xl shutdown/reboot" issued from Dom0.
In a spirit of adventure I upgraded a second VM - with the same result.
I ran up a new bullseye installation on a spare old PC and having both Dom0 and Domu as fresh Bullseye installs did not show the shutdown problems.
So, I figured, upgrade Dom0 to Bullseye, but the problem was not fixed.
I created a fresh minimal DomU on the old system and the shutdown still fails, but with slightly different information shown:
On the working fresh system (reboot from a console login):
On the failing system that was a fresh DomU install, I can run xl shutdown and then any time later I can open the console withjournal records "[ OK ] Reached target Power-Off"
systemd-shutdown[1] Syncing filesystems
systemd-shutdown[1] sending SIGTERM to remaining processes ...
then console shows journald received SIGTERM (and nothing more is in journal)
root filesystem is remounted r/o
systemd-shutdown[1] shows about 16 entries listing the shudown process, finishing with..
"systemd-shutdown[1]: Powering off" and
"reboot:system halted"
xl console <dom>.
So I can go in and out of console view until I destroy the VM.The console displays the same as above, getting to
"systemd-shutdown[1]: Powering off",
but never the final "system halted".
On the failing systems that were upgraded the console shows no messages from systemd-shutdown[1], although it looks to be getting to the same place because is does show the message about journald shutting down and one line about the root filesystem being remounted.
Conclusion so far - the common factor is my Dom0 (either buster or bullseye) together with bullseye on the DomU; either:
- some old configuration setting has come back to bite me, or
- something about the hardware is not compatible?