Hi Jaime,
the fix is working for me. Thank you.
I have to see, if this new LVM datastore works for my use case. I am not
using CLVM, so I think I have to change the drivers a bit. Because
Snapshosts with CLVM will not work with RHEL6 :/
Regards,
Stefan
On Fr, 2012-07-13 at 12:31 +0200, Jaime Me
Stefan,
You are right. It's a bug. We've created an issue and uploaded a patch:
http://dev.opennebula.org/issues/1358
We're also going to add to the know issues page [1] and the lvm
documentation guide [2].
[1] http://opennebula.org/documentation:rel3.6:known_issues
[2] http://opennebula.org/docu
Hello Jaime,
I followed your steps, but they are not working for me.
I put the raw image in /scratch/execnode.img and created a template for
it with the PATH attribute. I did this on host01, my front end with oned
running etc.
I registered the image and ONE created a LV on host03, one of my LVM
ho
Hello Stefan,
Yes, there was a major change in the SOURCE attribute between the versions
you mention. The current LVM drivers don't support SOURCE the way you are
using them, since the expect a specific format for the SOURCE and your
example "/dev/vg_cloud/execnode" doesn't work since it doesn't m
Hello,
I upgraded my installation from ONE 3.2 -> 3.6 with running virtual
machines without trouble, but I am facing some problems with the new LVM
datastore. I have some hosts with LVM (no CLVM!) and the volume group
vg_cloud.
Creating the datastore works without problems. The image is already o
