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 leases specified The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
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 access, disks were present, but no leases specified/ // The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
Could you please provide the following information?
Do you enable selinux on the vdsm host? If yes, then what's the version of selinux-policy? (rpm -qi selinux-policy)
What's your configuration in qemu-sanlock.conf? (egrep -v ^# /etc/libvirt/qemu-sanlock.conf)
What's your libvirt version?
Thanks. Mark.
vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
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 version: 24 Policy from config file: targeted
[root@localhost selinux]# rpm -q selinux-policy selinux-policy-3.7.19-195.el6_4.3.noarch
[root@localhost selinux]# rpm -q libvirt libvirt-0.10.2-18.el6_4.4.x86_64
[root@localhost selinux]# egrep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0
在 2013-05-15 14:55:49,"Mark Wu" wudxw@linux.vnet.ibm.com 写道:
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 access, disks were present, but no leases specified The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
Could you please provide the following information?
Do you enable selinux on the vdsm host? If yes, then what's the version of selinux-policy? (rpm -qi selinux-policy)
What's your configuration in qemu-sanlock.conf? (egrep -v ^# /etc/libvirt/qemu-sanlock.conf)
What's your libvirt version?
Thanks. Mark.
_______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.orghttps://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
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 version: 24 Policy from config file: targeted
[root@localhost selinux]# rpm -q selinux-policy selinux-policy-3.7.19-195.el6_4.3.noarch
already include the fix for the problem I suspected. But I still suggest you try to disable selinux to see if works.
[root@localhost selinux]# rpm -q libvirt libvirt-0.10.2-18.el6_4.4.x86_64
[root@localhost selinux]# egrep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0
libvirt shouldn't report that error with the configuration of 'require_lease_for_disks=0'. So does the problem still exist after you restarting libvirt? And what's the status of sanlock service?
在 2013-05-15 14:55:49,"Mark Wu" wudxw@linux.vnet.ibm.com 写道:
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 access, disks were present, but no leases specified/ // The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
Could you please provide the following information? Do you enable selinux on the vdsm host? If yes, then what's the version of selinux-policy? (rpm -qi selinux-policy) What's your configuration in qemu-sanlock.conf? (egrep -v ^# /etc/libvirt/qemu-sanlock.conf) What's your libvirt version? Thanks. Mark.
_______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
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" wudxw@linux.vnet.ibm.com wrote:
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 version: 24 Policy from config file: targeted
[root@localhost selinux]# rpm -q selinux-policy selinux-policy-3.7.19-195.el6_4.3.noarch already include the fix for the problem I suspected. But I still suggest you try to disable selinux to see if works.
[root@localhost selinux]# rpm -q libvirt libvirt-0.10.2-18.el6_4.4.x86_64
[root@localhost selinux]# egrep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0 libvirt shouldn't report that error with the configuration of 'require_lease_for_disks=0'. So does the problem still exist after you restarting libvirt? And what's the status of sanlock service?
在 2013-05-15 14:55:49,"Mark Wu" wudxw@linux.vnet.ibm.com 写道:
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 access, disks were present, but no leases specified The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
Could you please provide the following information?
Do you enable selinux on the vdsm host? If yes, then what's the version of selinux-policy? (rpm -qi selinux-policy)
What's your configuration in qemu-sanlock.conf? (egrep -v ^# /etc/libvirt/qemu-sanlock.conf)
What's your libvirt version?
Thanks. Mark.
_______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.orghttps://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
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 and libvirtd to it and we can follow up it there.
Mark.
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" wudxw@linux.vnet.ibm.com wrote:
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 version: 24 Policy from config file: targeted [root@localhost selinux]# rpm -q selinux-policy selinux-policy-3.7.19-195.el6_4.3.noarch
already include the fix for the problem I suspected. But I still suggest you try to disable selinux to see if works.
[root@localhost selinux]# rpm -q libvirt libvirt-0.10.2-18.el6_4.4.x86_64 [root@localhost selinux]# egrep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0
libvirt shouldn't report that error with the configuration of 'require_lease_for_disks=0'. So does the problem still exist after you restarting libvirt? And what's the status of sanlock service?
在 2013-05-15 14:55:49,"Mark Wu" <wudxw@linux.vnet.ibm.com> 写道: 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 access, disks were present, but no leases specified/ // The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
Could you please provide the following information? Do you enable selinux on the vdsm host? If yes, then what's the version of selinux-policy? (rpm -qi selinux-policy) What's your configuration in qemu-sanlock.conf? (egrep -v ^# /etc/libvirt/qemu-sanlock.conf) What's your libvirt version? Thanks. Mark.
_______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
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: Read/write, exclusive access, disks were present, but no leases specified The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
Would you share you vdsm.log, from the vmCreate command to the point of error? Federico may be able to fathom that.
Dan.
vdsm-devel@lists.fedorahosted.org