I backed up my 3 VMs, running on EE (KVM hypervisor) and wanted to give Fangtooth a try. The thought was to spin up 3 new VMs and restore the backup info to the new VMs. So far I’ve been unsuccessful, but surely because it’s brand new and I’m doing something wrong.
Are there pointed instructions to spin up a new VM, under Fangtooth? I got stuck around finding the location of my iso files on my machine, and being stumped with the choice of source and destination volumes – not sure what that means.
Also important, what is meant by the language “experimental” for VMs? Has a decision been made to stick with the current Incus implementation for VMs? If not, how will VMs be supported going forward?
As the docs say: A community feature. “Support” means paid Enterprise support, that comes in a future version of TrueNAS.
But as hobbyists we have “community support” anyway, meaning best effort through the forums, not formal support by ix.
Which means that while the virtualization features are a bit in flux, to determine how best to structure them so they can become an Enterprise feature, they are certainly also community-supported in the meanwhile like any other feature.
Try the stuff, give feedback through the little bell, report bugs.
Correct. It means the feature is brand new, under a lot of improvements and slippery when wet. It also means we’ve not done our normal rounds of SQA work to make it up to “Enterprise standards” yet, and it needs some more soak time released to the community first to help us find rough edges to fix for the release of 25.10 this fall.
Incus by default uses UEFI firmware ( OVMF) but can be set to use non-UEFI (eg. SeaBIOS) with some tweaking involved. But I cant speak if iX plans to support that.
Never have logged a defect/bug and not sure this qualifies. I was able to upload the iso file, but the installer complained and did not spin up the VM because the length of the file name, which I’ve never changed since I got the iso from MS, was too long:
Also, like a lot of folks I run my VMs headless. Under the KVM way, one could log in to a Windows VM and set up networking to get Remote Desktop working, then not have to bother with VNC, or the Java display GUI. And Remote Desktop is mature and very robust. I don’t see how users can perform this now. Worst yet, it looks like networking isn’t mapping to the hosts Ethernet resources to even get over to the machine VIA Remote Desktop.
I presume you talk about virtio ISO?
You need workaround so the installer is able to see it.
In short, Incus uses virtio devices. Windows doesnt have virtio drivers. To be able to mount virtio ISO you need method that use device that Windows installer understands. In this guide its IDE device.
Or use distrobuilder to have Windows ISO with already baked-in virtio drivers.
Uhm… i am not getting something here ?
Setting up a windows VM now requires 18 additional Steps ??? (According to that forum link ) or messing with the ISO-file to get the virtio drivers installed ?
This sounds very bad…
Keep in mind, this is a BETA. Work already landing in the RC1 next month which will let you install Win11 without needing the VIrtio driver. (I.E. the stock ISO will work again)
Think perhaps I’ll wait until RC1. The VMs that were taken out by moving from EE to FT were not production VMs with important workloads anyway. The important VMs are running on my Mac, and will not move until the FT cake is fully baked.
But did I read that Incus can take VMWare virt disk and use it?
