Live updating operating systems using virtualization

Building truly potable applications in this manner takes care and attention, especially in the Windows world. I have built render farms with thousands of diskless nodes.These nodes pull an operating system image from a PXE server on boot, load the render application and its configuration from the central server, then set about rendering whatever's in the queue, spitting the finished data into a folder.Bare metal operating systems don't tend to do so well when you run them on radically different hardware. People who do Virtual Desktop Infrastructure (VDI) for a living can explain in detail the number of possible ways this can occur, and the many, many hurdles to making it happen.

live updating operating systems using virtualization-45

Solutions to this problem can be largely divided into two groups: persistent and non-persistent workloads.Proper non-persistent workloads are a huge investment of time and effort up front.Administrators must learn the intricacies of the operating systems and the applications involved in order to pull it off. A persistent workload is one that simply must be installed on a server or where the availability requirements are such that the length of time a computer takes to reboot is an unacceptable amount of downtime.The Admin API would also allow the creation of a multi-user system on a Qubes machine, where each user can have a different set of secure domains/environments.The project’s co-founder, Joanna Rutkowska, said that the Admin API wouldn’t get access to the lowest level of the system, called dom0, and that Qubes OS’ security should be preserved.

Leave a Reply