Skip to content
master
Go to file
Code

Latest commit

Currently we set KVM migration capabilities only on the source instance
and leave them set even if migration fails. This leads to two problems:

 - There are a number of features (e.g. postcopy-ram) where the
   capability needs to be set on both, source and destination instance

 - If a migration breaks because of a capability mismatch, the
   capability remains set causing all future migration attempts to fail
   as well (see Debian bug #969028 [1])

Fix both issues by setting all capabilities on both sides of the
migration and clearing all capabilities on the surviving side when the
migration is over.

[1] https://bugs.debian.org/969028

Signed-off-by: Apollon Oikonomopoulos <apoikos@dmesg.gr>
4d8c16a

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
doc
 
 
lib
 
 
man
 
 
qa
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README

Ganeti 3.0
===========

For installation instructions, read the INSTALL and the doc/install.rst
files.

For a brief introduction, read the ganeti(7) manpage and the other pages
it suggests.

Please note, that there is no supported upgrade path for users running
Ganeti-2.17 (i.e. 2.17.0 beta1). Ganeti-2.17 was never released, so
hopefully no one uses it.

About

Ganeti is a virtual machine cluster management tool built on top of existing virtualization technologies such as Xen or KVM and other open source software.

Topics

Resources

License

Packages

No packages published
You can’t perform that action at this time.