hypervisor VS circle

So I'm working on making a hypervisor for my school. I've looked into the vendors like Proxmox, Vmware, etc. and I haven't found one that will let me make my own GUI. I have looked at pages like this https://rayanfam.com/topics/hypervisor-from-scratch-part-1/ or projects like Bareflank here https://github.com/Bareflank/hypervisor and they don't QUITE seem like what I am looking for, unless I'm just blind. I just want to have a hypervisor that can spin up oh so many virtual machine instances of Windows 10 and accessible in a browser. I want to have the freedom to make my own GUI so I can tailor it to my school's website. The idea is it's just something freshman can screw around with and have the option of spinning up a few VM instances as they please, while keeping in mind a very simple GUI a freshman could figure out. I'm not too concerned with hardware limitations, I just want to see if this is even possible, and if I have to deal with crap hardware/software that can only spin up 2 instances or something, so be it. I understand that I very well may be looking for a unicorn in that I will have to either use a vendor and accept their GUI or go through a monolith of assembly code to build my own, but if anyone has any suggestions or github links to help me do this in a reasonable amount of time it would be much appreciated.

If you're a developer and feeling adventurous, you can also try building it yourself. The source is all on GitHub. It uses the circle-stdlib project (which is circle plus some additions to support much of the C and C++ standard libraries) as a submodule; hopefully I've set that up correctly, but you could always clone that separately and place it in the MiniScript-Pi folder. Check out circle's build instructions for info on setting up your toolchain. (Mac users: be careful with the configure script, which does not work properly on MacOS; find me on Discord and I'll help you fix the script or configure manually.)

I suggest checking out circle https://github.com/rsta2/circle since it's basically a library for the pi hardware. I'm doing some experiments with it myself now.

You can also run a Pi without an operating system, programming it in C or C++ probably. See for example: GitHub - rsta2/circle: A C++ bare metal environment for Raspberry Pi with USB (32 and 64 bit)

BMC64 is VICE in a trenchcoat unikernel / bare-metal framework called Circle: https://github.com/rsta2/circle

It uses the circle library (https://github.com/rsta2/circle) to provide a minimal runtime (mainly to interface with the hardware).

I experimented with circle the other day (https://github.com/rsta2/circle) Looks promising, and most likely within your knowledge of C/C++ development.

Natively would be amazing but a vast amount of work.

The way Apple moved classic MacOS from 680x0 to PowerPC was to write a tiny kernel emulator, with an API to run native stuff on the metal, and run more or less the whole OS under emulation, profile it and just translate the most speed-critical bits.

That's a lot of work for a FOSS project but given the performance delta between 1980s 680x0 and 2020s ARM, total emulation of the whole thing should be perfectly fine. It's how the PiStorm Amiga upgrade works.

https://amigastore.eu/853-pistorm.html

So all I envision is something like Aranym:

https://aranym.github.io/

... running on top of Ultibo, say:

https://ultibo.org/

Or maybe Circle:

https://github.com/rsta2/circle

Circle is a C++ bare metal programming environment for the Raspberry Pi.

The only other reasonable option would be to port it to a new platform which is popular that has a few well documented hardware interfaces so as not to create a hellish nightmare writing drivers. Maybe then you could do a one-off port to that platform (though you might have to re-target the HolyC compiler to target it instead if it is not x86_64). The Raspberry PI seems like a decent option here since there is already a baremetal C++ library supporting USB, keyboard, mouse, sound, video, and as an added bonus UART, I2C, SPI, GPIO. You would have good code examples for porting all the necessary drivers. But obviously this would still be a lot of work and the compiler would need to be re-targeted and user space adapted for running on ARM. That being said backwards compatibility is strong, ARM seems actually interested in keeping it that way (at least for now). The library I'm talking about is here: https://github.com/rsta2/circle