this post was submitted on 06 Aug 2026
33 points (97.1% liked)
Linux
14583 readers
245 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Power saving with encryption at rest. I want the GPUs offline power wise.
Just spitballing here, but if you use a VM with gpu passthrough, the host system doesn't even see the GPU anymore, so if the VM is off I imagine the GPU is basically off as well. In terms of encryption at rest, you can probably make a separate LUKS volume for the VM disk image, and then lock it when the VM is off.
Edit: for example I have a VM with GPU passthrough and when the VM is off, I have no way to check the power consumption of the GPU (aside fom using external hardware) since the host doesn't have access. The host uses a sort of dummy driver for the GPU, so that the hypervisor can pass it on to the VM, so it is actually possible for the host to switch the driver and take control of the GPU when the VM is off. But until then I imagine power consumption is minimal.
I used to do this for my virtual gaming rig, and the catch is still idle draw. Just one B70 pulls over 30W idle, then there's the nvidia card and then CPU etc, too. As this machine is solely for remote development and inference, I want it fully off.
Now, I guess I do have all the confidential stuff in encrypted ZFS, so I can shutdown the docker containers, unmount ZFS, and suspend. This gives me encryption at rest. The problem is the startup/resume is actually slower than you might think.