Have you tried setting the uid/guid as part of the gluster volume? For oVirt it uses 36:36 for virt
gluster volume set DATA storage.owner-uid 36
gluster volume set DATA storage.owner-gid 36
I'm assuming, setting this will enforce these ownership permissions on all files.
On Sun, Jan 26, 2014 at 10:42 PM, Paul Boven <boven@xxxxxxx> wrote:
Hi Bernhard,
Indeed I see the same behaviour:
When a guest is running, it is owned by libvirt:kvm on both servers.
When a guest is stopped, it is owned by root:root on both servers.
In a failed migration, the ownership changes to root:root.
I'm not convinced though that it is a simple unix permission problem, because after a failed migration, the guest.raw image is completely unreadable on the destination machine, even for root (permission denied), whereas I can still read it fine (e.g. dd or md5sum) on the originating server.
Regards, Paul Boven.
On 01/23/2014 08:10 PM, BGM wrote:
Hi Paul,
thnx, nice report,
u file(d) the bug?
can u do a
watch tree - pfungiA <path to ur vm images pool>
on both hosts
some vm running, some stopped.
start a machine
trigger the migration
at some point, the ownership of the vmimage.file flips from
libvirtd (running machnie) to root (normal permission, but only when stopped).
If the ownership/permission flips that way,
libvirtd on the reciving side
can't write that file ...
does group/acl permission flip likewise?
Regards
Bernhard
On 23.01.2014, at 16:49, Paul Boven <boven@xxxxxxx> wrote:
Hi Bernhard,
I'm having exactly the same problem on Ubuntu 13.04 with the 3.4.1 packages from semiosis. It worked fine with glusterfs-3.4.0.
We've been trying to debug this on the list, but haven't found the smoking gun yet.
Please have a look at the URL below, and see if it matches what you are experiencing?
http://epboven.home.xs4all.nl/gluster-migrate.html
Regards, Paul Boven.
On 01/23/2014 04:27 PM, Bernhard Glomm wrote:
I had/have problems with live-migrating a virtual machine on a 2sided
replica volume.
I run ubuntu 13.04 and gluster 3.4.2 from semiosis
with network.remote-dio to enable I can use "cache mode = none" as
performance option for the virtual disks,
so live migration works without "--unsafe"
I'm triggering the migration now through the "Virtual Machine Manager" as an
unprivileged user which is group member of libvirtd.
After migration the disks become read-only because
on migration the disk files changes ownership from
libvirt-qemu to root
What am I missing?
TIA
Bernhard
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
--
Paul Boven <boven@xxxxxxx> +31 (0)521-596547
Unix/Linux/Networking specialist
Joint Institute for VLBI in Europe - www.jive.nl
VLBI - It's a fringe science
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
--
Paul Boven <boven@xxxxxxx> +31 (0)521-596547
Unix/Linux/Networking specialist
Joint Institute for VLBI in Europe - www.jive.nl
VLBI - It's a fringe science
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
