nd interface MAC doesn't match either of
those two, the network traffic is blocked. This is a common practice for
many cloud providers.
This issue has caused me plenty of headaches until I realized the switch
was eating my traffic coming from an unknown MAC.
--
Major Hayden
nds, systemd-machined stays up indefinitely.
I'll also take a look at Zbigniew's suggestion in the thread about disabling
watchdog for systemd-machined temporarily.
—
Major Hayden
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
keep systemd-machined running indefinitely and avoid any cgroup
trimming of active virtual machines:
while true; do machinectl; sleep 10; done
Should systemd-machined remain running whenever a VM or container is running?
--
Major Hayden
On Nov 4, 2014, at 08:38, Major Hayden wrote:
> I
ved.
Rebooting the hypervisor, rebooting a virtual machine, or building a new
virtual machine will cause systemd-machined to start again but it will stop
shortly afterwards.
I'm running libvirt 1.2.9 and systemd 216 on Linux 3.16.7. Thanks in advance
for yo
