My Oracle Support Banner

OLVM: VM Start on a Pinned Host Fails with Warning "Default Host parameter was ignored - assigned Host was not available" (Doc ID 3035536.1)

Last updated on JULY 17, 2024

Applies to:

Linux OS - Version Oracle Linux 8.6 with Unbreakable Enterprise Kernel [5.4.17] and later
Information in this document applies to any platform.

Symptoms

Unable to start any of the VMs on the pinned host. The VMs  always start on one particular host with below warning in engine.log. Even positive enforcing affinity didn't help in this case.

2024-04-23 10:50:50,813+09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [380fbdbe] VM '3faf86e9-797b-4aed-b25f-###############'(TestVM) moved from 'PoweringUp' --> 'Up'
2024-04-23 10:50:50,819+09 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-9) [380fbdbe] EVENT_ID: USER_RUN_VM_ON_NON_DEFAULT_VDS(152), Guest TestVM started on Host test.local. 
(Default Host parameter was ignored - assigned Host was not available).

Able to migrate the VMs to any of the host once it starts on the particular host.

Changes

New installation.

Cause

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
Symptoms
Changes
Cause
Solution


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