A lot of people dont know how this stuff works. Thats why I keep seeing things like “Truenas is replacing KVM” or “Truenas is replacing QEMU” which is all wrong.
Truenas is actually replacing libvirt with Incus.
Simple hierarchy of how VMs worked before and will work in Fangtooth:
VM before: TrueNAS → libvirt → QEMU → KVM
VM after: TrueNAS → Incus → QEMU → KVM
I’m not trying to be quarrelsome either. I agreed with you in fact that the UI needs to expose some of this stuff and encouraged you to submit a request to get it done. I said it was a good idea. I call that agreeing with you.
Still, re-read what I said, I said Truenas does not have doc on the underlying sysems, that is left to the underlying system. The doc for moving VMs is all over the internet as an example, thousands of guides, explanations, etc.
Some examples. Want to get you an image of some format? See:
https://docs.openstack.org/image-guide/convert-images.html
Not enough details? man qemu-img, there’s the doc, on Truenas even.
I don’t think Truenas can possibly doc everything every underlying system does. I suppose they could do a link as you noted. Then again, they don’t want you to use all those features as some stuff, like installing more software, requires you to break support. What it can/should do is expose more stuff in the UI since that’s the purpose of Truenas. Not CLI. I think the end goal is not to need to use CLI at all. I’d rather more time be devoted to that.
