Skip to content

test: stop the migrated guest when its scenario ends - #421

Open
fwiesel wants to merge 1 commit into
test/integration-ssh-configfrom
test/integration-guest-teardown
Open

fwiesel wants to merge 1 commit into
test/integration-ssh-configfrom
test/integration-guest-teardown

Conversation

@fwiesel

@fwiesel fwiesel commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

VM-QEMU stayed resident on HV2 after its migration, so the next scenario
started on a saturated host. Each scenario now destroys and undefines its guest
when it ends.

The hypervisor pair uses 2 vCPUs to match the 4-CPU runner, and the shared
dependency action installs virtiofsd and makes /dev/kvm accessible, because
security_driver = "none" stops libvirt from doing it.

The QEMU guest stays resident on HV2, so the Cloud Hypervisor scenario
starts on a saturated host. Destroy and undefine it at the end of the
QEMU stage.

The same hypervisor domains need virtiofsd for their shares and a
reachable /dev/kvm once the libvirt security driver is off. Install both
with the other dependencies, so a later hypervisor test reuses one
install instead of extending the shared action.

Signed-off-by: Fabian Wiesel <fabian.wiesel@sap.com>
@fwiesel
fwiesel force-pushed the test/integration-guest-teardown branch from 4209978 to 57aacdb Compare November 16, 2026 12:30

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant