CloudBioLinux - Eucalyptus version always freezing after boot

34 views
Skip to first unread message

Ócsvári Ádám [ocsi]

unread,
Apr 2, 2012, 6:44:37 PM4/2/12
to cloudbiolinux
I have a running Eucalyptus 3 cloud, with ESXi nodes. I'm trying to
run the Eucalyptus version of the CloudBioLinux.
After the run instance command everything looks fine, the instance is
starting, I can check it in the vSphare client. I've get the gui, the
desktop. It looks like boot is finished.. but there is everything
frozen. (Mouse, keyboard..)
I try to login with ssh, its also not working.
Other type of instances are working fine.
Its a fresh install from Eucalpytus and also from CloudBioLinux.

Does anyone have any idea, what can be the problem and/or the solution?

agbiotec

unread,
Apr 19, 2012, 12:28:41 PM4/19/12
to cloudb...@googlegroups.com
Hello,

  it seems you are running Eucalyptus from inside VMware ??? Could you
provide more details on your setup, and the commands you are using to
import / run the instances ?

 Also, which file exactly you've downloaded from cloudbiolinux.org, and
imported in your "Eucalyptus" ? We have only tested it on a Eucalyptus
cloud running directly on Ubuntu 11.04 Server (no VMware involved).

 Ntino

Ócsvári Ádám [ocsi]

unread,
Apr 24, 2012, 12:19:54 PM4/24/12
to cloudbiolinux
I'm using the same, Ubuntu 11.04 Server for eucalyptus 3.0. And I
have WMVare ESXI 4.1 nodes connected to the Eucalyptus management
system. I can run different instances on my cloud, it works fine.
I've downloaded this weeks ago:
https://s3.amazonaws.com/cloudbiolinuxvms/CloudBioLinux-32bit.Eucalyptus.img
And configured it with Ubuntu cloud-utils.
I can run this instance on my cloud. At vSphere Client I can see the
instance, I get the GUI, but there is nothing works (mouse, keyboard)
and no answer for ping, ssh. I spoke with the eucalyptus guys and they
said the problem is maybe with the file system, and definitely not too
good to use a 20GB image. Is this size really necessary? Maybe it will
be better to run a lightweight instance and then attache a volume with
the necessary data.

(for commands I use the same euca-run-instance emi-XXXX -t xlarge
command)

Adam
Reply all
Reply to author
Forward
0 new messages