On 02/14/2011 05:13 PM, Tino Vazquez wrote:
Many thanks for the feedback. for now, we are going for our initial
approach, to ensure the same behavior for all the ESX versions.
ok, but think that the ESX version 4.1 will be the last. From there, VMware will
release only ESXi versions.
Best r
Hi carlopmart,
Many thanks for the feedback. for now, we are going for our initial
approach, to ensure the same behavior for all the ESX versions.
Regards,
-Tino
--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebu
On 02/11/2011 04:10 PM, Tino Vazquez wrote:
Hi Luigi,
We are aware of that possibility, but we rather don't go there if we
can avoid it. Reasons:
* It is an unsupported method (to activate the ssh server)
FYI, ssh is a supported method since version ESXi 4.1
* The ssh server is dropbea
Hi Luigi,
We are aware of that possibility, but we rather don't go there if we
can avoid it. Reasons:
* It is an unsupported method (to activate the ssh server)
* The ssh server is dropbear based, which is not as tested as openssh
* as you said, root access needed from OpenNebula front-end
Si
Thanks Tino!
In contrast with what it's written on the documentation *it is possible* to
connect to the ESXi hypervisors machines via ssh and launch commands (but
only as root user). I noticed that on the ESXi 4.1 machines that we got
installed there is a nice program called esxtop which can also b
Hi Luigi,
I've updated the ticket, I will be implementing this for the next release.
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor / Cloud Researcher
www.OpenNebula.org | @tinova79
On Wed, Feb 9, 2011 at 3:14 PM, Luigi Fortunati
wrote:
> Thanks Tino,
> That
Thanks Tino,
That is probably more a problem of libvirt, since VMWare IM Driver use it in
order to access information about the hosts.
In order to get information about the hosts OpenNebula launches a virsh
command and parses the output.
The script that does this work is located in $ONE_LOCATION/li
Hi Luigi,
There is a bug in the IM driver for VMware, is not reporting the Free
memory at all. I've opened a ticket to keep track of the issue [1], it
will be solved in the next release.
Regards,
-Tino
[1] http://dev.opennebula.org/issues/481
--
Constantino Vázquez Blanco, MSc
OpenNebula Major
Ok, I tried some tests today.
The hardware/software environment includes 2 cluster nodes (ESXi 4.1), 2Gb
of RAM, 2 AMD Opteron 246 Processors (2GHz), trial version licenses. The
opennebula installation is *self-contained*.
800MB of memory are used by the hypervisor itself (that info comes from
vSph
Hi,
You have to add also de CPU capacity for the VM (apart from the number of
virtual cpus CPUs). The CPU value is used at the allocation phase. However
you are specifying MEMORY and should be included in the allocated memeory
(USED MEMORY in onehost show) So I guess there should be other problem
I can post the VM template content on monday. However, as far as I remember,
the vm template was really simple:
NAME="Debian"
VCPU= 2
MEMORY=1024
DISK=[IMAGE="Debian5-i386"]
OS=[ARCH=i686]
The VMs can boot and run, I can log on console through vSphere Client on the
newly created VMs.
I noticed th
On Fri, Feb 4, 2011 at 10:35 AM, Luigi Fortunati
wrote:
> To Siva:
> As far as I know you can connect to the ESXi Server in three ways:
>
> libvirt and virsh (the way of OpenNebula-VMWare Driver):
> The VMWare Driver of OpenNebula uses virsh commands (which relies on
> libvirt) to access some hype
Hi,
I am not sure this is related to the VMware monitoring... Can you send the
VM Templates?
Thanks
Ruben
On Thu, Feb 3, 2011 at 5:10 PM, Luigi Fortunati
wrote:
> Hi,
> I noticed a serious problem about the usage of VMWare ESXi 4.1 and
> OpenNebula 2.0.1.
> I'm actually using the VMWare driver
Hi,
I noticed a serious problem about the usage of VMWare ESXi 4.1 and
OpenNebula 2.0.1.
I'm actually using the VMWare driver addon which can be found on the
opennebula website (ver. 1.0) and libvirt (ver. 0.8.7).
It happens that OpenNebula can't get information about the usage of
resources on the
14 matches
Mail list logo
