<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd on myvirtualcloud.net</title><link>https://myvirtualcloud.net/tags/systemd/</link><description>Recent content in Systemd on myvirtualcloud.net</description><generator>Hugo</generator><language>en-us</language><copyright>Andre Leibovici</copyright><lastBuildDate>Thu, 17 Sep 2026 09:00:00 +1200</lastBuildDate><atom:link href="https://myvirtualcloud.net/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>Why systemctl daemon-reload drops GPUs from running Kubernetes pods</title><link>https://myvirtualcloud.net/why-systemctl-daemon-reload-drops-gpus-from-running-kubernetes-pods/</link><pubDate>Thu, 17 Sep 2026 09:00:00 +1200</pubDate><guid>https://myvirtualcloud.net/why-systemctl-daemon-reload-drops-gpus-from-running-kubernetes-pods/</guid><description>&lt;p&gt;A &lt;code&gt;systemctl daemon-reload&lt;/code&gt; on a Kubernetes GPU node can detach the GPU from containers that are already running. The pod stays Running, nothing restarts, and no component reports a fault. The workload simply loses the ability to open the device. Almost every package that ships a systemd unit runs a reload on install, so agent rollouts, &lt;code&gt;apt-daily-upgrade&lt;/code&gt; and snapd refreshes all trigger it.&lt;/p&gt;</description></item></channel></rss>