[virt-tools-list] [PATCH] Allow unsafe migrations in virt-manager

[Cole Robinson]

On 12/10/2013 04:33 PM, Charles Arnold wrote:
> Normally, setting cache=none is required in order to ensure a consistent view
> of storage between the source and destination migration hosts. However, some
> configurations have that quality without resorting to the use of an O_DIRECT
> open (which is what cache=none does), and hence cache=none wouldn't be
> necessary.
> 
> Unfortunately, libvirt is not able to determine on it's own all the
> configurations which require cache=none for migration but in the interest of
> safety enforces it when it isn't otherwise able to determine migration safety.
> 
> For this reason the libvirt api has an 'unsafe' option which allows the user
> to override the safety migration checks.
> 
> This patch adds a checkbox to allow unsafe migration to the 'Advanced options'
> portion of the migration dialog.
> 
> Signed-off-by: Charles Arnold <carnold at suse.com>
> 

Thanks, applied now.

- Cole