[Users] Unable to run VM with ”opening backend ‘pyt’ failed”
Hi everyone, I installed the vdsm(4.9.6) in CentOS 6, the libvirt version is 0.9.4 and the qemu-kvm's version is 0.12.1.2. I create a VM with all default values, But, when I run the vm, it returns failure with the follow error message in WebAdmin. "internal error Process exited while reading console log output: chardev: opening backend "pty" failed. There are logs file in attachment If you want other info, please tell me. Best wishes, Xuejie Chen
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 version is 0.9.4 and the qemu-kvm's version is 0.12.1.2. I create a VM with all default values, But, when I run the vm, it returns failure with the follow error message in WebAdmin. "internal error Process exited while reading console log output: chardev: opening backend "pty" failed.
There are logs file in attachment
If you want other info, please tell me.
Best wishes, Xuejie Chen
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 and the type is "Local on host" I add the host and create a Local storage domain to the DC. I create VM with default values, but I failed to run the vm with follow error message:
error : virNetClientProgramDispatchError:170 : internal error Process exited while reading console log output: char device redirected to /dev/pts/4 qemu-kvm: -drive file=/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259/9c728c1d-762e-4670-9076-9ca5a37b6354,if=none,id=drive-virtio-disk0,format=raw,serial=7e1011e0-d0ac-4c1f-bd09-a19e450c3259,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image /rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259/9c728c1d-762e-4670-9076-9ca5a37b6354: Permission denied Best wishes, Xuejie Chen 2012/7/12 Dan Kenigsberg <danken@redhat.com>:
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 version is 0.9.4 and the qemu-kvm's version is 0.12.1.2. I create a VM with all default values, But, when I run the vm, it returns failure with the follow error message in WebAdmin. "internal error Process exited while reading console log output: chardev: opening backend "pty" failed.
There are logs file in attachment
If you want other info, please tell me.
Best wishes, Xuejie Chen
This is a multi-part message in MIME format. --------------070602040304090703010809 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Thanks! --------------070602040304090703010809 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 07/16/2012 09:46 AM, xuejie chen wrote: <blockquote cite="mid:CA+LNO-7aAUDGyVjpBQjzedd=NNbCMpoeOiFAbmS8gWuWYaYERQ@mail.gmail.com" type="cite"> <pre wrap=""> <source file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259</pre> </blockquote> Please upgrade vdsm to 4.10.0 as Dan suggested above. If the problem still exists, please:<br> <br> check the owner and permission of that image file:<br> <pre wrap="">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<big> Run </big><big>"setenforce 0" </big><big>to disable selinux and see if it helps: Thanks! </big> </pre> </body> </html> --------------070602040304090703010809--
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
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 Greetings. Le mardi 17 juillet 2012 à 09:16 +0200, Martin Kletzander a écrit :
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 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Romain LE DISEZ
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.
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 enabled on vdsm installation automatically.
I have seen that not set for many times. Thanks Robert
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
2012/7/17 Martin Kletzander <mkletzan@redhat.com>:
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).
I checked the owner of that image file is vdsm. But I found the user of qemu-kvm is root. So I modified the qemu.conf and set user to qemu. The problem disappeared. Thanks a lot Xuejie Chen
On 07/20/2012 10:20 AM, xuejie chen wrote:
2012/7/17 Martin Kletzander <mkletzan@redhat.com>:
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).
I checked the owner of that image file is vdsm. But I found the user of qemu-kvm is root. So I modified the qemu.conf and set user to qemu.
This modification shouldn't be necessary as the binary packages are compiled with this setting usually. However, in case you used some yourself-built package, that might have caused the config change (happens to me with compiled packages from repo. Martin
participants (6)
-
Dan Kenigsberg -
Mark Wu -
Martin Kletzander -
Robert Middleswarth -
Romain LE DISEZ -
xuejie chen