Re: [Users] Unable to run VM with ”opening backend ‘pyt’ failed”
On 07/17/2012 02:41 AM, Mark Wu wrote:
On 07/16/2012 09:46 AM, xuejie chen wrote:
> <source
file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259
Please upgrade vdsm to 4.10.0 as Dan suggested above. If the problem
still exists, please:
check the owner and permission of that image file:
ls -l
/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259/9c728c1d-762e-4670-9076-9ca5a37b6354
Run "setenforce 0" to disable selinux and see if it helps:
As Mark pointed out, checking the permissions should be enough, so
"ls -lZ" will do. I don't know if "Local on host" means exactly
what I
think, but in case it's not managed using vdsm, that directory may need
to me mounted from somewhere, libvirt itself doesn't do that (unless
it's in network filesystem pool).
In case this goes down to a problem in libvirt, feel free to say what's
wrong and I'll see what I can do about it.
Martin