jjOn Wed, Apr 27, 2016 at 2:03 AM, Bill James <bill.ja...@j2.com> wrote:
> I have a hardware node that has 26 VMs.
> 9 are listed as "running", 17 are listed as "paused".
> In truth all VMs are up and running fine.
> I tried telling the db they are up:
> engine=> update vm_dynamic set status = 1 where vm_guid =(select
> vm_guid from vm_static where vm_name = 'api1.test.j2noc.com');
> GUI then shows it up for a short while,
> then puts it back in paused state.
> 2016-04-26 15:16:46,095 INFO [org.ovirt.engine.core.vdsbroker.VmAnalyzer]
> (DefaultQuartzScheduler_Worker-16) [157cc21e] VM '242ca0af-4ab2-4dd6-b515-5
> d435e6452c4'(api1.test.j2noc.com) moved from 'Up' --> 'Paused'
> 2016-04-26 15:16:46,221 INFO [org.ovirt.engine.core.dal.dbbroker.auditlogh
> andling.AuditLogDirector] (DefaultQuartzScheduler_Worker-16) [157cc21e] Cor
> relation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM api1.
> test.j2noc.com has been paused.
> Why does the engine think the VMs are paused?
> Attached engine.log.
> I can fix the problem by powering off the VM then starting it back up.
> But the VM is working fine! How do I get ovirt to realize that?

If this is an issue in engine, restarting engine may fix this.
but having this problem only with one node, I don't think this is the issue.

If this is an issue in vdsm, restarting vdsm may fix this.

If this does not help, maybe this is libvirt issue? did you try to check vm
status using virsh?

If virsh thinks that the vms are paused, you can try to restart libvirtd.

Please file a bug about this in any case with engine and vdsm logs.

Adding Michal in case he has better idea how to proceed.

Users mailing list

Reply via email to