Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

virError(Code=67, Domain=10, Message='unsupported configuration: vcpu '1' is missing hotplug data' #3102

Open
Muyan0828 opened this issue Sep 18, 2024 · 4 comments
Labels
kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Muyan0828
Copy link

Muyan0828 commented Sep 18, 2024

What happened:
vm cannot running on arm64

What you expected to happen:
vm running normal

How to reproduce it (as minimally and precisely as possible):
Steps to reproduce the behavior.

  1. deploy hco on arm64
  2. create a vm

Additional context:
virt-launcher log

2024-09-05 {"component":"virt-launcher","kind":"","level":"error","msg":"Failed to sync vmi","name":"t-lc-aa","namespace":"sy-k","pos":"server.go:202","reason":"virError(Code=67, Domain=10, Message='unsupported configuration: vcpu '1' is missing hotplug data')","timestamp":"2024-09-05T07:15:08.325522Z","uid":"233a5558-361b-4261-abbe-0a46c99ad041"}

vm xml

	<cpu mode="host-passthrough">
		<topology sockets="16" cores="1" threads="1"></topology>
	</cpu>
	<vcpu placement="static">16</vcpu>
	<vcpus>
		<vcpu id="0" enabled="yes" hotpluggable="no"></vcpu>
		<vcpu id="1" enabled="yes" hotpluggable="yes"></vcpu>
		<vcpu id="2" enabled="yes" hotpluggable="yes"></vcpu>
		<vcpu id="3" enabled="yes" hotpluggable="yes"></vcpu>
		<vcpu id="4" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="5" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="6" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="7" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="8" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="9" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="10" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="11" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="12" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="13" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="14" enabled="no" hotpluggable="yes"></vcpu>
		<vcpu id="15" enabled="no" hotpluggable="yes"></vcpu>
	</vcpus>
	<iothreads>1</iothreads>

Environment:

  • KubeVirt version (use virtctl version): 1.3.0
  • Kubernetes version (use kubectl version): v1.28.8
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): Ubuntu 22.04.2 LTS
  • Kernel (e.g. uname -a): 5.15.0-112-generic
  • Install tools: N/A
  • Others: N/A
@Muyan0828
Copy link
Author

I think the root cause is hco enable kvVMLiveUpdateFeatures by default, but kubevirt not support cpu_hotplug on arm64
https://kubevirt.io/user-guide/compute/cpu_hotplug/#limitations

@orenc1
Copy link
Collaborator

orenc1 commented Sep 19, 2024

Hi @Muyan0828 ,
Thanks for reporting the issue 👍 ,
Could you please advise if you're running an homogeneous cluster of only ARM64 nodes? or an heterogeneous cluster with mixed ARM64 and AMD64 nodes?
Also, could you please provide the images you used for the virt-handler and virt-launcher that are running on the ARM node?

thanks

@Muyan0828
Copy link
Author

Muyan0828 commented Sep 25, 2024

Hi @Muyan0828 , Thanks for reporting the issue 👍 , Could you please advise if you're running an homogeneous cluster of only ARM64 nodes? or an heterogeneous cluster with mixed ARM64 and AMD64 nodes? Also, could you please provide the images you used for the virt-handler and virt-launcher that are running on the ARM node?

thanks

cluster wiith mixed ARM64 and AMD64
virt-handle: quay.io/kubevirt/virt-controller:v1.3.0
virt-launcher: quay.io/kubevirt/virt-launcher:v1.3.0

@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants