Thanks for the additional information. You are right: `machinectl list`
does list the VMs managed by libvirt:

====================================

$ virsh list
 Id   Name                    State
---------------------------------------
 9    rbasak-gu-build         running
 10   rbasak-gu               running
 11   rbasak-gu-focalorigin   running
 12   paride-uvt-i            running

$ machinectl list
MACHINE                       CLASS SERVICE      OS VERSION ADDRESSES
qemu-10-rbasak-gu             vm    libvirt-qemu -  -       -        
qemu-11-rbasak-gu-focalorigin vm    libvirt-qemu -  -       -        
qemu-12-paride-uvt-i          vm    libvirt-qemu -  -       -        
qemu-9-rbasak-gu-build        vm    libvirt-qemu -  -       -        

4 machines listed.

====================================

But in my case stopping systemd-machined does not affect the VMs:

====================================

$ sudo systemctl stop systemd-machined

$ virsh list
 Id   Name                    State
---------------------------------------
 9    rbasak-gu-build         running
 10   rbasak-gu               running
 11   rbasak-gu-focalorigin   running
 12   paride-uvt-i            running

# ^^ note, still running ^^

$ uvt-kvm ssh paride-uvt-i
Welcome to Ubuntu Impish Indri (development branch) (GNU/Linux 
5.11.0-20-generic x86_64)

[...]

ubuntu@paride-uvt-i:~$ uptime
 14:40:51 up 3 days,  4:58,  1 user,  load average: 0.00, 0.00, 0.00

# ^^ and actually working with no downtime ^^

ubuntu@paride-uvt-i:~$ logout
Connection to 192.168.122.184 closed.

$ systemctl is-active systemd-machined
inactive

# ^^ machined still inactive ^^

====================================

However this is done using Impish (both host and guest) and not Focal.

TODO to complete the triage of this bug is: try the same on Focal. If it
works (= stopping systemd-machined doesn't stop the VMs) then the
reported problem may be a local configuration issue. Otherwise we'll
have to search for what's causing the difference.

@Helmut: feedback from your side is appreciated here. If you can try to
reproduce the issue with Impish and share your findings, great! Also I
think it's worth triple-checking that the your misbehaving Focal system
doesn't have any change that can cause machined kill the VMs when it
stops. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939577

Title:
  Missing dependency in libvirt-guests.service leads sometimes to killed
  VMs on host shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1939577/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to