Post #1617593

2026-03-10 14:26 UTC

If you&#39;re trying to run Remnux on KVM by loading the OVA: To get network access: KVM changes the network adapter name, so you&#39;ve got to change the config in /etc/netplan, replacing the old vmware adapter (like enss0) with whatever the new one is and then reboot. You can use networkctl to find the non-loopback adapter name (like en1ps0) The Remnux docs also say to run &quot;remnux install&quot; after loading into KVM to install spice and other tools. When I do that, it makes the VM worse: cursor disappears, resolution gets jacked. Instead, installing spice-vdagent using apt gets you all the nice stuff like dynamic resolution and copy-paste. Afterwards, if you try to use remnux-install, it will again break the vm tools inside the VM. I&#39;m unsure the cause.

Replies (1)

@mayahustle@infosec.exchange 2026-03-10 14:44

Separate but related, when did VMware and Virtual Box get so terrible on Linux? I used to use them all the time, but with secure boot, installing either of them is not so straightforward. I gave up on VMWare after a few hours of trying to figure out the which combination of software version, user-provided patches, and kernel version to install. I realized later that I had forgotten to sign keys for secure boot. You'd think the installer would at least give you a warning. Virtual Box on the other hand, told me I had to sign its kernel modules, had me go through the process, and then failed to install. (via apt). Downloading the deb appeared to fix it, but the actual VM experience wasn't great. KVM on the other hand, installs (optionally) with the Kubuntu installer, and worked fine out the box.

Open ##2313471