Why do you call it a hypervisor when it's more like a VMM?

Even the name "VMM" is a quirk of KVM; before KVM, "virtual machine monitor" was another name for a hypervisor: that is, the thing that ran on the bare hardware and provided the virtual hardware interface to the VM. KVM has fairly unique architecture, where a VM is basically a process.

I'm willing to tolerate that "drift" of meaning, because we need a word for the piece of software which converts a process into a VM, and "VMM" is a good fit. But I'd have to really object to the idea of calling such a piece of software a "hypervisor".

If your plan is to make wiser into an actual hypervisor at some point, I'd appreciate it if you made that clear in your README.

@gwd you are correct vmm is a better fit. I'll update the repo thanks for the feedback :)

KVM isn't particularly unique in its process architecture. It is a classic "type 2 hypervisor", just as Wiser is.

I do prefer VMM as the term though.

it is*

Wow, nice work, great name

What's your roadmap?

Its something to think upon. As of now i don't have anything, just fix bugs and complete unfinished components maybe :).