I’m a Windows guy since forever and I recently got into selfhosting. So far its a blast! Are posts about that welcome here?

  • nevetsg@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 day ago

    My host OS is Windows Server 2022 because I Prefer it, HyperV works, Windows Backup works, and the drivers work. I then run a Linux VM for Docker and a few other VM’s for silly things. If I break a VM I can have it restored in a few clicks. I tried to use Proxmox as the host OS but it would kill itself every 6 months. It was a good learning experience but it would take a Lot of convincing to try it again.

    • early_riser@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      16 hours ago

      I’m gonna sound like everyone I complain about here, so feel free to ignore me. How did Proxmox break? I’ve been hosting a bunch of Proxmox containers on a 15 year old crappy laptop and it’s been smooth sailing for at least a year and a half.

      Not trying to shun you for using windows or discount your personal experience with Proxmox or anything, just genuinely curious. If you prefer windows, use it.

      • nevetsg@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 hours ago

        I can’t remember the actual errors. I was running it on an old DELL PC they I had added an extra drive to, I think it was an SSD I had lying about. Everything would be running fine with no errors, Linux and Windows VM’s. Then one day all services were offline. Being a PC I had to plug in a screen+KB/Mouse. The host OS would boot and then flood the screen with errors regarding unable to mount the storage. troubleshooting with Boot USB showed all of the virtual Partitions (the ones that the VM data sits in) had been corrupted. Maybe a Linux guru could have restored them but I was lost.
        I started over with a clean install of Proxmox, Maybe I had done something wrong the first time. I cant remember if I managed to restore the VM’s from backup. A few months later Bam, exact same thing happened again. I thought maybe my PC or drives had issues but decided to try Windows 2019 HyperV host instead. That ran for 2 years without issues on the same hardware.