Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
devc1 wrote:what does this have with "hypervisor security"
It just means you're doing something that you're not supposed to be able to do. Code running inside QEMU is not supposed to be able to crash QEMU. If it does, that's bypassing the security. Bypassing security is not always very interesting.
devc1 wrote:And can u answer the question in the last forum "High performance graphics for all GPUS.."
You already got an answer to your last question in that thread.
You're the exact opposite of me, my OS target is modernity and maybe fix the (All OS'es sucks), in each thing I wanted to change I will need to change the whole API (I had no big C/C++ experience before starting but I had experience in other things). Now after recreating the Scheduler, I am recreating an optimized memory manager with page fragmentation and Page File. I will need to work on some drivers and after that I wan't to design an ultimate fancy UI to match or (better) the Windows 11 UI.
Who knows, maybe my OS will not be considered from suckers ::)
I do not like reading manuals, I am a teenager and I got things to do !
Octocontrabass wrote:I mean simpler things, like crashing QEMU or making your disk image grow bigger than 32MB. Probably nothing as exciting as you're imagining.
I used to always crash QEMU when I was creating the USB EHCI driver IIRC. Any driver who is ruining the devices could crash it !
No, I really remember that QEMU used to crash on something when I was creating the driver. I have restart and shutdown disabled on QEMU, it just says "Window Not responding..." and then it crashes. Try to mess up with some devices and it will crash.
