I just use KVM under linux.
this post was submitted on 09 Apr 2026
17 points (90.5% liked)
Selfhosted
58397 readers
1195 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Can't you somehow convert the virtual harddisks of your VMs from vhd or whatever it is to qcow2 and start them on the new hypervisor? I mean that's pretty much the abstraction, virtualization is made for. I've never done it for Windows, though. I believe the "qemu-img" package has tools to convert disk images. It'll obviously need quite some temporary storage. And the VM configs / networking to be recreated on Proxmox.
This is great and exactly what I was looking for. Thank you.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HA | Home Assistant automation software |
| ~ | High Availability |
| LXC | Linux Containers |
| NAS | Network-Attached Storage |
| SSD | Solid State Drive mass storage |
4 acronyms in this thread; the most compressed thread commented on today has 17 acronyms.
[Thread #228 for this comm, first seen 10th Apr 2026, 01:30] [FAQ] [Full list] [Contact] [Source code]
Edit: Also yeah you should be able to dual-boot but I wouldn't recommend it. Linux and Windows bootloaders don't like to play nice with eachother.
2nd Edit: Added the official PVE Hyper-V migration documentation, but that blog covers it in more detail.
3rd Edit: It looks like there are some important caveats when virtualizing TrueNAS, which I assume you're familiar with since you have it virtualized already but I wanted to add the TrueNAS virtualization guide just in case. https://www.truenas.com/blog/yes-you-can-virtualize-freenas/
You should be able to migrate most or all of your existing Hyper-V VMs to Proxmox, which would be relatively straight forward. My recommendation would be backing up everything to your TrueNAS (that has the dedicated HBA) then you can wipe your Windows boot drive and install Proxmox. Then you could start by migrating your TrueNAS VM over and passing it's HBA back to it.
Once you have your NAS working in PVE then you could either migrate/rebuild your other VMs, or look into splitting your services into containers (Proxmox uses LXC natively, but Docker is another option.) There are some great helper scripts to get services spun up quickly so you can minimize downtime.
You didn't mention how much, if any, experience you have with PVE/Debian and I know from a friend recently switching that some things are a bit more "difficult" than TrueNAS so hit me up if you need anything. The PVE admin documents will be helpful as well.
https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#HyperV
You should be able to migrate most or all of your existing Hyper-V VMs to Proxmox, which would be relatively straight forward. My recommendation would be backing up everything to your TrueNAS (that has the dedicated HBA) then you can wipe your Windows boot drive and install Proxmox. Then you could start by migrating your TrueNAS VM over and passing it's HBA back to it.
Yeah I thought about this being the easiest way to do it. I just wasn't sure if TrueNAS would come back up and just recognize the disks and start working. I have backups of everything and I've tested restoral. I would prefer to not have to go the backup restoral route as it's more a scorched earth option. My other VMs I'm not really concerned about, it was mainly the NAS.
I don't really have any experience with PVE, but I want to learn. I've been learning about docker containers more recently, I like learning new tech so I'm all for it. My main PC has been running Linux for about 6 months now and I'm just trying to get away from Microsoft in general. Thanks for the info.
I haven't used TrueNAS but from what I'm reading it has an option to import existing pools. If you have spare SSD I would yank your windows drive out of the system and try installing Proxmox on the spare drive first. There's a truenas installation script on that community page I linked in my other post, it says to follow this discussion after it runs. That might be a good starting point.
God, I'm sorry you had to use Hyper-V.
As challenging as Proxmox is for someone new to it, it's so much better than Hyper-V.
I have a 3-node Proxmox cluster with HA that is currently collecting dust because I overbuilt when rent was cheap and now I can’t afford to run it; so I’m running essential services on my desktop PC with Hyper-V and NONE OF THE NETWORKING MAKES ANY GODDAMN SENSE oh my god why can’t I get WSL2 and a VM to see the fucking LAN at the same time they don’t need to talk to each other I just need HomeAssistsnt and paperless to work from LAN devices why is this all so shit