Bug 2115371

Summary: Unable to start windows VMs on PSI setups
Product: Container Native Virtualization (CNV) Reporter: Kedar Bidarkar <kbidarka>
Component: VirtualizationAssignee: Itamar Holder <iholder>
Status: CLOSED ERRATA QA Contact: Denys Shchedrivyi <dshchedr>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.11.0CC: acardace, cnv-qe-bugs, dholler, dshchedr, sgott, yadu
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.11.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hco-bundle-registry-container-v4.11.1-17 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2119069 (view as bug list) Environment:
Last Closed: 2022-12-01 21:12:19 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:
Bug Depends On:    
Bug Blocks: 2119069, 2122552, 2125985    

Description Kedar Bidarkar 2022-08-04 14:24:25 UTC
Description of problem:
Unable to start Windows VMs on PSI setups.


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

How reproducible:
On PSI Setups.

Steps to Reproduce:
1. Create any windows VMs on PSI Setups
2.
3.

Actual results:
Windows VMs on PSI Setups, fail to start with the below message.

{"component":"virt-controller","level":"info","msg":"reenqueuing VirtualMachineInstance default/vm-win10-411new","pos":"vmi.go:272","reason":"failed to determine the lowest tsc frequency on the cluster: no schedulable node exposes a tsc-frequency","timestamp":"2022-08-04T11:48:10.942248Z"}


As we don't see any tsc frequency label on worker nodes of PSI Clusters.

Expected results:
Windows VMs on PSI Setups work fine.

Additional info:

Comment 1 Kedar Bidarkar 2022-08-08 14:17:27 UTC
Moving this to 4.11.1 till we have a solution, where in we are not required to skip these tests in PSI Setups.

Comment 2 Kedar Bidarkar 2022-08-08 16:11:49 UTC
This issue is seen because the tsc labels are not present on the PSI Clusters ( Virtual Machine based worker nodes) Worker Nodes.
cpu-timer.node.kubevirt.io/tsc-frequency=2095077000
cpu-timer.node.kubevirt.io/tsc-scalable=true

Comment 3 Denys Shchedrivyi 2022-09-30 20:47:22 UTC
I verified it on v4.11.1-20 - Windows succesfully started on PSI:

> $ oc get vm
> NAME                       AGE   STATUS    READY
> win-10-1664569276-268539   16m   Running   True
>
> $ oc get pod
> NAME                                           READY   STATUS    RESTARTS   AGE
> virt-launcher-win-10-1664569276-268539-kr7ht   1/1     Running   0          18m


But it is not migratable:

> $ virtctl migrate win-10-1664569276-268539
>Er ror migrating VirtualMachine Internal error occurred: admission webhook "migration-create-validator.kubevirt.io" denied the request: Cannot migrate VMI, Reason: NoTSCFrequencyNotLiveMigratable, Message: HyperV Reenlightenment VMIs cannot migrate when TSC Frequency is not exposed on the cluster: guest timers might be inconsistent

If I understand correctly - it is expected that this VM is not migratable, but in our automation we have several tests with migrating Windows VM, so we still can't run some tests on PSI cluster without workaround (removing hyperv.reenlightenment from the VM spec)

Comment 4 Antonio Cardace 2022-10-13 15:07:46 UTC
*** Bug 2100629 has been marked as a duplicate of this bug. ***

Comment 5 Denys Shchedrivyi 2022-10-14 19:53:09 UTC
Moving to Verified since it is expected behavior

Comment 13 errata-xmlrpc 2022-12-01 21:12:19 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 (Moderate: OpenShift Virtualization 4.11.1 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:8750