-
Notifications
You must be signed in to change notification settings - Fork 60
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I run a Build Cloud and Vagrant Images workflow in my fork https://github.com/adelton/almalinux-cloud-images/actions/runs/22015099373, unchecking the Allow self-hosted runner (aarch64 or vagrant_vmware only) option to make sure only the GitHub hosted runners are used.
I observed the 10-v2 gencloud-x86_64 image job to fail in the Check nested virtualization support step with
[Debug] vmx|svm CPU flags:
8
[Debug] KVM modules:
kvm_intel 479232 0
kvm 1392640 1 kvm_intel
irqbypass 12288 1 kvm
[Debug] Nested virtualization support:
cat: /sys/module/kvm_amd/parameters/nested: No such file or directory
Expected Behavior
I would expect the build to pass even on a runner with kvm_intel instead of kvm_amd.
Steps To Reproduce
- Fork the https://github.com/AlmaLinux/cloud-images repo.
- In the repo settings, enable Actions.
- In the
Actionstab, select theBuild Cloud and Vagrant Imagesworkflow. - In the blue stripe at the right, select
Run workflow. - Fill in the Custom date+time stamp, change Cloud image type to
gencloud, uncheck theAllow self-hosted runner, checkStore images to the workflow Artifacts, uncheckUpload to S3 Bucket. - Click
Run workflowbutton. - Check the workflow run output, specifically check if it run on a runner which reports the
kvm_intelmodule loaded.
Anything else?
No response
Search terms
ci kvm_intel
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working