Systemd-nspawn freezes when switching --link-journal settings. Steps to reproduce: 1) Run "systemd-nspawn --directory=/some/dir --boot --link-journal=host" 2) Quit that VM (I used ^]^]^]) 3) Run "systemd-nspawn --directory=/some/dir --boot --link-journal=guest" Expected result: A VM is started with the journal in guest mode. Actual result: The VM is not started, systemd-nspawn stops responding. I need kill -9 to stop the systemd-nspawn. The order of host/guest mode is not important. The problem persists till /var/log/journal/{VM_machine_id} is deleted.
Hi Tobias, Thank you for reporting, I'm able to reproduce and I've located the problem! There is also another bug that keeps systemd-nspawn blocking, thus the kill -9 I'll send patches to the mailing list Thanks.
I've just posted patches: http://lists.freedesktop.org/archives/systemd-devel/2014-April/018596.html systemd-nspawn should be able to terminate cleanly on errors, for the bind mount I'm not sure we'll see what others think! Thanks.
Patch applied as http://cgit.freedesktop.org/systemd/systemd/commit/?id=e866af3a. The issue seems fixed in my testing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.