On 08/07/2021 10:34, Michal Prívozník wrote:
On 7/5/21 11:28 PM, lejeczek wrote:
Hi guys
I'm trying to spin up a VM whose image is on a GlusterFS vol, and I fail:
-> $ virsh create /var/lib/pacemaker/conf.d/win10Pro.xml
error: Failed to create domain from /var/lib/pacemaker/conf.d/win10Pro.xml
error: failed to initialize gluster connection (src=0x7f0af807b410
priv=0x7f0af8090070): Invalid argument
In logs:
...
2021-07-05 21:13:12.950+0000: 141524: warning :
virSecurityDACSetOwnership:828 : Unable to restore label on
'win10Pro.qcow2'. XATTRs might have been left in inconsistent state.
internal error: child reported (status=125): failed to initialize
gluster connection (src=0x7f0b00097030 priv=0x7f0b000956c0): Invalid
argument
Any ideas & suggestions greatly appreciated.
thanks, L.
Hey, since this is gluster I wonder if it is related to this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1786301
That one is a deadlock scenario, but nevertheless might be worth turning
off seclabel remembering to see if that's the root cause. Just set
remember_owner=0 in /etc/libvirt/qemu.conf, restart libvirtd and see if
the problem persists.
Michal
This error is, well, in my opinion quite misleading, as the
problem turns out was - a non-existent GlusterFS Vol to
which storage path pointed to in my guest/domain definition.
Whether there were any other underlying problems I cannot
say, don't know, but if you guys get those or similar to
aforementioned errors, then I suggest check that 'obvious' bit.
many thanks, L.
