I am trying to install and setup proxmox on laptop and use it as daily driver. I want to make network setup that can use both ethernet and WiFi, whichever is available and i want VMs to be able to access LAN because some things dont work otherwise (like NDI). I have writen config file that makes 2 bridges and every VM would have 2 interfaces. I havent installed Proxmox yet because i dont want to mess things up (it wouldn’t be first time :) ). My question is does this config look ok and are there some recomendations.

/etc/network/interfaces

auto lo
iface lo inet loopback

# Ethernet interface
auto eth0
iface eth0 inet manual

# WiFi interface
auto wlan0
iface wlan0 inet manual

# Ethernet bridge
auto vmbr0
iface vmbr0 inet dhcp
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0

# WiFi bridge
auto vmbr1
iface vmbr1 inet dhcp
    bridge_ports wlan0
    bridge_stp off
    bridge_fd 0
  • scholar@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    When you say you want to use proxmox as your daily driver, what sort of things are you wanting to do with it? Are you going to be spending most of your time inside a WM, and want to be able to switch to a different VM? I’m struggling to see your use case.

    • RealBot@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      I would do everything in VMs, mostly Linux and probably one Windows. Proxmox would be only for managing VMs. I want everything in VMs because it’s more flexible for partitioning storage and i can have both Linux and Windows runing at the same time (which can’t be done with dualboot). I am student of computer science so i use it for programming, both for college and side projects. Sometimes there are a lot of programs i have so OS kind of gets bloated, not so much from performance standpoint but just mental overhead of having 10, 20, 30 programs and having to keep in mind what program needs what dependencies, env variables, etc… so i want to kind of group them to VMs and CTs.

      • scholar@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        4 months ago

        You’d probably be better off picking a normal distro and then running QEMU to run Windows or other VMs. Proxmox is more comparable to VMware ESXi in that it is designed for running server VMs and managed through a web ui.

        • RealBot@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          4 months ago

          I have thought about that, but Proxmox already has built-in a lot of things for virtualization and managing VMs and has less bloat because it has only one purpose.

      • exu@feditown.com
        link
        fedilink
        English
        arrow-up
        5
        ·
        4 months ago

        Have you thought about trying QubesOS instead, as it’s pretty much built for this purpose?

        • RealBot@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 months ago

          That’s interesting, haven’t considered that. Although I would want to run most things in CTs/LXCs and not full VMs for performance reasons. And Proxmox has more DIY feel which i kind of like. If I fail with Proxmox, might give QubesOS a try.

          • Findmysec@infosec.pub
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 months ago

            Qubes OS doesn’t have GPU acceleration using Virtio-powered interfaces if that’s something you need. Also it’s based on Xen and you are not encouraged to mess around with dom0.

            TBH if there’s a way that you can attach to the display output of a VM with a GUI when you start your computer, it will probably fit your use-case perfectly. I haven’t found a method to do this but I think there should be some way to attach directly to the display of a VM after booting up.