Bug 1854047 - VM with legacy BIOS failed to run under cluster with "Q35 chipset with legacy BIOS"
Summary: VM with legacy BIOS failed to run under cluster with "Q35 chipset with legacy...
Keywords:
Status: CLOSED DUPLICATE of bug 1853909
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.1.7
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-06 08:04 UTC by Nisim Simsolo
Modified: 2020-07-06 09:45 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-07-06 09:45:33 UTC
oVirt Team: Virt
Embargoed:


Attachments (Terms of Use)
vdsm.log (192.87 KB, application/x-xz)
2020-07-06 08:07 UTC, Nisim Simsolo
no flags Details
engine.log (169.22 KB, application/x-xz)
2020-07-06 08:07 UTC, Nisim Simsolo
no flags Details

Description Nisim Simsolo 2020-07-06 08:04:32 UTC
Description of problem:
Trying to run new VM with Legacy BIOS under a cluster with "Q35 chipset with legacy BIOS" failed with the next engine.log:
2020-07-06 10:49:44,671+03 ERROR [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-11589) [4c2467c7-9b87-4484-bc10-998ba0e2a82a] Can't find VDS to run the VM 'f7a51a40-fa82-4569-b6bc-fb95f81e51e5' on, so this VM will not be run.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.1.7-0.3.el8ev
vdsm-4.40.22-1.el8ev.x86_64
qemu-kvm-4.2.0-28.module+el8.2.1+7211+16dfe810.x86_64
libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Browse WebAdmin, create new VM, select default cluster (Cluster BIOS type is: Q35 chipset with legacy BIOS), Select OS type RHEL 8, change BIOS type to "Legacy". click ok button. 
2. Run VM.
3.

Actual results:
VM failed to run

Expected results:
VM should be able to run with legacy BIOS when cluster BIOS type is "Q35 Chipset with Legacy BIOS").

Additional info:
engine.log and vdsm.log attached

Comment 1 Nisim Simsolo 2020-07-06 08:07:33 UTC
Created attachment 1699995 [details]
vdsm.log

Comment 2 Nisim Simsolo 2020-07-06 08:07:56 UTC
Created attachment 1699996 [details]
engine.log

Comment 3 Arik 2020-07-06 09:05:19 UTC
This looks like a duplicate of bz 1853909 -
can you please check if it works on a new cluster?

Comment 4 Nisim Simsolo 2020-07-06 09:34:39 UTC
(In reply to Arik from comment #3)
> This looks like a duplicate of bz 1853909 -
> can you please check if it works on a new cluster?

Same VM configuration on a new cluster (with default BIOS type) is running successfully.

Comment 5 Arik 2020-07-06 09:45:33 UTC

*** This bug has been marked as a duplicate of bug 1853909 ***


Note You need to log in before you can comment on or make changes to this bug.