[one-users] ttylinux via ssh not accessible any more after migrate / suspend -> resume
mauch at kit.edu
Thu Sep 2 15:54:24 PDT 2010
one more time,
I'm now working with OpenNebula 2.0beta with the KVM Hypervisor (head
node and cluster nodes are based on 10.04). I tried to play with the
supported ttylinux image form the ONE website. Starting the machine and
login via ssh is no problem. After Stop -> Resume the machine is still
available via network.
But if I perform a migration of the the machine or suspend -> resume,
the network conncetion is gone (ping / ssh find no aim). I looked via
VNC into the VM, and everything looks ok, the eth0 device is still
configured right, but also no possibility to ping something others
outside the VM. Restarting of the network did not solve the problem. The
log files are clear. All physical hosts are in the same switch.
Does anyone have an idee what goes wrong??
Am 30.08.2010 11:32, schrieb Javier Fontan:
> Can you try to access it by other means to check if there is something
> broken in the VM? If you are using xen you should be able to access it
> using "xm console" from the physical node. With KVM you can add VNC
> access to it.
> If the machine seems to be in good shape there can also be some
> problem in the network relearning where the machine is. Are both
> physical hosts in the same switch?
> On Mon, Aug 30, 2010 at 12:56 AM, Viktor Mauch<mauch at kit.edu> wrote:
>> I use ONE 1.4 with a shared NFS and play a litle bit with the ttylinux image
>> which automatically configures the eth0 device during booting.
>> The VM is accessible via SSH and everything looks fine. After livemigration,
>> normal migration or suspend->resume the ssh connection is no longer
>> $ ssh root at VM_IP
>> ssh: connect to host VM_IP port 22: No route to host
>> Users mailing list
>> Users at lists.opennebula.org
More information about the Users