The driver is merged into the base repository, where most Redox drivers and system components live. The kernel, bootloader and driver changes that let Redox boot to a shell on Cloud Hypervisor are merged too (details below). Both are fun pieces of work on their own, but they are really the first steps of a bigger effort with two directions: The guest work is generously funded by NGI Zero Commons and NLnet as part of the Virtualized Redox grant.
Most Internet-facing software today runs in virtual machines, either in the cloud or on edge servers close to its users. The easiest way I know to think about a hypervisor is as an operating system whose processes are operating systems. A process runs directly on the CPU until it needs the kernel, for a system call, a page fault or a timer tick, and then the kernel takes over for a moment.
