Dear, I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0." I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem??? Best Regards
----- Original Message -----
From: "Miguel Angel Costas" <migacos2002@gmail.com> To: users@ovirt.org Sent: Monday, July 13, 2015 3:00:33 PM Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0."
I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem???
please attach engine + vdsm logs for the time of the failure
Best Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hello oVirt users, I am facing a serious problem regarding my GlusterFS storage and virtual machines that have *bootable* disks on this storage. All my VMs that have GlusterFS disks are occasionally (1-2 times/hour) becoming paused with the following Error: VM vm02.mytld has been paused due to unknown storage error. Engine Log INFO [org.ovirt.engine.core.vdsbroker.VmAnalyzer] (DefaultQuartzScheduler_Worker-69) [] VM '247bb0f3-1a77-44e4-a404-3271eaee94be'(vm02.mytld) moved from 'Up' --> 'Paused' INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused. ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused due to unknown storage error My iSCSI VM's, some of which may have mounted (not bootable) disks from the same GlusterFS storage, do NOT suffer from this issue AFAIK. My installation (oVirt 3.6/CentOS 7) is pretty much a typical one, with a GlusterFS enabled cluster with 4 hosts, 2-3 networks, and 6-7 VMs.. Thanks, K.
Hi again Konstantinos. Can you please attach the full VDSM & Engine logs so we can understand the reason for your problem? Thanks. ----- Original Message ----- From: "Konstantinos Christidis" <kochrist@ekt.gr> To: users@ovirt.org Sent: Thursday, July 16, 2015 11:29:26 AM Subject: [ovirt-users] VM has been paused due to unknown storage error Hello oVirt users, I am facing a serious problem regarding my GlusterFS storage and virtual machines that have *bootable* disks on this storage. All my VMs that have GlusterFS disks are occasionally (1-2 times/hour) becoming paused with the following Error: VM vm02.mytld has been paused due to unknown storage error. Engine Log INFO [org.ovirt.engine.core.vdsbroker.VmAnalyzer] (DefaultQuartzScheduler_Worker-69) [] VM '247bb0f3-1a77-44e4-a404-3271eaee94be'(vm02.mytld) moved from 'Up' --> 'Paused' INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused. ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused due to unknown storage error My iSCSI VM's, some of which may have mounted (not bootable) disks from the same GlusterFS storage, do NOT suffer from this issue AFAIK. My installation (oVirt 3.6/CentOS 7) is pretty much a typical one, with a GlusterFS enabled cluster with 4 hosts, 2-3 networks, and 6-7 VMs.. Thanks, K. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Check your vdsm Logs on your nodes. I bet you find something about I/O errors i guess... Also check your glusterfs logs. Maybe you can find some problems, too. Mario Am 16.07.15 um 10:29 schrieb Konstantinos Christidis:
Hello oVirt users,
I am facing a serious problem regarding my GlusterFS storage and virtual machines that have *bootable* disks on this storage.
All my VMs that have GlusterFS disks are occasionally (1-2 times/hour) becoming paused with the following Error: VM vm02.mytld has been paused due to unknown storage error.
Engine Log INFO [org.ovirt.engine.core.vdsbroker.VmAnalyzer] (DefaultQuartzScheduler_Worker-69) [] VM '247bb0f3-1a77-44e4-a404-3271eaee94be'(vm02.mytld) moved from 'Up' --> 'Paused' INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused. ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused due to unknown storage error
My iSCSI VM's, some of which may have mounted (not bootable) disks from the same GlusterFS storage, do NOT suffer from this issue AFAIK.
My installation (oVirt 3.6/CentOS 7) is pretty much a typical one, with a GlusterFS enabled cluster with 4 hosts, 2-3 networks, and 6-7 VMs..
Thanks,
K. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Check your vdsm Logs on your nodes. I bet you find something about I/O errors i guess... Yes there are many IO errors
Hello Mario, On 16/07/2015 04:12 μμ, ml@ohnewald.net wrote: libvirtEventLoop::INFO::2015-07-16 22:30:02,237::vm::3609::virt.vm::(onIOError) vmId=`bb46929c-0b4e-4f01-868a-7e7638fa943b`::abnormal vm stop device virtio-disk0 error eother libvirtEventLoop::INFO::2015-07-16 22:30:02,237::vm::4889::virt.vm::(_logGuestCpuStatus) vmId=`bb46929c-0b4e-4f01-868a-7e7638fa943b`::CPU stopped: onIOError Full vdsm log - https://paste.fedoraproject.org/245148/43707759/ and glusterfs errors W [MSGID: 114031] [client-rpc-fops.c:2973:client3_3_lookup_cbk] 0-distributed_vol-client-0: remote operation failed: Transport endpoint is not connected. Path: / (00000000-0000-0000-0000-000000000001) [Transport endpoint is not connected] W [fuse-bridge.c:2273:fuse_writev_cbk] 0-glusterfs-fuse: 362694: WRITE => -1 (Transport endpoint is not connected) K.
Also check your glusterfs logs. Maybe you can find some problems, too.
Mario
Am 16.07.15 um 10:29 schrieb Konstantinos Christidis:
Hello oVirt users,
I am facing a serious problem regarding my GlusterFS storage and virtual machines that have *bootable* disks on this storage.
All my VMs that have GlusterFS disks are occasionally (1-2 times/hour) becoming paused with the following Error: VM vm02.mytld has been paused due to unknown storage error.
Engine Log INFO [org.ovirt.engine.core.vdsbroker.VmAnalyzer] (DefaultQuartzScheduler_Worker-69) [] VM '247bb0f3-1a77-44e4-a404-3271eaee94be'(vm02.mytld) moved from 'Up' --> 'Paused' INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused. ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-69) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm02.mytld has been paused due to unknown storage error
My iSCSI VM's, some of which may have mounted (not bootable) disks from the same GlusterFS storage, do NOT suffer from this issue AFAIK.
My installation (oVirt 3.6/CentOS 7) is pretty much a typical one, with a GlusterFS enabled cluster with 4 hosts, 2-3 networks, and 6-7 VMs..
Thanks,
K. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Omer, I have reinstalled the Server (Centos 6.6) + Ovirt Manager (oVirt Engine Version: 3.5.3.1-1.el6) with 2 Nodes (oVirt Node - 3.0.4 - 1.0.201401291204.el6) and working perfect. At this moment the DataCenter is configured with compatibility version 3.4. The problem appears when upgrade one of the Node to the lastest version. with the package "ovirt-node-iso.noarch 0:3.5-0.999.201504280933.el6".. [image: Imágenes integradas 1] The log files are attached. Thanks you very much for help me!!! Best regards 2015-07-16 4:01 GMT-03:00 Omer Frenkel <ofrenkel@redhat.com>:
----- Original Message -----
From: "Miguel Angel Costas" <migacos2002@gmail.com> To: users@ovirt.org Sent: Monday, July 13, 2015 3:00:33 PM Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0."
I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem???
please attach engine + vdsm logs for the time of the failure
Best Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Jul 17, 2015, at 21:47 , Miguel Angel Costas <migacos2002@gmail.com> wrote:
Hi Omer,
I have reinstalled the Server (Centos 6.6) + Ovirt Manager (oVirt Engine Version: 3.5.3.1-1.el6) with 2 Nodes (oVirt Node - 3.0.4 - 1.0.201401291204.el6) and working perfect. At this moment the DataCenter is configured with compatibility version 3.4.
The problem appears when upgrade one of the Node to the lastest version. with the package "ovirt-node-iso.noarch 0:3.5-0.999.201504280933.el6"..
<image.png>
The log files are attached.
Thanks you very much for help me!!!
Best regards
2015-07-16 4:01 GMT-03:00 Omer Frenkel <ofrenkel@redhat.com>:
----- Original Message -----
From: "Miguel Angel Costas" <migacos2002@gmail.com> To: users@ovirt.org Sent: Monday, July 13, 2015 3:00:33 PM Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0."
it failed within libvirt. We would need to see qemu and libvirt logs too /var/log/libvirt/qemu/<VM>.log /var/log/libvirt/libvirt.log (or something like that:) Thanks, michal
I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem???
please attach engine + vdsm logs for the time of the failure
Best Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
<logs.tar.gz>_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Michal, I have attached the log files from the 2 Nodes. I found other differents after upgrade the NODE. UPGRADED [root@NAHVOVH02 libvirt]# ps -Ze | grep libv system_u:system_*r:ovirt_t:*s0 13807 ? 00:26:41 libvirtd IT's WORKING [root@NAHVOVH01 libvirt]# ps -Ze | grep libvir system_u:system_r:*virtd_t*:s0-s0:c0.c1023 32704 ? 00:18:41 libvirtd Thank you for help!! 2015-07-20 6:18 GMT-03:00 Michal Skrivanek <michal.skrivanek@redhat.com>:
On Jul 17, 2015, at 21:47 , Miguel Angel Costas <migacos2002@gmail.com> wrote:
Hi Omer,
I have reinstalled the Server (Centos 6.6) + Ovirt Manager (oVirt Engine Version: 3.5.3.1-1.el6) with 2 Nodes (oVirt Node - 3.0.4 - 1.0.201401291204.el6) and working perfect. At this moment the DataCenter is configured with compatibility version 3.4.
The problem appears when upgrade one of the Node to the lastest version. with the package "ovirt-node-iso.noarch 0:3.5-0.999.201504280933.el6"..
<image.png>
The log files are attached.
Thanks you very much for help me!!!
Best regards
2015-07-16 4:01 GMT-03:00 Omer Frenkel <ofrenkel@redhat.com>:
----- Original Message -----
From: "Miguel Angel Costas" <migacos2002@gmail.com> To: users@ovirt.org Sent: Monday, July 13, 2015 3:00:33 PM Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0."
it failed within libvirt. We would need to see qemu and libvirt logs too /var/log/libvirt/qemu/<VM>.log /var/log/libvirt/libvirt.log (or something like that:)
Thanks, michal
I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem???
please attach engine + vdsm logs for the time of the failure
Best Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
<logs.tar.gz>_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi guys, I have reinstalled the node with the ISO (ovirt-node-iso-3.5-0.999.201504280933.el6.iso) downloaded instead upgrade from the Ovirt-Engine manager console and It solved the problem. I saw selinux context of libvirtd is different now. [root@NAHVOVH02 ~]# ps -Ze | grep libvirt unconfined_u:system_r:virtd_t:s0-s0:c0.c1023 26864 ? 00:00:16 libvirtd do you know if it should be defined like a bug? Thanks for your help!! 2015-07-20 7:27 GMT-03:00 Miguel Angel Costas <migacos2002@gmail.com>:
Hi Michal,
I have attached the log files from the 2 Nodes. I found other differents after upgrade the NODE.
UPGRADED [root@NAHVOVH02 libvirt]# ps -Ze | grep libv system_u:system_*r:ovirt_t:*s0 13807 ? 00:26:41 libvirtd
IT's WORKING [root@NAHVOVH01 libvirt]# ps -Ze | grep libvir system_u:system_r:*virtd_t*:s0-s0:c0.c1023 32704 ? 00:18:41 libvirtd
Thank you for help!!
2015-07-20 6:18 GMT-03:00 Michal Skrivanek <michal.skrivanek@redhat.com>:
On Jul 17, 2015, at 21:47 , Miguel Angel Costas <migacos2002@gmail.com> wrote:
Hi Omer,
I have reinstalled the Server (Centos 6.6) + Ovirt Manager (oVirt Engine Version: 3.5.3.1-1.el6) with 2 Nodes (oVirt Node - 3.0.4 - 1.0.201401291204.el6) and working perfect. At this moment the DataCenter is configured with compatibility version 3.4.
The problem appears when upgrade one of the Node to the lastest version. with the package "ovirt-node-iso.noarch 0:3.5-0.999.201504280933.el6"..
<image.png>
The log files are attached.
Thanks you very much for help me!!!
Best regards
2015-07-16 4:01 GMT-03:00 Omer Frenkel <ofrenkel@redhat.com>:
----- Original Message -----
From: "Miguel Angel Costas" <migacos2002@gmail.com> To: users@ovirt.org Sent: Monday, July 13, 2015 3:00:33 PM Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0."
it failed within libvirt. We would need to see qemu and libvirt logs too /var/log/libvirt/qemu/<VM>.log /var/log/libvirt/libvirt.log (or something like that:)
Thanks, michal
I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem???
please attach engine + vdsm logs for the time of the failure
Best Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
<logs.tar.gz>_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Jul 23, 2015, at 15:01 , Miguel Angel Costas <migacos2002@gmail.com> wrote:
Hi guys,
I have reinstalled the node with the ISO (ovirt-node-iso-3.5-0.999.201504280933.el6.iso) downloaded instead upgrade from the Ovirt-Engine manager console and It solved the problem.
I saw selinux context of libvirtd is different now.
it does look like a bug in setting selinux context during upgrade Fabian would know if that is already a known problem or not…can you take a look at the thread, please? Thanks, michal
[root@NAHVOVH02 ~]# ps -Ze | grep libvirt unconfined_u:system_r:virtd_t:s0-s0:c0.c1023 26864 ? 00:00:16 libvirtd
do you know if it should be defined like a bug?
Thanks for your help!!
2015-07-20 7:27 GMT-03:00 Miguel Angel Costas <migacos2002@gmail.com>: Hi Michal,
I have attached the log files from the 2 Nodes. I found other differents after upgrade the NODE.
UPGRADED [root@NAHVOVH02 libvirt]# ps -Ze | grep libv system_u:system_r:ovirt_t:s0 13807 ? 00:26:41 libvirtd
IT's WORKING [root@NAHVOVH01 libvirt]# ps -Ze | grep libvir system_u:system_r:virtd_t:s0-s0:c0.c1023 32704 ? 00:18:41 libvirtd
Thank you for help!!
2015-07-20 6:18 GMT-03:00 Michal Skrivanek <michal.skrivanek@redhat.com>:
On Jul 17, 2015, at 21:47 , Miguel Angel Costas <migacos2002@gmail.com> wrote:
Hi Omer,
I have reinstalled the Server (Centos 6.6) + Ovirt Manager (oVirt Engine Version: 3.5.3.1-1.el6) with 2 Nodes (oVirt Node - 3.0.4 - 1.0.201401291204.el6) and working perfect. At this moment the DataCenter is configured with compatibility version 3.4.
The problem appears when upgrade one of the Node to the lastest version. with the package "ovirt-node-iso.noarch 0:3.5-0.999.201504280933.el6"..
<image.png>
The log files are attached.
Thanks you very much for help me!!!
Best regards
2015-07-16 4:01 GMT-03:00 Omer Frenkel <ofrenkel@redhat.com>:
----- Original Message -----
From: "Miguel Angel Costas" <migacos2002@gmail.com> To: users@ovirt.org Sent: Monday, July 13, 2015 3:00:33 PM Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I want to start a VM appear this message "VM lalala is down with error. Exit message: internal error Cannot parse sensitivity level in s0."
it failed within libvirt. We would need to see qemu and libvirt logs too /var/log/libvirt/qemu/<VM>.log /var/log/libvirt/libvirt.log (or something like that:)
Thanks, michal
I tried to find the error on Internet and Blogs but I can't find the solutions. Could you help me to solve the problem???
please attach engine + vdsm logs for the time of the failure
Best Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
<logs.tar.gz>_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (6)
-
Amit Aviram -
Konstantinos Christidis -
Michal Skrivanek -
Miguel Angel Costas -
ml＠ohnewald.net -
Omer Frenkel