It is in Debian backports. I tried it a while back but the web interface felt a lot like cockpit and the command line didn't seem to have any advantages over virsh.
I've not used virsh, but have used cockpit on baremetal, didn't find it to bad.
Upto now, I've mainly concentrated on docker, which I do like, for it's ease of use. I see incus is starting to allow some docker things going forward.
I've also seen Truenas is going to use Incus (doesn't mean I think what Truenas does, then so should OMV) for me OMV is a lot better than Truenas, as I don't use ZFS, and a lot cleaner looking, it also works with my little JBOD system.
For me being a homelab person, I like to try new stuff out and thought if someone else has given Incus a go, then I could save myself some work, if it didn't work or needed a work around for it to function correctly.
While I am curious why the kvm plugin is hard to "read" or exactly what makes lxconsole easier to read, lxconsole isn't confined to the constraints of the OMV web interface. lxconsole seems to have advantages when using a cluster. Otherwise, I just see a lot of unneeded info if you are using a single node.
It's a me thing regarding the use of the plugin, I've not done loads of vm or lxc. The last lxc I did, I wanted to increase disk space, couldn't see how to do it, where I know you can from incus.
Regarding lxconsole, it just looked to me, easier to navigate, plus of course there seems to be more tutorials for Incus and lxconsole than OMV, but I can generally get my round OMV.
Canonical doesn't control lxc. They control lxd. Since the plugin isn't using lxd at all, I don't see how Ubuntu control is a problem.
My bad, I was under the impression lxc was a newer or subset of lxd.
The kvm plugin works with virsh, the plugin itself, cockpit, virt-manger, or any other tool that supports libvirt.
Perhaps I'll spend some time looking at the above as well. Always nice to see whats out there.
Why? I bounce from omv kmv plugin to virsh to virt-manger to VMware to proxmox all day long and don't have issues with any of them. I try to make the plugin easy to use from my experience with those systems. I'm curious where I went wrong or somehow came up a system that is unusable enough to make people use a completely new system.
Like I said earlier, I'm a simple homelab person, who see's something and thinks I'll learn that, and give it a go, sometimes it clicks straight away, others not. If there is more than one way of doing something, then to me thats good.
The plugin is excellent, the same as the docker plugin is as well, but I also like Dockge for docker as well, and would of liked to jump between the 2, but I can't, so I've stuck with your compose plugin because it does all I want and more, but if the plugin used 'compose.yml' for the compose file, I could use either, but I'm grateful that OMV has some brilliant tools and maintainers.
I haven't written any code since I ran a BBS, so I get it, when someone couldn't always see the software as I saw it, especially as I used to hate writing documentation. Which is why I like forums and try and help where I can.
Obviously, it doesn't look as though anyone is interested in Incus, so I'll spin up some OMV vms and see how it goes.