On 05/15/2013 05:41 PM, Mars gu wrote:
Thanks for your help, Wu.
But the problem is still existing. And the my san-lock service is
running.
OK, it seems my suggestions are not very helpful. Sorry for that.
Would you like to open a bug for it?
And then you could upload the log messages of vdsm
On Wed, May 15, 2013 at 02:00:43PM +0800, Mars gu wrote:
hi all，
my Engine version is 3.1.2. and my Vdsm version is 4.10.3-10.
I created a VM and tried to run it, then some error occoured, the error
log is below:
Exit message: internal error unsupported configuration:
hi all，
my Engine version is 3.1.2. and my Vdsm version is 4.10.3-10.
I created a VM and tried to run it, then some error occoured, the error
log is below:
Exit message: internal error unsupported configuration: Read/write,
exclusive access, disks were present, but no
On 05/15/2013 02:00 PM, Mars gu wrote:
hi all，
my Engine version is 3.1.2. and my Vdsm version is 4.10.3-10.
I created a VM and tried to run it, then some error occoured, the
error log is below:
/ Exit message: internal error unsupported configuration: Read/write,
exclusive
On 05/15/2013 04:05 PM, Mars gu wrote:
hi Wu,
the information you need is below:
[root@localhost selinux]# sestatus
SELinux status: enabled
SELinuxfs mount:/selinux
Current mode: enforcing
Mode from config file: enforcing
Policy
Thanks for your help, Wu.
But the problem is still existing. And the my san-lock service is running.
ps: My vdsm is installed in ovirt-node-2.6.1 which use upstart to control
libvirtd.
At 2013-05-15 17:02:38,Mark Wu wu...@linux.vnet.ibm.com wrote:
On 05/15/2013 04:05 PM, Mars gu wrote:
