{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreickjtag75oyj5pvbxoainnnwwrwnulakcl6sydf2bnahrxn33dd2a",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mhzf6vclxqx2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifeafinzt2h7t4njeaefi6mgwfr346jofefusn44dsgev733sw3p4"
    },
    "mimeType": "image/png",
    "size": 528401
  },
  "path": "/post/47841837",
  "publishedAt": "2026-03-26T23:55:47.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Linux",
    "cm0002",
    "5 comments",
    "@user224@lemmy.sdf.org"
  ],
  "textContent": "submitted by cm0002 to linux\n22 points | 5 comments\n\n\n> Proxmox is a virtualization platform based on Debian. It’s not supposed to have a GUI, the management is either done via web UI or SSH.\n>\n> But since it basically is just Debian with some more stuff, I installed Plasma on top of it.\n>\n> It is also not supposed to use WiFi since that won’t work with Linux bridges. But, after removing the adapter from `/etc/network/interfaces` (which gets automatically added any time I make a change through PVE web UI) and rebooting, I was able to make use of the adapter inside Plasma. And also create a bridge on proxmox, add IP to it, enable IP routing, and NAT everything coming from that subnet (used for VMs) through the WiFi adapter.\n>\n> I just wish the noVNC could dynamically resize VM display like with VirtualBox after installing guest additions.\n>\n> There is no use case. It can be done, that’s it. I also tried to install Proxmox on my phone under Limbo PC emulator (QEMU-based), but I couldn’t avoid random kernel panics during installation.\n>\n> Also, Proxmox with 10GiB of available RAM (8+4, 2 for GPU), where the host uses up 3GiB is not really ideal. And on a weak dual-core CPU, on top of that.\n>\n> Edit: But now I got an idea.\n>  Now, there are issues. The simple solution will create multiple SSH connections that will never leave the laptop - that is - useless encryption, aside from other likely issues. The main thing is extremely easy set-up.\n>  OK.\n>  Thing 0: Exchange and authorize SSH keys between host and VMs.\n>  Thing 1: Create another ext4 or whatever volume on LVM, and mount it on host (probably better to have VM with large disk - why should every VM have SSH access to host). This will be used for file sharing.\n>  Thing 2: Mount it on all desired VMs using SSHFS.\n>  Thing 3: Install waypipe (like ssh -X, but for Wayland) to VMs and host.\n>  Thing 4: Create shortcuts on host desktop for desired GUI applications (which will run on VMs), prefixed by waypipe command. E.g.: `waypipe -c none ssh user@debian-main.home.arpa firefox`.\n>\n> Waypipe works with vsock as well, which might be useful in this situation, but I have no idea how that’s used, and if it is relevant here. Based on the man page, it does sound like it though.\n>  But anyway, mostly just a concept.\n\nOC by @user224@lemmy.sdf.org",
  "title": "Cursed setup - Proxmox VE on a laptop, with KDE Plasma on top of it."
}