-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
5
-
False
-
-
False
-
POST
-
---
-
---
-
-
CNV Virtualization Sprint 241, CNV Virtualization Sprint 244, CNV Virtualization Sprint 245, CNV Virtualization Sprint 246, CNV Virtualization Sprint 247
-
Important
-
No
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
Create the following VMI:
```
apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
annotations:
cpu-load-balancing.crio.io: disable
cpu-quota.crio.io: disable
irq-load-balancing.crio.io: disable
name: dpdk-vmi
spec:
domain:
cpu:
cores: 8
dedicatedCpuPlacement: true
isolateEmulatorThread: true
model: host-model
sockets: 1
threads: 1
devices:
disks:
- disk:
bus: virtio
name: rootdisk - disk:
bus: virtio
name: cloudinitdisk
networkInterfaceMultiqueue: true
rng: {}
memory:
guest: 4Gi
hugepages:
pageSize: 1Gi
terminationGracePeriodSeconds: 0
volumes: - containerDisk:
image: 'quay.io/kiagnose/kubevirt-dpdk-checkup-vm:main'
imagePullPolicy: Always
name: rootdisk - cloudInitNoCloud:
userData: |
#cloud-config
user: cloud-user
password: 0tli-pxem-xknu
chpasswd:
expire: false
name: cloudinitdisk
```
Actual results:
virt-launcher pod does not start.
kubelet emits the following event:
```
SMT Alignment Error: requested 9 cpus not multiple cpus per core = 2
```
Expected results:
The VMI should start.
Additional info:
Git Pull Request: https://github.com/kubevirt/hyperconverged-cluster-operator/pull/2695 closed
- blocks
-
CNV-36582 [RT Checkup] Make the CPU count even
-
- Closed
-
- external trackers
- links to
-
RHEA-2023:116760 OpenShift Virtualization 4.15.0 Images
- mentioned on