Hi Javier,
There is no kvm version mismatch. I had to downgrade libvirt installation
from 0.9 to 0.8 in order to fix the migrate issue.
Thanks a lot.
Regards,
Karthik
On Wed, May 18, 2011 at 6:53 PM, Javier Fontan wrote:
> Could this be the problem?
>
> https://bugs.launchpad.net/ubuntu/+sourc
Could this be the problem?
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/244467
Also, is kvm the same version in both hosts. Maybe a kvm version
mismatch can cause that problem.
On Thu, May 12, 2011 at 2:26 PM, Karthik Mallavarapu
wrote:
> Hello Javier,
> The issue comes when we try to mig
Hello Javier,
The issue comes when we try to migrate a VM onto this particular node. I
could deploy the VM successfully now because I had rebooted the problematic
node machine earlier. But now when I tried to migrate a VM from another node
to this particular node, the VM gets stuck in BOOT state.
Can you check /var/log/libvirt/qemu/one-54.log? There should be some info there.
On Tue, May 10, 2011 at 5:26 PM, Karthik Mallavarapu
wrote:
> Hello All,
> I have an opennebula installation with 1 frontend and two nodes. The base OS
> is ubuntu 10.10 64 bit edition. When I try to deploy a VM usin
Hello All,
I have an opennebula installation with 1 frontend and two nodes. The base OS
is ubuntu 10.10 64 bit edition. When I try to deploy a VM using the command
*onevm create ubuntu.template* the VM gets deployed successfully on one node
but it gets stuck in BOOT state on the other node. I am e
