Repository navigation
Conversation
A one-vCPU guest froze under nested KVM before network setup: PID 1 reported "Failed to fork off sandboxing environment for executing generators: Protocol error" and stopped, with no lease for the whole 360-iteration window. The QEMU guest, which has two vCPUs, booted and migrated in the same run. Signed-off-by: Fabian Wiesel <fabian.wiesel@sap.com>
Contributor
Author
|
Folded into gardenlinux/gardenlinux-sci#413 as a separate commit ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ci: give the Cloud Hypervisor guest two vCPUs
Draft, based on
refactor/integration-hv-prep(d5537ba) and gardenlinux/gardenlinux-sci#413. This pull request changes one line in.github/actions/test/integration/test/cloudhypervisor/vm.xml:<vcpu placement='static'>1</vcpu>becomes<vcpu placement='static'>2</vcpu>.Observed freeze
In push run 43202159294 at
70316d9,Test CloudHypervisorfailed inWait for VM to be ready. The guest console,serial-VM-CHV-HV1.log, reported:PID 1 stopped at guest time 275 s, before network setup. The wait loop printed
No IP address found for VM. Retrying...andWaiting for VM to respond to SSH... (1/360)through(359/360), thenTimeout waiting for VM to respond to SSH.The whole 360-iteration window passed with no lease:virsh -c ch:///session domifaddr VM-CHVreturned no entry, and no ARP entry appeared for the guest MAC52:54:00:00:00:11. The Cloud Hypervisor domain itself started normally.Same-run QEMU control
Test QEMUpassed in the same run. The QEMU guest, which already has two vCPUs and the same 2 GiB of memory, booted and migrated from HyperVisor 1 to HyperVisor 2, ending withDummy file exists on VM, migration successful.The QEMU domain XML uses<vcpu>2</vcpu>.Earlier local observation
An earlier local nested-KVM run of the same one-vCPU Cloud Hypervisor definition showed the same freeze, with PID 1 reporting the same sandboxing fork error before network setup.
Scope
The diff is exactly this one line; no other file changes. No release, key, or readiness claim is made.