Skip to content

Conversation

@higuoxing
Copy link
Contributor

Sometimes, the QEMU process exits early due to various reasons, e.g., the missing of kernel binary, providing incorrect qemu commandline arguments, ... and vmtest didn't check the exit status of QEMU and it will wait for 5 seconds to detect the error.

This patch teaches vmtest exit earlier when the QEMU process exits unexpectedly.

Sometimes, the QEMU process exits early due to various reasons, e.g.,
the missing of kernel binary, providing incorrect qemu commandline
arguments, ... and vmtest didn't check the exit status of QEMU and it
will wait for 5 seconds to detect the error.

This patch teaches vmtest exit earlier when the QEMU process exits
unexpectedly.
Copy link
Owner

@danobi danobi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@danobi
Copy link
Owner

danobi commented Oct 7, 2025

can you please look into the test failure though?

@higuoxing
Copy link
Contributor Author

can you please look into the test failure though?

Thanks for reviewing this! I pushed a new commit to fix the failed test. The root cause is that, after this change, the error message 'qemu: could not open kernel file ...' appears in the 'Caused by' section. We need to use format("{:?}", err) to get full content of the error message.

@danobi danobi merged commit 074c59e into danobi:master Oct 8, 2025
1 check passed
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.

2 participants