Live Migration does not work unless cache=none

Bug #1222682 reported by Jesse Pretorius
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Undecided
Yassine
openstack-manuals
Won't Fix
High
Unassigned

Bug Description

If O_DIRECT is not supported, 'cache=none' is not set. Thus, Live Migration gives the following error:

"Live Migration failure: Unsafe migration: Migration may lead to data corruption if disks use cache != none"

However, it is ok to migrate if the storage is "coherent" across nodes. So Nova's live-migration should support the Libvirt's unsafe=True flag.

Ideally there should be a nova flag which can be set to pass through the libvirt 'unsafe=true' flag. My thinking is that if 'cache=writethrough' is set then the underlying storage should be safe, but perhaps it's best not to make that assumption and rather to have a nova.conf flag.

Tags: libvirt nova
tags: added: libvirt
Changed in nova:
assignee: nobody → Yassine (yassine-lamgarchal)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/49329

Changed in nova:
status: New → In Progress
Revision history for this message
Yassine (yassine-lamgarchal) wrote :

I noticed the options 'live_migration_flag' and 'block_migration_flag' in nova.conf which can be used for adding the flags VIR_MIGRATE_UNSAFE so that it fixes the issue.

What do you think about ?

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote : Re: [Bug 1222682] Re: Live Migration does not work unless cache=none

Fair point. As long as the options are shown in the documentation at
http://docs.openstack.org/grizzly/openstack-compute/admin/content/configuring-migrations.html#true-live-migration-kvm-libvirt
 and
http://docs.openstack.org/grizzly/openstack-compute/admin/content/hypervisor-configuration-basics.html
then
a deployer will know that the options are available.

On 14 October 2013 18:10, Yassine <email address hidden> wrote:

> I noticed the options 'live_migration_flag' and 'block_migration_flag'
> in nova.conf which can be used for adding the flags VIR_MIGRATE_UNSAFE
> so that it fixes the issue.
>
> What do you think about ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1222682
>
> Title:
> Live Migration does not work unless cache=none
>
> Status in OpenStack Compute (Nova):
> In Progress
>
> Bug description:
> If O_DIRECT is not supported, 'cache=none' is not set. Thus, Live
> Migration gives the following error:
>
> "Live Migration failure: Unsafe migration: Migration may lead to data
> corruption if disks use cache != none"
>
> However, it is ok to migrate if the storage is "coherent" across
> nodes. So Nova's live-migration should support the Libvirt's
> unsafe=True flag.
>
> Ideally there should be a nova flag which can be set to pass through
> the libvirt 'unsafe=true' flag. My thinking is that if
> 'cache=writethrough' is set then the underlying storage should be
> safe, but perhaps it's best not to make that assumption and rather to
> have a nova.conf flag.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1222682/+subscriptions
>

--
Jesse Pretorius
mobile: +27 83 680 5492
email: <email address hidden>
skype: jesse.pretorius

Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → High
milestone: none → icehouse
status: Confirmed → Triaged
tags: added: nova
Revision history for this message
Anne Gentle (annegentle) wrote :

The code itself is abandoned. The referring URLs are grizzly. Marking as won't fix.

Changed in openstack-manuals:
status: Triaged → Won't Fix
Tom Fifield (fifieldt)
Changed in openstack-manuals:
milestone: icehouse → none
Joe Gordon (jogo)
Changed in nova:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.