Bug 2083135 - VM fails to schedule with vTPM in spec
Summary: VM fails to schedule with vTPM in spec
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.11.0
Assignee: Jed Lejosne
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-09 12:21 UTC by vsibirsk
Modified: 2023-11-13 08:17 UTC (History)
2 users (show)

Fixed In Version: hyperconverged-cluster-operator-v4.11.0-69 virt-handler-v4.11.0-71
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 19:32:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
VMI yaml (5.19 KB, text/plain)
2022-05-09 12:21 UTC, vsibirsk
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 7713 0 None open non-root: use /var/run/kubevirt-private for cache and config files 2022-05-10 09:10:45 UTC
Red Hat Issue Tracker CNV-18038 0 None None None 2023-11-13 08:17:20 UTC

Description vsibirsk 2022-05-09 12:21:54 UTC
Created attachment 1878081 [details]
VMI yaml

Description of problem:
After enabling vTPM feature in VM spec, it fails to schedule

Version-Release number of selected component (if applicable):
HCO image: brew.registry.redhat.io/rh-osbs/iib:228430

How reproducible:
100%

Steps to Reproduce:
1.create a VM with tpm: {} in spec.template.spec.domain.devices
2.start a VM

Actual results:
VMI fails to schedule with error:
message: 'server error. command SyncVMI failed: "LibvirtError(Code=1, Domain=0,
Message=''internal error: Could not run ''/usr/bin/swtpm_setup'' to create
config files. exitstatus: 1;\nError: Could not write to /var/run/swtpm_setup.conf:
No such file or directory\n'')"'

Expected results:
VMI scheduled successfully

Additional info:
attached VMI yaml

Comment 1 Antonio Cardace 2022-05-10 09:32:37 UTC
This bug prevents Windows 11 guests from running in NonRoot mode which is the default mode for CNV 4.11.

Comment 3 vsibirsk 2022-05-23 10:09:26 UTC
Verified with hco-operator v4.11.0-69
After adding tpm: {} in spec.template.spec.domain.devices and starting VM, VM starts and schedules OK

Comment 5 errata-xmlrpc 2022-09-14 19:32:24 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.11.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-2022:6526


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