1 / 27

Live Migration of Virtual Machines

Live Migration of Virtual Machines. Presented by: Edward Armstrong University of Guelph. Overview. Problem Description Solutions Strengths and Weaknesses Results. Migrating an OS - Complexity. Migrating an OS – Timescale. Considerations. Both machines must be active at the same time.

carol
Download Presentation

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 Presented by: Edward Armstrong University of Guelph

  2. Overview • Problem Description • Solutions • Strengths and Weaknesses • Results

  3. Migrating an OS - Complexity

  4. Migrating an OS – Timescale

  5. Considerations • Both machines must be active at the same time. • Migration of active live services. • Total migration time. • Resource contention.

  6. Migrating memory

  7. Memory - Pure stop and copy. • Pros • Simplicity. • Consistency. • Cons • Downtime proportional to memory. • Unacceptable for live services. Source Machine Target Machine

  8. Memory - On demand migration. • Pros • Shorter downtime. • Consistency. • Cons • Longer migration time. Page fault request Send page Source Machine Target Machine

  9. Memory - Pre copy migration. • Pros • Copy low fault pages quickly. • Works well for live processes. • Cons • Large number of faults for busy memory. Iterative push Live page fault Source Machine Target Machine

  10. Network and disk resources. • Unique to an OS instance. • Ordering of resources are non-determinsitic. • Need to maintain open network connections.

  11. Resolving network connections with an ARP* response. Source Machine No Address LAN Packets Target Machine 192.168.0.102 *ARP: Address Resolution Protocol

  12. Resolving network connections with an ARP* response. Unsolicited ARP reply Source Machine No Address LAN Packets Target Machine 192.168.0.102 *ARP: Address Resolution Protocol

  13. Resolving network connections with an ARP* response. Packets Source Machine 192.168.0.102 LAN Target Machine No Address *ARP: Address Resolution Protocol

  14. Network resources. • Pros • Handled by external devices. • Similar scheme can be used to migrate disk services (not covered in paper). • Cons • Small amount of packet loss. • Requires a LAN with unsolicited ARP responses enabled.

  15. Design Overview Select a new target machine Source Machine Target Machine

  16. Design Overview Confirm available resources on target. Failure means VM continues to run on source. Source Machine Target Machine

  17. Design Overview Transfer memory. Retransmit memory used during transfer. Source Machine Target Machine

  18. Design Overview Halt source to redirect network traffic and transfer CPU state. Source Machine Target Machine

  19. Design Overview Verify transfer complete. Disable source. Source Machine Target Machine

  20. Design Overview Activate target machine Target Machine Source Machine

  21. Summary of Design • At all times there is at least one consistent image available. • Minimized down time. • Not a fast process overall. • Requires tuning. • Requires certain hardware.

  22. Performance – Dirty Pages. 8 second granularity, used to decide which pages make for good pre-migration.

  23. Performance

  24. Performance 1- 4 pre-copy iterations

  25. Performance 1- 4 pre-copy iterations

  26. Performance 1- 4 pre-copy iterations

  27. Thank You

More Related