You are viewing a plain text version of this content. The canonical link for it is here.
Posted to tashi-commits@incubator.apache.org by st...@apache.org on 2012/08/08 02:34:06 UTC
svn commit: r1370641 - /incubator/tashi/trunk/doc/INSTALL2
Author: stroucki
Date: Wed Aug 8 02:34:05 2012
New Revision: 1370641
URL: http://svn.apache.org/viewvc?rev=1370641&view=rev
Log:
INSTALL2: Note Qemu version incompatibilities, and the risk for migrations
Modified:
incubator/tashi/trunk/doc/INSTALL2
Modified: incubator/tashi/trunk/doc/INSTALL2
URL: http://svn.apache.org/viewvc/incubator/tashi/trunk/doc/INSTALL2?rev=1370641&r1=1370640&r2=1370641&view=diff
==============================================================================
--- incubator/tashi/trunk/doc/INSTALL2 (original)
+++ incubator/tashi/trunk/doc/INSTALL2 Wed Aug 8 02:34:05 2012
@@ -22,6 +22,15 @@ should be chosen so that there is always
accounting data. Otherwise, this could lead to VMs running but not known
to the nodemanager.
+If you are using Qemu/KVM as the hypervisor, be advised that the VM
+format changes rather quickly. E.g. version 1.1 of Qemu states it will
+accept migrations in from versions 0.13 to 1.1. Migrations out are
+liable to be dropped on the floor by a receiving older version Qemu
+(with a successful return from the sending Qemu). Be careful to only
+deploy Qemu versions in your cluster that can work together. Since
+suspend and resume are handled via the same mechanisms, the above caveat
+applies to these actions too.
+
---+ Deployment over multiple networks
To add additional networks to the Apache Tashi cluster, they should be