[Bug 448674] Re: VM is suspended after live migrate in Karmic

[Mark Burgo]

Well Question then?

Karmic is to be supported for another year, correct?

This is a bug with karmic correct?

the workaround is to suspend and then resume the vm this removes live
migration from the mix if I have to do the suspend and resume.   Why not
just backport libvirt-0.7.2 from the version of lucid that was working
to karmic  so that live migration works as advertised?

Lucid is still at beta 1  while I will try it for you  it is not usable
in production because to much of the pacemaker utilities are not in the
lucid release at this time requiring ppa's to be installed for fully
functional systems.

Weather the bug meets the SRU is not the question the question is we
have a bug on a system that redhat released the patches for months ago
and it was not fixed on a ubuntu release that is to be supported for
another year.  This needs fixed as not everyone will install lucid the
day it is released.  I enjoy working with ubuntu and this is a problem
that must be corrected before the release of lucid on the karmic
platform.

Unless you have a full workaround that does not require someone
connecting and suspending and resuming the migrated VM then it is not a
valid workaround.   we need the vm to migrate without human intervention

Thank You

P.S.  the lucid beta 1 is being installed as we speak on a set of test
boxes to attempt the test.  However, as I stated above not all of the
pacemaker+openais/heartbeat packages are in the beta release so it is
not even a valid environment to run any thing on at this time.

-- 
VM is suspended after live migrate in Karmic
https://bugs.launchpad.net/bugs/448674
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.