Hi Hector:
Hi,
I see now the original filename was ok, i mixed it up with the
template parameter. Do you see any error poping up in Sunstone? Can
you try debugging the upload with firebug, see if the POST comes back
with a body that might offer more hints (make sure you try uploading a
file
Hi Alvaro,
On 28 February 2013 09:38, Alvaro Simon asi...@cesga.es wrote:
Hi Hector:
Hi,
I see now the original filename was ok, i mixed it up with the template
parameter. Do you see any error poping up in Sunstone? Can you try debugging
the upload with firebug, see if the POST comes back
Hi,
I think the datastore is needing some extra information, which can be found
here [1]. You are lacking the BRDIGE_LIST option:
BRIDGE_LIST Space separated list of ESX servers that are going to be used
as proxies to stage images into the datastore (vmfs datastores only)
Set it to one of your
I've created a ticket with this:
http://dev.opennebula.org/issues/1788
I also think it is good to use one parameter to select the output
format instead of adding multiple ones (like --xml, --template,
--json, etc).
Thanks
On Wed, Feb 27, 2013 at 4:50 PM, Hans-Joachim Ehlers
It seems that there are problems with the values returned by he
probes, specifically this:
FREESPACE= TOTALSPACE= USEDSPACE=
Could you send us the list of files in /var/tmp/one/remotes/im/kvm.d?
It seems you have added a probe that is not behaving correctly.
On Tue, Feb 26, 2013 at 11:55 AM,
Hi Daniel
Currently you are running Susntone using Webrick. I think the problem
is, Webrick provides a StringIO instead of a Tempfile as expected in
the Sunstone code.
Could you try installing another server, for example thin (gem install
thin), restart Sunstone server and check that is indeed
On 28 February 2013 13:45, Alvaro Simon asi...@cesga.es wrote:
Hi Daniel
Currently you are running Susntone using Webrick. I think the problem
is, Webrick provides a StringIO instead of a Tempfile as expected in
the Sunstone code.
Could you try installing another server, for example thin
Hello,
as I am currently starting to get acquainted with OpenNebula, I need
some help with save migration.
I have setup a cluster with two equal servers. I have installed CentOS
6.3 with the OpenNebula Packages from the repository (version 3.8.1-2.6)
on each of them. Using the sunstone
Tino, I edit the vmfs.conf, and setting the BRIDGE_LIST. I not work. I
work in two scenarios : The firts DS=vmfs - TM=vmfs - sytemTM=ssh, the
secound DS=vmware TM=ssh - sytemTM=ssh. (scenarios 2.1 and 2.3 in
http://opennebula.org/documentation:rel3.8:vmware_ds).
In the first scenario(DS=vmfs
...
URL:
http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130228/22477853/attachment.htm
--
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Hi Kapetanakis.
I think you can achieve all those things without hacking code.
* Using block devices directly:
A suggested workflow to work directly with block devices is to create a new
empty persistent image of type datablock and use it inside a VM and install
the OS directly to that image.
Hi Tobias,
I have no idea why that's happening to you. I'm wondering, have you tried
start the VM manually in the host after it fails to deploy? the files
should be still there until you do onevm delete.
$ virsh create /var/lib/one/datastores/0/vm_id/deployment.0
Does
Sorry Tobias, the command I sent is not the correct one, you have to
explicitely say that you want to connect to the system socket. Do this
instead:
$ sudo -u oneadmin virsh -c qemu:///system create deployment.0
On Thu, Feb 28, 2013 at 6:14 PM, Tobias Honacker
t.honac...@googlemail.comwrote:
Hi Jaime,
bash-4.1$ sudo -u oneadmin virsh -c qemu:///system create deployment.0
Fehler: Fehler beim Erstellen der Domain von deployment.0
Fehler: internal error process exited while connecting to monitor: qemu-kvm:
-drive
Is 'oneadmin' in the 'disk' group? can you try that?
On Thu, Feb 28, 2013 at 6:28 PM, Tobias Honacker
t.honac...@googlemail.comwrote:
Hi Jaime,
bash-4.1$ sudo -u oneadmin virsh -c qemu:///system create deployment.0
Fehler: Fehler beim Erstellen der Domain von deployment.0
Fehler: internal
Hi Jaime,
It works, thanks. Don't know why i don't try this.
Thanks for support. Maybe we should put this to the documentation.
Best regards,
Tobias
Von: Jaime Melis jme...@opennebula.org
Datum: Thu, 28 Feb 2013 18:35:23 +0100
An: Tobias Honacker t.honac...@googlemail.com
Cc: Users
Hi,
Yes, I just added it to the docs, I don't know why it wasn't there in the
first place.
I'm glad it's working now.
cheers,
Jaime
On Thu, Feb 28, 2013 at 6:43 PM, Tobias Honacker
t.honac...@googlemail.comwrote:
Hi Jaime,
It works, thanks. Don't know why i don't try this.
Thanks for
Hi,
The set up seems to be fine.
First problem
---
What is the output of the following in the front-end?
bash -xv /var/lib/one/remotes/datastore/vmfs/cp
18 matches
Mail list logo