Hello Michael,
The KVM domain is "auto-started" by libvirtd, and that appears to result
in systemd-machined starting up.
Stopping systemd-machined, then stopping and re-starting the virtual
machine using virsh causes systemd-machined to restart along with it.
I've tried both disabling and masking the systemd-machined service using
systemctl, but that appears to have no effect.
Regards,
John Pearson.
On 28/03/17 16:09, Michael Biebl wrote:
Am 27.10.2016 um 23:13 schrieb John Pearson:
Hello Michael,
Thanks for looking at this.
On 22/10/16 11:07, Michael Biebl wrote:
Am 27.07.2016 um 02:59 schrieb John Pearson:
Hello Michael,
After the problem first occurred I reviewed bug #767468 and purged both
cgmanager and sytemd-shim, but the problem remained. And, of course,
/proc shows systemd-machined (and only systemd-machined) still "thought"
/nfs/home was mounted.
Why is systemd-machined running? Do you have any systemd-nspawn
containers running where /home is symlinked or bind-mounted?
I have no idea - it was installed as part of the systemd package, and
starts automatically at boot. The machine runs a single KVM instance
hosting Windows 7, managed by libvirtd.
If you stop systemd-machined, is the problem gone?
That seems to fix it without any obvious drawbacks, but I assume I'd
have to do the same after each reboot.
Is machined started by libvirtd then? What if you systemctl disable
libvirtd.service, does systemd-machined.service still start?
Can you reproduce the problem with stretch, i.e. with systemd v232?
--
*email:* j...@huiac.com
"The greatest shortcoming of the human race
is our inability to understand
the exponential function."
- Albert Allen Bartlett
*web:* http://www.huiac.com/
*mob:* +61 407 391 169
*phone:* +61 8 7127 6275
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
