1 / 24

Live migration of Virtual Machines

This paper discusses advanced techniques for live migration of virtual machines, focusing on optimal strategies that minimize downtime and enhance performance. By integrating live OS migration into the Xen virtual machine monitor, it enables rapid relocation of interactive workloads while maintaining service integrity. The evaluation highlights the success of migrating complex server workloads efficiently, achieving downtime as low as 210ms for standard applications and 60ms for gaming servers. Future work will expand on cluster management and network redirection methodologies.

linus-vasquez
Télécharger la présentation

Live migration of Virtual Machines

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Live migration of Virtual Machines Nour Stefan, SCPD

  2. Introduction • Related work • Design • Writable Working Sets • Implementation Issues • Evaluation • Future work • Conclusions

  3. Introduction • OS virtualization • Data centers • Cluster computing • Live OS migration • Avoid problem of “residual dependencies” • In-memory state can be transferred in a consistent and efficient way • Kernel-internal state • Application-level state • Separation of concerns between Users and Operator of a data center or cluster • Separation of hardware and software considerations, and consolidating clustered hardware into a single coherent management domain • High-performance migration support for Xen

  4. Related work • Collective project • For slow connections and longer time spans • Stop the OS execution while transfer • Zap • NomadBIOS • Pre-copy migration • Not adapting to the writable working set

  5. Design • Migrating memory • Balancing Downtime and Total migration time • Push phase • Stop-and-copy phase • Pull phase • Local resources • Connections to local devices(disks , network interfaces) • Single switched LAN • Generate an unsolicited ARP reply from migrated host, advertising that the IP has moved to a new location • Network-Attached Storage

  6. Writable Working Sets

  7. Measuring Writable Working Sets

  8. Measuring Writable Working Sets

  9. Measuring Writable Working Sets

  10. Implementation Issues • Managed migration • Performed largely outside the migratee • Migration daemons running in the management VM of the source and destination (new VM on destination) • Rounds of copying (dirtied during the previous round) • Dirty bitmap copied from Xen at start of each round • Shadow page tables (read-only page-tables entries => page fault trapped by Xen)

  11. Implementation Issues • Self migration • Implemented within the migratee OS • Migration stub on destination machine • Consistent OS checkpointing • Two-stage stop-and-copy phase • Disables all OS activity except for migration => final scan of dirty bitmap => shadow buffer • Transfer shadow buffer

  12. Implementation Issues • Dynamic Rate-Limiting • Rapid Page Dirtying

  13. Evaluation • Test setup • Dual Intel Xeon 2GHz CPU and 2GB memory • TG3 broadband

  14. Evaluation

  15. Evaluation

  16. Evaluation

  17. Evaluation

  18. Future work • Cluster management • Wide Area Network redirection • Migrating Block Devices

  19. Conclusions • By integrating live OS migration into the Xenvirtual machine monitor we enable rapid movement of interactive workloads within clusters and data centers. Our dynamic network-bandwidth adaptation allows migration to proceed with minimal impact on running services, while reducing total downtime to below discernable thresholds. • Our comprehensive evaluation shows that realistic server workloads such as SPECweb99 can be migrated with just 210ms downtime, while a Quake3 game server is migrated with an imperceptible 60ms outage.

  20. ?

More Related