LWN.net Logo

Proxmox VE 1.5: combining KVM and OpenVZ

Proxmox VE 1.5: combining KVM and OpenVZ

Posted Feb 26, 2010 13:10 UTC (Fri) by ebirdie (subscriber, #512)
Parent article: Proxmox VE 1.5: combining KVM and OpenVZ

I wonder the limitation of OpenVZ containers/VMs stored to local repository only. How one can migrate a system in OpenVZ container to another machine, if the host machines aren't sharing a storage to run VMs from?


(Log in to post comments)

Proxmox VE 1.5: combining KVM and OpenVZ

Posted Feb 26, 2010 18:27 UTC (Fri) by dowdle (subscriber, #659) [Link]

OpenVZ has had live migration for over two years now... and the way the vzmigrate script does it (a stock part of OpenVZ) is by doing multiple rsync passes. It does the first pass while the container continues to run, then does a checkpoint, and then does a second rsync, and then a restore.

Depending on the filesystem size, it can take a while... although if the deltas are small for the second rsync pass, the perceived "downtime" caused by the migration is usually only a few seconds... with network connections maintained. For offline migrations, where the container is shutdown completely and then restarted on the target host, downtime is generally only 20-30 seconds... depending on how long it takes to start up the container.

I would imagine that Proxmox VE uses vzmigrate or their own script designed similar to vzmigrate, but I'm not positive.

Proxmox VE 1.5: combining KVM and OpenVZ

Posted Feb 27, 2010 16:47 UTC (Sat) by evgeny (guest, #774) [Link]

I don't know about Proxmox, but OpenVZ per se does not have to run off local storage. I've been happily managing a two-peer OpenVZ redundant/load balancing cluster on top of DRBD+heartbeat. Live migration typically takes about one second.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds