Bug 2229704

Summary:	[ARM64] VMs stuck in starting state with error "domain configuration does not support video model 'virtio'"
Product:	Container Native Virtualization (CNV)	Reporter:	SATHEESARAN <sasundar>
Component:	Virtualization	Assignee:	Jed Lejosne <jlejosne>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	4.14.0	CC:	acardace, kbidarka, sgott
Target Milestone:	---
Target Release:	4.14.0
Hardware:	aarch64
OS:	Linux
Whiteboard:
Fixed In Version:	v4.14.0.rhel9-1889	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 14:06:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description SATHEESARAN 2023-08-07 11:15:42 UTC

Description of problem:
-----------------------
When creating Virtual Machine(VM) with arm64 cluster, VM fails is stuck in 'starting' state with the error ""domain configuration does not support video model 'virtio'"

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
OCP Version:  4.14.0-ec.4
CNV v4.14.0

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create a VM ( with source from fedora cloud image URL )

Actual results:
---------------
VM is stuck in starting state

Expected results:
-----------------
VM should be running

Comment 4 SATHEESARAN 2023-09-18 10:12:01 UTC

Verified with:
OCP - 4.14.0-rc.1
CNV -  v4.14.0.rhel9-1981

Verified the bug with the following steps:

1. Created a ARM cluster, installed CNV operator and created HyperConverged CR
2. Updated the fedora-server-small template to make use of URL of aarch64 fedora image,
vm.spec.template.spec.domain.machine.type to 'virt', vm.spec.template.spec.domain.features.smm.enabled to 'false',
vm.spec.template.spec.domain.firmware.bootloader.efi.secureBoot to 'false'

3. Create a vm with the above said configuration.

VM was running and no errors were seen.

Checked for qemu packages available with virt-launcher pod.
sh-5.1$ rpm -qa | grep -E "qemu.*gpu"
qemu-kvm-device-display-virtio-gpu-7.2.0-14.el9_2.5.aarch64
qemu-kvm-device-display-virtio-gpu-pci-7.2.0-14.el9_2.5.aarch64

So qemu GPU packages are now available with virt-launcher pod.

With this observation marking this bug as VERIFIED

Comment 6 errata-xmlrpc 2023-11-08 14:06:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6817