Hi Christian, Thanks for your attention. I replicated the issue and here is the journal log for today.
Regards Pedro Serrano On Wed, 2021-04-21 at 11:08 +0000, Christian Ehrhardt wrote: > Hi Pedro, > > > Wouldn't it be beneficial for all guests to be shutdown before > unmounting all filesystems? > > Yes on first sight that looks like a compelling suggestion. > But i've learned the hard way that usually adding dependencies > eventually breaks more things than it fixes - so let us first try to > understand what to expect and what happened. > > > The ordering at the moment includes: > - libvirt-guests.service > - virt-guest-shutdown.target > - libvirtd.service > > Of these the "big one" is libvirtd.service which has > After=network.target > After=local-fs.target > After=remote-fs.target > And many more which imply further lateness on startup. > > libvirt-guests.service is what shuts down the guests and starts as > After=libvirtd.service > and thereby after all of the above. > > virt-guest-shutdown.target exists to allow people to hook arbitrary > things into this chain in case any thing needs to be done. > Note: In most cases it is better t identify what a local system has > that makes it special and set it up to go down before this. See the > discussion and references from > https://bugzilla.redhat.com/show_bug.cgi?id=1401054 for this. > > On shutdown usually the order of these is reversed - I'd expect that > libvirt-guests.service needs to stop before libvirtd.service stops > (which also is reasonable as it needs to interact with libvirt). > And libvirt.service should need to be passed to leave the > local/remote-FS targets on the way out, but targets might be more > special in this regard. > > Therefore the question becomes - which FS or FS-target was > stopped/cut in your case before libvirt.service was stopped. > Could you maybe share the journal of that boot so that we can try to > dissect what was going down beofore it? > > You can access those with > $ journalctl --list-boots > And then select the right one and redirect it into a file like > $ journalctl -b <number> > logfile > > ** Bug watch added: Red Hat Bugzilla #1401054 > https://bugzilla.redhat.com/show_bug.cgi?id=1401054 > > ** Changed in: libvirt (Ubuntu) > Status: New => Incomplete > ** Attachment added: "ps01ubx-journalctl-2021-04-23-1441.txt" https://bugs.launchpad.net/bugs/1924494/+attachment/5491583/+files/ps01ubx-journalctl-2021-04-23-1441.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924494 Title: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
