I normally update to the latest version to profit from improvements. So I did a couple of weeks ago to 25.04.0 Since all my VM’s where gone I switched back instantly.
Today I could not resist to give it a retry using 25.0.4.1 So I spend an hour trying to migrate and start an existing VM.
I tried to understand the GUI which seems to be build with quite different things in mind than a classical VM !!
Containers, mac vlans default IP range things I do not like. I just want to choose a ZVOL and ISO and a bridge towards the vlan of my choose
What ever the simple thing I tried to archive, is nothing more than to start my existing VM/zvol by selecting that zvol, assign cpu and NIC and GO!
What ever I did not manage and again switched back to 24.x
Hoping for a TrueNas version with decent and not experimental VM support
Did you actually select VM (second option) instead of container?
VM (of course) my impression is that the whole new interfaces is build with containers in mind not VM’s
If you select VM you can:
Choose an existing zVOL (select import on the volume overview that opens)
I did select zvol but all kind of things there which are strange IMHO
all kind of conversions where I just want to use an unmodified zvol containg the VM-disk; I did choose to clone, since I absolutely did not trust what was going to happen;
I also tried to create a new VM but the logical option to select an ISO present on the system seems not there!
Set Memory and CPU limits
that was about the only ‘clear’ thing
There is a question related to root size. No idea what it is.
There is also the size of the zvol of course
And there is no option to select a second zvol
(which I sometime use as second or larger storage (on a HD))
Set the BUS type (NVMe, SCSi, etc.) size has no effect on existing zVOLs, I like setting it to the right value anyways
my vm’s are located on an NVME-drive so I did select VME
Use the default network setting or select a bridge interface (you obviously need to create the bridge interface for the corresponding VLAN first)
I have that of course and did select that
all kind of network ranges and mac bridges and vlans which I absolutely not like to use
I did choose the original bridge. The VM does have Its own IP’s
Choose passthrough devices (or not, leaving that section empty)
not applicable
Choose if VNC should be exposed
I did activate that, however note that the address is inside the GreenZone (truenas address ranges) Where I would like to see it in the choosen address range.
despite opening the firewall in favor of VNC I could not access the VM using VNC
The VM starts, but was not accessable on its address and not via VNC, I could access it via TrueNas using the console. From there I could see:
that it was running
and not having an IP address
After some further tries changing options, I was completey done with it and did boot the previous version (using the very worth-full boot selector) . Luckily enough TrueNas did run that version without problems and the VM was not damaged.
It is probably me but I find the GUI confusing. The old not Ideal, but much easier to understand what you are doing
Before I did create this VM I did create the ZVOL’s. During installation I used a debian image as available in a ISO-directory in a truenas dataset. I could start the VM from a virtual CD, removed after install
It is possible to upload the OS installation ISO, and use that for the VM creation – on the Instances screen there’s a “configutation” button, which opens a menu, which includes “manage volumes” item, which, when clicked, opens a popup with list of volumes, which has “Upload ISO” button. This actually worked for me – I was able to upload an ISO, make a VM and install Windows, and it does show up on the network (granted, I didn’t do any VLAN-ning, just gave the VM a MAC-VLAN interface and it was able to talk to the DHCP server). Also VNC worked, but again, it’s exposed on the TN’s main IP.
I am glad I did choose clone before since I do not want my real VM to be damaged.
Note that the shown data structure is NOT visible in the GUI when using 25.04.1, what I do not like.
Given the automatic data structure, I also start to understand why you can only use one dataset. Given the fact that my NVME-storage is limited, I am not happy with that.
I will normally run a VM on a NVME-drive, however if it need lots of storage, the extra storage will be on my Harddisk Raid (mostly that is not necessary). I can hardly expant NAME-capacity since the very limited number of PCIE-lanes on consumer systems (next to the still high NVME prices).
I did reinstall 25.04.1 to be able to check reactions in this forum.
Here my default settings, where again multiple questions pop up:
I did not remove the hidden data structure what is happening now
you can enable ^storage^ however what if you do not enable storage !!??
what does bridge automatic / bridge selection do!!?? I normally select a bridge on a per VM base! Bridges are in my case if not always related to a certain vlan, and my VM’s always belong to a certain network security domain = vlan
