Any commands to check the same ? On Apr 28, 2016 5:10 PM, "Michal Skrivanek" <[email protected]> wrote:
> > > On 28 Apr 2016, at 10:03, Budur Nagaraju <[email protected]> wrote: > > > > HI > > > > One of the vm is showing "?" and unable to perform any actions below > are the logs ,let me know is there any ways to bring it back ? > > then it’s probably broken in lower layers. check/add vdsm.log from that > period, but it is likely that libvirt lost control over the qemu process. > You may want to check that particular qemu process if it is alright or .g. > stuck in D state or something else. > Sometimes bouncing libvirtd and vdsm might help > > Thanks, > michal > > > > > > > 2016-04-28 13:31:10,501 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] Failed in DestroyVDS method > > 2016-04-28 13:31:10,502 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] Command > org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand return value > > StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=42, > mMessage=Virtual machine destroy error]] > > 2016-04-28 13:31:10,502 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] HostName = cstkvm1 > > 2016-04-28 13:31:10,503 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] Command > DestroyVDSCommand(HostName = cstkvm1, HostId = > 808e0118-32af-47d0-b9eb-43c34494c292, > vmId=7212cdd2-8171-4882-977e-82b7c95f5e62, force=false, secondsToWait=0, > gracefully=false, reason=) execution failed. Exception: VDSErrorException: > VDSGenericException: VDSErrorException: Failed to DestroyVDS, error = > Virtual machine destroy error, code = 42 > > 2016-04-28 13:31:10,503 INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] FINISH, DestroyVDSCommand, > log id: 5e35dcad > > 2016-04-28 13:31:10,504 ERROR > [org.ovirt.engine.core.vdsbroker.DestroyVmVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] VDS::destroy Failed > destroying vm 7212cdd2-8171-4882-977e-82b7c95f5e62 in vds = > 808e0118-32af-47d0-b9eb-43c34494c292 : cstkvm1, error = > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to DestroyVDS, error = > Virtual machine destroy error, code = 42 > > 2016-04-28 13:31:10,513 INFO > [org.ovirt.engine.core.vdsbroker.DestroyVmVDSCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] FINISH, DestroyVmVDSCommand, > log id: 6ff5ad79 > > 2016-04-28 13:31:10,516 ERROR [org.ovirt.engine.core.bll.StopVmCommand] > (org.ovirt.thread.pool-8-thread-39) [191cb679] Command > org.ovirt.engine.core.bll.StopVmCommand throw Vdc Bll exception. With error > message VdcBLLException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to DestroyVDS, error = > Virtual machine destroy error, code = 42 (Failed with error destroyErr and > code 42) > > 2016-04-28 13:31:10,531 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-8-thread-39) [191cb679] Correlation ID: 191cb679, > Job ID: b8b77109-e559-46b4-be1f-6402e85c0a62, Call Stack: null, Custom > Event ID: -1, Message: Failed to power off VM raghpai-MOSS10 (Host: > cstkvm1, User: admin@internal). > > > > > > > > Thanks, > > Nagaraju > > > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
