{"id":23920,"date":"2022-12-16T03:54:52","date_gmt":"2022-12-16T03:54:52","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/16\/xen-project-goes-for-vm-hyperlaunch-with-version-4-17-the-register\/"},"modified":"2022-12-16T03:54:52","modified_gmt":"2022-12-16T03:54:52","slug":"xen-project-goes-for-vm-hyperlaunch-with-version-4-17-the-register","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/16\/xen-project-goes-for-vm-hyperlaunch-with-version-4-17-the-register\/","title":{"rendered":"Xen project goes for VM Hyperlaunch with version 4.17 \u2022 The Register"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Version 4.17 of the Xen project’s eponymous hypervisor has debuted, bringing with it the first look at Hyperlaunch capabilities that allow the creation of multipole VMs on startup.<\/p>\n

When Xen goes to work today, it creates Dom0<\/a> \u2013 a privileged domain that has to run before the DomU unprivileged domains that contain virtual machines can get to work.<\/p>\n

In 2018, Xen developers started work to change that \u2013 in part because Dom0 takes a while to get going on small devices, leading some developers to look at alternative hypervisors. Makers of small devices like virtualization because the isolation it affords improves the security of their machines.<\/p>\n

\n