Hi,
I don't entirely understand the difference between both options, could you
explain in more detail what you mean by distributing the datastore to all
the nodes?
Assuming your configuration is as follows: NFS Server exports datastores 0
and 1 - Mounted in Frontend + Nodes
I recommend the
Jaime,
Thanks for your reply, now datastore 0 and datastore 2 are in existing
storage box, mounted in frontend + nodes, we want to move datastore 0
and datastore 2 from existing storage box to frontend + nodes, could it
be done?
So in existing storage box just have datastore 1 and in new
Rhesa,
the problem is datastore 0, it's the system datastore. If you move it to
the local nodes, it will not be shared and synchronized across the nodes,
therefore you will lose many benefits like live-migration and instant
persintant image VM deployment.
Why is it that you want to move
Datastore 0 and datastore 2 will be synchronized frontend + nodes (we
just use persistent image) so i think datastore 0 just synchronized
symbolic link.
If we have problem maybe existing storage box (datastore 1) broken, all
vm used new storage box ( datastore 100) will not impact with
We are going to convert it to a more compatible version and reupload.
Hello, guys. Any progress on that?
Thanks.
On 08/21/2014 04:23 PM, Javier Fontan wrote:
We found a problem with the format of that image. It only works with
qemu = 1.10. We are going to convert it to a more compatible
Probably we should have explained these changes more clearly in the
release notes. There were two things we wanted to do with the repos:
* Have repositories for development versions so it is easier to test
* Separate repositories between series so the software is not upgraded
accidentally from
Dear all,
we've just published the talks of the two recent Dojos:
http://opennebula.org/aftermath-of-the-latest-centos-dojos-cologne-and-paris/
regards,
Jaime
--
Jaime Melis
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | jme...@opennebula.org
Hi.
I have set the dialog width in the function setupCreateVMDialog of vms-tab.js
to 1%: dialog.width(“1%”);
With that set, the Create VM window renders OK in Google Chrome on Red Hat
(except it is a bit large) and still renders OK in Google Chrome on Windows and
in Firefox.
I guess this is
Greetings,
I am attempting to attach a CDROM image to a running VM via Sunstone but
the command fails with the following error:
Tue Aug 26 08:52:21 2014 [Z0][VMM][D]: Message received: LOG E 24
attach_disk: Command virsh --connect qemu:///system attach-device one-24
Hey guys,
Are there any known issues running Wheezy together with QEMU/ KVM 2.1
from wheezy-backports and ONE 4.8?
Thanks for sharing,
Arnold
--
Arnold Bechtoldt
Karlsruhe, Germany
0xE2356889.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
Hi
when I create a template of type cdrom and try to upload dell'immagene iso I
get the following error.
TTP/1.1 500 Tue Aug 26 20:39:33 2014 [I]: 192.168.2.244 - - [26/Aug/2014
20:39:33] GET
/image?timeout=falsecsrftoken=bf59266c40d563bfad0576a92cb00167 HTTP/1.1
401 - 0.0029
Tue Aug 26
Hi,
We are testing Debian 7 (wheezy) with QEMU/KVM 2.1 and kernel from
wheezy-backports. Still not in production. So far no problems (even
Windows 2012 R2 works OK). (No ceph support, but it is not problem in
our case).
Regards,
Rolandas
P.S. Our testbed is OpenNebula 4.8.
On 2014.08.26
12 matches
Mail list logo