Hello,
I am using a Linux NFS server to store and run my VM images and would like to
know what type of NFS mount does OpenNebula recommend for mounting the
datastore NFS shares on my ONE hosts. Would you rather recommend hard or soft
NFS mount options?
Regards
ML
Quoting ML mail (mlnos...@yahoo.com):
Hello,
I am using a Linux NFS server to store and run my VM images and would
like to know what type of NFS mount does OpenNebula recommend for
mounting the datastore NFS shares on my ONE hosts. Would you rather
recommend hard or soft NFS mount options?
Thanks for your input! I will change my NFS mounts for hard instead of soft, as
currently I have the following:
nfsserver:/data/01/one/datastores/100 /var/lib/one/datastores/100 nfs
soft,intr,rsize=8192,wsize=8192
any other options you might recommend or adapt?
On Wednesday, June 18,
noatime, nodiratime - might save some bandwidth
-Original Message-
From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of ML mail
Sent: Wednesday, June 18, 2014 11:07 AM
To: users@lists.opennebula.org
Subject: Re: [one-users] NFS hard or soft mount for datastores?
Thanks
Hello,
We tried to update to 4.6.2 from 4.6.0-1 (Debian Wheezy system with
packages obtained from opennebula.org), and MySql database. The
opennebula database wasn't upgraded (no onedb upgrade...), as it
wasn't needed, as stated in the upgrade instructions.
The upgrade went apparently well, but
Can you check that both one servers have correct time set? ntp should
be configured in both servers.
Also check if login with Keep me logged in checkbox fixes the problem.
On Tue, Jun 17, 2014 at 4:47 PM, Rhesa Mahendra
rh...@lintasmediadanawa.com wrote:
Hi,
If i change zone to other zone (
From what I see in the link you've sent this sanlock plugin works when
libvirt manages the storage, that is, cloning and deleting LVs.
OpenNebula does not use libvirt to manage storage, it is done by our
own drivers so it can be used also for xen (we don't use libvirt for
xen), VMware or other
Dear All,
Docker 1.0 was released recently. Megam is a cloud automation engine,
and would like to support this feature. With the latest release Docker
uses libcontainer.
Our *vision* is to enable and simplify running Docker container images
using Megam on OpenNebula.
*Terminology:*
*
Sorry for the huge delay. To test these kind of troubles you can try
executing the monitoring scripts manually. In the remote host as
oneadmin go to /var/tmp/one/im and execute this:
bash -x run_probes kvm /var/lib/one/datastores 4124 20 0 localhost
You should get more information about what's
When you say KVM monitor is it libvirtd?
OpenNebula probes use libvirt to talk to qemu/kvm so the must be seen
with virsh -c qemu:///system command. If this is not the case maybe a
libvirtd restart can fix the problem.
In one 4.6 we have changed this a bit. In 4.4 if there was no
information
We have several users using the fs_lvm in production, so yes, the
driver is completed and tested.
You can execute the monitoring script manually to check what could be
happening. In the remote host, as oneadmin, go to
/var/tmp/one/im/kvm-probes.d and execute:
bash -x ./monitor_ds.sh kvm
Hi,
It seems more related to an optimization of the mysql server rather than a
problem because of the update process. Yo may try to check the database
size, and maybe try purge the binary logs or optimize the tables.
Cheers
Ruben
On Wed, Jun 18, 2014 at 11:43 AM, Fernando Durá
Hi Javier,
Yes, it was libvirt and restarting it really helped. In the meantime I've
encountered similar sort of problem with datastore monitoring - one of the
connections to my SAN storage died and the vgdisplay commands issued by the
probe were getting stuck, thus each monitoring request
Please help. I'm having some recurring errors after VM is deploy PROLOG
and then powered on BOOT. At the BOOT phase I suspect there is something
going on ... because as soon as I *reboot* the VM I get Boot failed: could
not read the boot disk
Upon further inspection the libvirt qemu log files
Also,
When using the Gluster Datastore I've been getting this error as well when
I deploy a VM it gets hung up at BOOT. The former post was actually
deploying from default id 1 datastore which is a gluster mount point for
the same directory as the Gluster Datastore id 103.
Here get Permission
Hi folks,
I'm trying to set up my hosts to have the vm disk images stored locally.
From the ONE docs, it looks like I need to create a system datastore using
the ssh driver. However, I have done so yet the disk images remain on the
frontend node.
I used Sunstone to create a new datastore with
The previous error with the disk could be a permission problem. Are
you able to read/write the image? Can you check permissions in the
fuse mounted filesystem?
I've never got the stderr problem. This issue may be the culprit but
it was just the first thing I've found:
In the frontend the datastores are always at /var/lib/one/datastores.
The base path is only for nodes. If you want to use another filesystem
or path mount it in the datastore location or use a symlink.
On Wed, Jun 18, 2014 at 8:23 PM, kerryhall . kerryh...@gmail.com wrote:
Hi folks,
I'm trying
Sorry if I'm not understanding this correctly.
All running system disk images must fit in /var/lib/one on the frontend?
/var/lib/one is currently 1TB on my frontend, but I have hundreds of hosts,
each with 1-2TB of storage. I want the disk images for the running vms to
live on the hosts *only*.
Ok, in my excitement getting things tested here, I neglected to enable
virtualization in the BIOS on my second host. o_O
This works now!!
Thanks for the help Javier!!
Kerry
On Wed, Jun 18, 2014 at 3:47 PM, kerryhall . kerryh...@gmail.com wrote:
Sorry if I'm not understanding this correctly.
Hello Users,
Please see the TAB SEPARATED VALUES dump of an XMLRPC request to the
oneacct API:
http://i.imgur.com/1OyLw8f.png
I'm getting interesting values from the Accounting API, and it's not very
well documented [ OID, HID, CID, etcetera have no description in the XSD ]
; and I'm
Hi,
Am 18.06.2014 um 20:57 schrieb Javier Fontan jfon...@opennebula.org:
The previous error with the disk could be a permission problem. Are
you able to read/write the image? Can you check permissions in the
fuse mounted filesystem?
I've never got the stderr problem. This issue may be the
22 matches
Mail list logo
