On 07/20/2012 10:20 AM, xuejie chen wrote:
> 2012/7/17 Martin Kletzander :
>> On 07/17/2012 02:41 AM, Mark Wu wrote:
>>> On 07/16/2012 09:46 AM, xuejie chen wrote:
>>> file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/
2012/7/17 Martin Kletzander :
> On 07/17/2012 02:41 AM, Mark Wu wrote:
>> On 07/16/2012 09:46 AM, xuejie chen wrote:
>>> >> file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259
>> Please up
On 07/17/2012 08:54 PM, Mark Wu wrote:
On 07/17/2012 06:41 PM, Romain LE DISEZ wrote:
nodes fixed it for me:
I am not sure how you met this problem. In previous versions, the
boolean 'virt_use_nfs' was set on first running of vdsmd after
installation or reconfigure.
In lastest vdsm, it's en
On 07/17/2012 06:41 PM, Romain LE DISEZ wrote:
nodes fixed it for me:
I am not sure how you met this problem. In previous versions, the
boolean 'virt_use_nfs' was set on first running of vdsmd after
installation or reconfigure.
In lastest vdsm, it's enabled on vdsm installation automatically
Hi all,
I had a similar problem. I'm using the RPM for CentOS at dreyou.org.
I found that SELinux denies access to the ISO on NFS to libvirt/qemu.
Using audit2allow, I found that there is a boolean for that.
Running this command on the nodes fixed it for me:
setsebool virt_use_nfs 1
Greetin
On 07/17/2012 02:41 AM, Mark Wu wrote:
> On 07/16/2012 09:46 AM, xuejie chen wrote:
>> > 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 suggeste
On 07/16/2012 09:46 AM, xuejie chen wrote:
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-9ca5a37b6
> Would you be kind to try out our release candidate vdsn-4.10.0 ?
> I suspect that 4.9.6 has multiple already-solved issues such as
> requiring libvirt >= 0.9.10-20.
I reinstalled the vdsm(4.9.6) in CentOS 6.,
The problem of "pty failed" disappeared.
But another problem appeared.
I create a DC an
On Wed, Jul 11, 2012 at 05:23:18PM +0800, xuejie chen wrote:
> Hi everyone,
>
> I installed the vdsm(4.9.6) in CentOS 6,
Would you be kind to try out our release candidate vdsn-4.10.0 ?
I suspect that 4.9.6 has multiple already-solved issues such as
requiring libvirt >= 0.9.10-20.
> the libvirt
9 matches
Mail list logo