Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-55614

[4.17.3] VMCP for Windows VMs has "preferredTPM: persistent: true" preventing VM from starting if VM does not have TPM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • CNV v4.20.0
    • None
    • CNV Infrastructure
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • ---
    • ---
    • None

      Description of problem:

      VMCP for the following OS types has "preferredTPM: persistent: true":
~~~
windows.11
windows.11.virtio
windows.2k22 
windows.2k22.virtio 
windows.2k25 
windows.2k25.virtio
~~~

With this being set in the VMCP, VMs that do not have a TPM configured (nor secure boot) will fail to start. A 10mb pvc is created.

This causes further issues if a CU is migrating from VMWare to CNV, as the migration will fail.

      Version-Release number of selected component (if applicable):

      4.17.3

      How reproducible:

      Create a Windows 11, 22, 25 VM without a TPM device (ex in VMWare) and migrate the VM to Openshift. The migration will complete, but when trying to start the VM, it will fail to start due to the "phantom" TPM device

      Actual results:

      VM fails to start

      Expected results:

      VM should start whether it has TPM configured or not

      Additional info:

      This is

      very 

      similar to JIRA issue: https://issues.redhat.com/browse/CNV-54727

The workaround for both is the same, create a VMP for the OS in the namespace of the VM, removing the "preferredTPM: persistent: true" section. After doing so, the VM will start.

              dholler@redhat.com Dominik Holler
              rhn-support-rknipp Robert Knipp
              Geetika Kapoor Geetika Kapoor
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: