I tried kernel 3.8.3-201.fc18.x86_64 and get the same problem. I tried kernel 3.6.11-3.fc18.x86_64, the host activated but the storage data domain and iso domain becomes inactive.
I have this errors on engine log: 2013-03-18 11:11:15,287 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand] (DefaultQuartzScheduler_Worker-1) [6ccaf399] XML RPC error in command GlusterVolumesListVDS ( HostName = node2.acloud.pt ), the error was: java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException, <type 'exceptions.ValueError'>:I/O operation on closed file 2013-03-18 11:11:15,290 ERROR [org.ovirt.engine.core.bll.gluster.GlusterManager] (DefaultQuartzScheduler_Worker-1) [6ccaf399] Error while refreshing Gluster lightweight data of cluster Default!: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.ValueError'>:I/O operation on closed file 2013-03-18 11:11:20,360 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand] (DefaultQuartzScheduler_Worker-4) [629f0dd3] XML RPC error in command GlusterVolumesListVDS ( HostName = node2.acloud.pt ), the error was: java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException, <type 'exceptions.ValueError'>:I/O operation on closed file 2013-03-18 11:11:20,362 ERROR [org.ovirt.engine.core.bll.gluster.GlusterManager] (DefaultQuartzScheduler_Worker-4) [629f0dd3] Error while refreshing Gluster lightweight data of cluster Default!: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.ValueError'>:I/O operation on closed file ----- Mensagem original ----- De: "Joop van de Wege" <jvdw...@xs4all.nl> Para: supo...@logicworks.pt Enviadas: Sábado, 16 de Março de 2013 8:06:25 Assunto: Re: [Users] BUG: soft lockup supo...@logicworks.pt schreef: So, there is not a solid solution for this? ----- Mensagem original ----- De: "Joop" <jvdw...@xs4all.nl> Para: supo...@logicworks.pt, Users@ovirt.org Enviadas: Sexta-feira, 15 Março, 2013 21:57:35 Assunto: Re: [Users] BUG: soft lockup supo...@logicworks.pt wrote: I have a host that have this error BUG: soft lockup - CPU#4 stuck for 22s! [sh: 1534], and the host died this host was installed from fedora18 minimum installation, kernel version 3.8.2-206.fc18.x86_64. I have another host with the same configuration, and have no errors, until now. Any idea? Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Just to let you know you're not alone. I ! have a few hosts which have the same problem. F18 minimal install, started at 3.6.x kernel. Every upgrade since has had this. Some reboots! at higher versions work, mostly not. Disabling multipath might help but then vdsm doesn't work. Hosts are HP ML110G5, HP DL360 G6, from memory Joop Sticking to the 3.6 kernel works each and every time. I still try new kernels once in a while but it seems that anything after it isnt stable.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
