Hi there,
I am starting to look at version 2.0 although my existing installation is still
1.4. If I do "git pull" in the git source, I think I get update to date in the
latest code for 2.0. My understanding is that 2.0 is not compatible with 1.4 so
I don't really want to get the 2.0 code for my
In my configuration we have small OS images (~ 1GB) and we allow the users
to use this image and expand the size as needed (via sparse image dd script)
as we don't have shared storage. I have been leveraging the DISK -> SIZE
operation in the 1.4 template code base along with custom transfer manag
Hello,
I have created a ticket to solve it making this value user configurable.
http://dev.opennebula.org/issues/348
Bye
On Mon, Sep 13, 2010 at 3:53 PM, Neil Mooney wrote:
> Perhaps this demonstrates that these arguments/options are better configured
> in the IM_driver, than hard wired into t
Perhaps (if you didnt already ), enable the debug level information:
http://www.opennebula.org/documentation:archives:rel1.2:cg
look for debug within the document:
#Debug for MADs.
# If set, MADs will generate cores andlogs in $ONE_LOCATION/var.
# Possible values are [0=ERROR, 1=DEBUG]
ONE_MAD
Perhaps this demonstrates that these arguments/options are better
configured in the IM_driver, than hard wired into the code.
At least then they are changeable without recompiling...
Just a thought.
Neil
On 09/13/2010 02:59 PM, Stefan Freitag wrote:
Hi Javier,
I agree with you that tap:aio s
hello, Im trying to follow the example of ubuntu installation in this link
http :/ / help.ubuntu.com / community / OpenNebula
I add the cluster node
onehost add cluster_xx im_kvm vmm_kvm tm_ssh
but when check the status of the node I got an error in the log saying that
the driver information co
Hi Javier,
I agree with you that tap:aio should be used instead of file:, but
sometimes it is not possible :-(
In Dortmund we had SLES 10 in place as OS for the physical machines and
this rejected to work properly with tap:aio.
SLES, as it is an enterprise server edition of SUSE, does not include
Hello,
Seems that there are problems monitoring the host as it does not show
information about CPU (all 0). Can you check
$ONE_LOCATION/var/oned.log for any monitoring errors? If you cannot
see anything there log into your "monaco-kvm1" node as oneadmin and
execute the biggest file at "/tmp/one-im
Hello,
If you are using OpenNebula 1.4 you can specify disk target as
"ioemu:hda". Also "tap:aio:" method should work with current versions
of Xen, in fact it is recommended method over "file:". That is my
understanding after reading Xen documentation and mailing lists.
Anyway if you really need
Hi,
I have been looking at the source for similar reasons.
I think the file you need to look at is:
./src/vmm/XenDriver.cc
At least to get an understanding of where it gets the arguments from.
Cheers
Neil
On 09/13/2010 12:47 PM, Ruben Diez wrote:
Hi:
When i create a VM on xen by use the O
Hi Jonathan,
To define an OpenNebula VMware template you need to set as the source
for the DISK the folder where all the VMware related VM files are
placed.
About the error you are experiencing, the configuration should be
(assuming you are using the tm_vmware driver, i discourage the use of
the
Hi:
When i create a VM on xen by use the OpenNebula stuff, in the created
"deployment.0" file the "disk" section looks like this:
disk = [
'tap:aio:/srv/cloud/one/var//123/images/disk.0,hda,w',
.
But i would to use a xen block device configuration like this:
disk = [
'file:/srv
Hello,
There are no XMLRPC calls where an XML is sent as input parameter.
Also we do not have schema definition on the output. I have reopened a
bug about it: http://dev.opennebula.org/issues/152
Meanwhile you can use CLI with -x parameter to get raw xml. For example:
$ onevm show -x
Also you
13 matches
Mail list logo
