News for hackers. Stuff that matters.
Re:Xen hypervisor memory corruption due to x86 emulator flaw by peterwwillis on Tuesday March 10, 2015 @11:00AM (#9178044)
If they have one spare xen host they can live migrate all guests from one host to the spare, patch the original host, reboot, then live migrate the spare's guests back to the original, and repeat. Patching them all and rebooting them all at once might be quicker though.
Re:Xen hypervisor memory corruption due to x86 emulator flaw by mikeash on Tuesday March 10, 2015 @11:52AM (#9178378)
Do you need to migrate them back? Would be faster to just use the newly patched original host as the new spare, and repeat like that.
Re:Xen hypervisor memory corruption due to x86 emulator flaw by jroll on Tuesday March 10, 2015 @11:36AM (#9178269)
This becomes a physics problem; it's a race between how quickly VMs can be migrated and when the embargo is lifted.
Re:Xen hypervisor memory corruption due to x86 emulator flaw by avsm on Tuesday March 10, 2015 @02:54PM (#9179795)
The XenServer toolstack supports exactly this mode of operation in a pool of physical hosts via a 'host evacuate' operation that live relocates VMs away and brings them back once the host upgrade is complete.

http://docs.vmd.citrix.com/XenServer/5.0.0/1.0/en_gb/install...