My Oracle Support Banner

OLVM: Guest VM Stuck In "Powering Down" Status with error "Virtual machine destroy error code = 42" (Doc ID 2944392.1)

Last updated on APRIL 26, 2023

Applies to:

Linux OS - Version Oracle Linux 8.5 with Unbreakable Enterprise Kernel [5.4.17] and later
Linux x86-64


Guest VM was stuck in "Powering Down" status while powering down as part of normal application requirement.

Below Error messages seen in engine.log

2023-04-12 09:23:53,706+03 INFO [org.ovirt.engine.core.vdsbroker.DestroyVmVDSCommand] (EE-ManagedThreadFactory-engine-Thread-652069) [5569d467] FINISH, DestroyVmVDSCommand, return: , log id: 1e437db3
2023-04-12 09:23:53,706+03 ERROR [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-652069) [5569d467] Command 'org.ovirt.engine.core.bll.StopVmCommand' failed: EngineException: 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)                      <<<<<<<<<<<<<<<<<<

2023-04-12 09:23:53,719+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-652069) [5569d467] EVENT_ID: USER_FAILED_STOP_VM(56), Failed to power off VM <VM_Name> (Host:<KVM_Hostname>, User: admin@internal-authz). 




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.