-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
False
-
-
False
-
CLOSED
-
---
-
---
-
CNV Virtualization Sprint 223, CNV Virtualization Sprint 224, CNV Virtualization Sprint 225, CNV Virtualization Sprint 226
-
Critical
-
None
+++ This bug was initially created as a clone of Bug #2115371 +++
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.
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:
— Additional comment from Kedar Bidarkar on 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.
— Additional comment from Kedar Bidarkar on 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
- blocks
-
CNV-21186 [2125985] Unable to start windows VMs on PSI setups
-
- Closed
-
- is blocked by
-
CNV-20315 [2115371] Unable to start windows VMs on PSI setups
-
- Closed
-
- is duplicated by
-
CNV-21186 [2125985] Unable to start windows VMs on PSI setups
-
- Closed
-
- external trackers
- links to