124

Hypervisor in 1k Lines

This is a cool intro to how virtualization instructions work, but people need to understand that it is not revolutionary simplicity or anything like that. It's just a a cool tech demo lacking all the important bits of a modern hypervisor required to make it practical, like paravirtualized drivers for example.

Same when someone claims to have written an OS in 1000 lines and all it does is get you to real mode with VGA graphics and an interactive (but useless) prompt.

(Note that you can benefit from virtualization technology in specialized scenarios outside common hypervisors, but that's not really what's being demoed here.)

3 days agoarghwhat

Any thoughts on OsakaOS

2 days agoge96

That it's fine to do things just to have fun an mess around, but thats all there is to it. It's not even an OS at the current state.

Other small OS's are actually OS's and can be impressive efforts. Sometimes they bring new concepts or paradigms, but that itself is rarely more than a curiosity without impact. Still fun though, at the very least for the authors.

2 days agoarghwhat

Hm I would like to see this in C rather than Rust. And I wonder if you can run the 1000 line OS in C along with the 1000 line hypervisor

It would be nice to see a demo!

3 days agochubot

How do you define an OS? You can write an EFI "OS" that prints "Hello, world" in approximately 5 lines.

3 days agoLiamPowell

It's a bit more than that.

> We'll implement basic context switching, paging, user mode, a command-line shell, a disk device driver, and file read/write operations in C.

see https://1000os.seiya.me/en/

3 days agospongebobism

that's not an OS, that's an EFI application

2 days agodark-star

Why does it need qemu? Isn't it a qemu?

3 days agogiveita

I guess because it's a risc-v hypervisor and the author expects you to run it on an x86 machine.

2 days agoahakki

Thanks. Good use of a turtle. (Turtles all the way down)

2 days agogiveita

[dead]

3 days agocurtisszmania

[dead]