Skip to content
This repository was archived by the owner on Mar 16, 2026. It is now read-only.

also detect qemu.start() failure and avoid double-shutdown#30

Merged
il-steffen merged 1 commit intoIntelLabs:masterfrom
il-steffen:detect_startup_fail
Nov 7, 2022
Merged

also detect qemu.start() failure and avoid double-shutdown#30
il-steffen merged 1 commit intoIntelLabs:masterfrom
il-steffen:detect_startup_fail

Conversation

@il-steffen
Copy link
Copy Markdown
Contributor

This improves on #25 which was not handling errors during qemu.start() phase. In this case, the Worker-00 will typically not create the snapshot, which leads all other Workers to wait forever on snapshot creation.

Fix:

  • on Qemu ABORT event or any other qemu.start() failure, let Worker send ABORT to manager
  • in manager, if no Workers are ready but someone has aborted, exit and kill them all.
  • also, use qemu.async_exit() to avoid duplicate execution of qemu.shutdown()

- raise and detect ABORT during qemu.start(), before first READY
- when first VM aborts and no snapshot is created, nobody gets READY
- if none are ready but someone has aborted, let manager exit
- use qemu.async_exit() to avoid duplicate execution of qemu.shutdown()
@il-steffen il-steffen requested a review from Wenzel November 5, 2022 00:57
@il-steffen il-steffen merged commit 19bf493 into IntelLabs:master Nov 7, 2022
@il-steffen il-steffen deleted the detect_startup_fail branch November 25, 2022 15:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant