By migrating VMs one at a time I noticed that trouble seemed to be following one of them in particular. I powered that VM down and the problem stopped. Unlike all the other VMs this one had the "random number generator enabled" box checked. I removed the setting and started the VM. It took longer than normal to start and the host spit out some kernel errors. But then the VM started and everything now appears to be normal. On Sun, Jan 24, 2016 at 1:43 AM, Fil Di Noto <fdinoto@gmail.com> wrote:
This has been showing up in the logs on a couple of my hosts. When I put the host into maintenance mode the message stops but then appears on another host where the VMs were migrated to. Is this a serious problem? ( and is it caused by hot-adding CPU cores or memory? )
periodic/21::ERROR::2016-01-24 09:34:41,884::executor::188::Executor::(_execute_task) Unhandled exception in <virt.periodic.NumaInfoMonitor object at 0x7efc240c8250> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 186, in _execute_task callable() File "/usr/share/vdsm/virt/periodic.py", line 271, in __call__ self._execute() File "/usr/share/vdsm/virt/periodic.py", line 311, in _execute self._vm.updateNumaInfo() File "/usr/share/vdsm/virt/vm.py", line 5025, in updateNumaInfo self._numaInfo = numaUtils.getVmNumaNodeRuntimeInfo(self) File "/usr/share/vdsm/numaUtils.py", line 116, in getVmNumaNodeRuntimeInfo vnode_index = str(vcpu_to_vnode[vcpu_id]) KeyError: 1