libvirt_vcpu_plug_unplug: add kdump test after vCPU hotplug/unplug! - #34
Open
Anushree-Mathur wants to merge 1 commit into
Open
libvirt_vcpu_plug_unplug: add kdump test after vCPU hotplug/unplug!#34Anushree-Mathur wants to merge 1 commit into
Anushree-Mathur wants to merge 1 commit into
Conversation
Test that the guest kernel survives a live vCPU count change by triggering kdump immediately after hotplug and after unplug, then verifying a new vmcore is generated and the guest recovers. libvirt/tests/cfg/libvirt_vcpu_plug_unplug.cfg: Add kdump_after_plug_unplug variant inside positive_test.vcpu_set as a peer of with_maxvcpu, restricted to live + ppc64le/ppc64. Three sub-variants: - hotplug_kdump: plug 4→8 vCPUs, trigger kdump, verify vmcore - unplug_kdump: unplug 8→4 vCPUs, trigger kdump, verify vmcore - plug_and_unplug_kdump: both in sequence on_crash=restart so the guest reboots after kdump capture and the test can log back in to verify the new vmcore. libvirt/tests/src/libvirt_vcpu_plug_unplug.py: Import utils_kdump and read kdump_after_plug_unplug/crash_dir params. After successful hotplug and after successful unplug, call utils_kdump.trigger_crash() with an explicit session (timeout=240) and wait_time=120. Guard the uptime reboot check with 'if not kdump_after_plug_unplug' since kdump intentionally reboots the guest. All existing non-kdump variants are unaffected. Signed-off-by: Anushree-Mathur <anushree.mathur@linux.ibm.com> Signed-off-by: Anushree-Mathur <anushree.mathur@linux.ibm.com>
Author
|
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
1 participant
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.
Test that the guest kernel survives a live vCPU count change by
triggering kdump immediately after hotplug and after unplug, then
verifying a new vmcore is generated and the guest recovers.
libvirt/tests/cfg/libvirt_vcpu_plug_unplug.cfg:
Add kdump_after_plug_unplug variant inside positive_test.vcpu_set
as a peer of with_maxvcpu, restricted to live + ppc64le/ppc64.
Three sub-variants:
on_crash=restart so the guest reboots after kdump capture and the
test can log back in to verify the new vmcore.
libvirt/tests/src/libvirt_vcpu_plug_unplug.py:
Import utils_kdump and read kdump_after_plug_unplug/crash_dir params.
After successful hotplug and after successful unplug, call
utils_kdump.trigger_crash() with an explicit session (timeout=240)
and wait_time=120.
Guard the uptime reboot check with 'if not kdump_after_plug_unplug'
since kdump intentionally reboots the guest.
All existing non-kdump variants are unaffected.
Signed-off-by: Anushree-Mathur anushree.mathur@linux.ibm.com