yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

honestly, if you are going to do live migration it is assumed that you
have similar back ends. I'm not convinced a valid use case is live
migration to different filesystems.

** Changed in: nova
       Status: Incomplete => Won't Fix

** Changed in: nova
       Status: Won't Fix => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1175290

Title:
  Block migrating an instance from an O_DIRECT supported fs to non
  O_DIRECT supported fs fails

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  I tried block migrating an instance from a server that can use
  O_DIRECT to a server that has ZFS as a filesystem. This fails with
  libvirt complaining about:

  2013-05-01 19:12:05.286+0000: 12030: error : qemuProcessWaitForMonitor:1796 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/38
  kvm: -drive file=/var/lib/nova/instances/instance-000000ae/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /var/lib/nova/instances/instance-000000ae/disk: Invalid argument

  
  This either needs to be checked and fail or (preferably) the libvirt.xml needs to be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1175290/+subscriptions