What distro and version of that distro are you using? Did you install gpg from the repository or elsewhere? What version of gpg are you running?

The OOM killer is particularly bad with ZFS since the kernel doesn’t by default (at least on Ubuntu 22.04 and Debian 12 where I use it) see the ZFS as cache and so thinks its out of memory when really ZFS just needs to free up some of its cache, which happens after the OOM killer has already killed my most important VM. So I’m left running swap to avoid the OOM killer going around causing chaos.

I think that also causes issues for roaming profiles and folder redirection. If roaming is turned on then everything in the %appdata%\roaming folder is synced to a server. %AppData%\Local is not. So if your app is using %AppData%\Roaming for temporary data then you are causing a whole bunch on unnecessary IO. Same for using Documents since that if often synced.

Can you run a live CD on the machine? You mentioned Memtest but I’m wondering if an Ubuntu one would work.

Absolutely!

Steam hardware survey but that will skew towards gamers. That said, it would be a good indicator on how compatible Wayland is.

I kinda get it. The host has complete access to VM memory and can manipulate it without detection. Both of those games are free to play as well so cheating is more of an issue. I have no idea what Back4Blood’s justification would be though.

That said it’s a PITA and given the massive attack surface of Easy Anti Cheat it becomes easier to justify running in VMs where you can isolate things and use snapshots if there is ever a breach.

It’s a gaming machine. I mainly use a gaming VM with GPU passthrough under Proxmox, but the anti-cheat is some games (Fortnite and The Finals) don’t allow you to run them in VMs. So I run those games in Windows directly under a standard user account as a compromise.

UEFI or legacy BIOS? I recently installed Windows 11 on a machine with Proxmox on NVME but installed Windows on a SATA SSD. Windows added its boot entry to the NVME SSD but did not get rid of the Proxmox boot entry.

I’ve definitely had the same issue as you on in the past on legacy BIOS and when I worked in a computer shop 2014-2015 we always removed any extra drives before installing Windows to avoid this issue (not like the other drives had an OS anyway).

Wait… so the author displayed in “by <author>” is the supposed author of the software, not the one that put it on the store? That’s insane! Also sounds like you’d be open to massive liability since the reputation of the software author will be damaged if somebody publishes malware under their name.

It should be:

• Developed by: <author of software>
• Uploaded by: <entity who uploaded to store>

Seconding the RAM issue possibility. If you can, shut down the host and run a memory test over a few days to see if it trips. Memory tests can take days to trip in some circumstances, in others, it’s immediate.

Truly, the year of the Linux desktop!

morethanfftnchars

To be fair, you can probably find it on Archive.org. Would be kinda neat if somebody made MaymayOS that just had theme packs for the other meme distros to keep them alive.

Other comments have hit this, but one reason is simply to be an extra layer. You won’t always know what software is listening for connections. There are obvious ones like web servers, but less obvious ones like Skype. By rejecting all incoming traffic by default and only allowing things explicitly, you avoid the scenario where you leave something listening by accident.

Another option may be to use Windows Server 2022 Eval. You may run in to problems with software refusing to run on a server though. The initial eval lasts 180 days, but you can run a command to extend that 5 times (don’t quote me on the exact number) which will give you an updated system for years to come.

It is a checkbox in Rufus. Ventoy will also do this for you.

Can’t even get the ISO anymore. 😭

Sounds like you just volunteered to post Linux news and related content!

Are you running QEMU directly, or through libvirt (GNOME Boxes, Virt Manager)?

EDIT: NVM I see you’ve answered that in another comment. I believe you can’t do this with QEMU directly. If you don’t need to be able to edit the VM config besides core count, disk size and RAM use GNOME Boxes. Otherwise use Virt Manager.