A recap of KVM Forum 2019
A recap of KVM Forum 2019
Posted Nov 21, 2019 2:21 UTC (Thu) by bergwolf (guest, #55931)Parent article: A recap of KVM Forum 2019
> In "Bring QEMU to Micro Service World", Xiao Guangrong and Zhang Yulei described how they used QEMU to launch micro-services extremely quickly. Their solution, called QEMU basepoint, bypasses QEMU and guest initialization. Using the existing QEMU migration feature, it saves the state of the VM into a template file just after it starts. Then it uses this basepoint to launch new VMs. To save QEMU initialization time as well, the new VMs are handled by a fork of the base QEMU process. This solution allows them to reduce the boot time, but it still has limitations, such as the lack of kernel address-space layout randomization, that will be addressed in the future.
The exact same feature has been around for years in hyperhq's [runv](https://github.com/hyperhq/runv) and kata-containers(https://github.com/kata-containers/runtime). But I wonder how KASLR can be solved because re-randomization seems difficult and breaks the fundamental memory sharing idea of vm templates.
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.
