Weekend is here and so are my hypervisor updates.
Was pretty occupied the entire week but managed to debug my `Invalid OpCode` issue with KVM.
Root cause? - I wasn't loading all of the segments of the ELF properly 🤦♂️.
Now finally kernel is loading properly and has a simple serial driver.
Off to the real work now, a hypervisor, deterministic hypervisor!
Not much of an update today. Spent almost the entire day debugging "KVM internal error". Happens only if I call `panic!` in my Kernel (not in bootloader).
The paging is set, stack is set, ELF sections are loaded properly. Will continue debugging this week.
And my bootloader can finally load my kernel! That completes step 1 of many other steps in my attempt create a hypervisor!
Bootloader can now properly parse the EFI_SYSTEM_TABLE and can extract RSDP related data to pass onto the kernel.
It might have been a mistake to write all the parsers on my own but it forces me to carefully go through both ACPI as well as UEFI specs (for copy-pasta).
1
6
677
After a busy week, finally started working on the hypervisor!
The goal is to have a simple bootloader + kernel (capable of creating simple VMs) up and running by the end of this weekend.
This weekend's read was "DiffKV". It was kinda dense read as it is an amalgamation of quite a few ideas:
- Inline KVs for small sized vals.
- Separate KVs to a vTree (LSM like structure) for mid sized vals.
- Separate KVs to a vLog (ref: WiscKey) for large vals.
- Use "hotness aware" vLog.
- Reduce GC overhead by running them "lazily"
- Several other optimizations!
I really liked the paper for the various ideas it shared but I think it definitely is more complex for my needs right now :).
I am reviewing the literature around LSM based storages as I am planning to write a toy etcd compatible DB.
Today's read was "WiscKey". The basic ideas of the paper are:
- Store values in a separate vLog file to reduce amplifications.
- Replace regular log file with vLog file.
- To reduce the cost of randomized IO on the vLog file use prefetching (exploit SSD parallelism).
I am not sure how GC on vLog will affect performance when the system is under high write workload. My concern is not the algorithms or locks but GC saturating the Disk bandwidth.
And my copy of “Hacker’s delight” is finally here!
Thanks to #1BRC!
Yesterday I decided to give @zeddotdev a shot and saw "CRDT" (on their site) which piqued my interest in them again.
"A Gentle Introduction to CRDTs" was a fun little read!
I am considering to read a few foundation papers on CRDTs as they are still a huge black box for me.











