Hi,
Am 03.07.2014 16:59, schrieb Jaime Melis:
As far as I know, the shared_lvm hasn't been updated lately:
- https://github.com/OpenNebula/addon-shared-lvm-single-lock
- http://community.opennebula.org/shared_lvm
also having the issue in OpenNebula 4.6.0
Fabian
Hi,
Recently I found there is a support for locks in libvirt, has anybody
tried that? Anybody uses fcntl with lvm?
Thanks
Dne 14-07-06 02:41 AM, Fabian Zimmermann napsal(a):
Hi,
Am 03.07.2014 16:59, schrieb Jaime Melis:
As far as I know, the shared_lvm hasn't been updated lately:
-
As far as I know, the shared_lvm hasn't been updated lately:
- https://github.com/OpenNebula/addon-shared-lvm-single-lock
- http://community.opennebula.org/shared_lvm
On Fri, Jun 27, 2014 at 9:40 PM, Miloš Kozák milos.ko...@lejmr.com wrote:
Hi,
it is great to know, is it related to the
Hi,
Issues with delete and shutdown have been greatly improved in
OpenNebula 4.4+, I would recommend upgrading as far as possible.
Best,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
Hi,
it is great to know, is it related to the improved monitoring in ONE? I
am getting ready for trials of ONE 4.6.
We are using shared_lvm driver, so I would like to know if the new LVM
driver is compatible with it? Or I can expect some major issues? I
havent had enough time to check..
Hi all,
We are using Opennebula 4.2 system with several hosts ( KVM + network
storage) .
Recently we have discovered, by having disk r/w issues on a VM, that after
a delete - recreate action, specific VM is running on two different hosts:
the old placement host and the new placement host.
Hi, I would like to add that I have experienced it few times with ONE 3.8..
On 6/26/2014 9:34 AM, Robert Tanase wrote:
Hi all,
We are using Opennebula 4.2 system with several hosts ( KVM +
network storage) .
Recently we have discovered, by having disk r/w issues on a VM, that
We have also seen this behavior in OpenNebula 3.2.
It appears that the failure mode occurs because the onevm delete
(or shutdown or migrate)
doesn't correctly verify that the virtual machine has gone away.
It sends the acpi terminate signal to the virtual machine
but if that fails, the VM will
