-
Notifications
You must be signed in to change notification settings - Fork 736
[hyper-v] Move disabling automatic checkpoints to vm creation #4205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[hyper-v] Move disabling automatic checkpoints to vm creation #4205
Conversation
78200a5 to
c71ebcc
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4205 +/- ##
=======================================
Coverage 89.31% 89.31%
=======================================
Files 259 259
Lines 15684 15684
=======================================
Hits 14008 14008
Misses 1676 1676 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Currently, disabling automatic checkpoints causes issues when the VM is not in an appropriate state at the time the constructor is executed. This causes the daemon to crash since the command throws an exception. Fixes: #4204 Signed-off-by: Mustafa Kemal Gilor <mustafa.gilor@canonical.com>
c71ebcc to
eab38fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and works nicely, thanks Mustafa! I have only a minor comment, but we can even do it as a separate PR, so approving this anyway.
| inline static const std::vector<RunSpec> postfix_ctor_runs = {{"Set-VM"}, {"Get-VMCheckpoint"}}; | ||
| {"Set-VMMemory"}, | ||
| {"Set-VM"}}; | ||
| inline static const std::vector<RunSpec> postfix_ctor_runs = {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be able to remove this now, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Currently, disabling automatic checkpoints causes issues when the VM is not in an appropriate state at the time the constructor is executed. This causes the daemon to crash since the command throws an exception. Fixes: #4204 MULTI-2061
…cal#4205) Currently, disabling automatic checkpoints causes issues when the VM is not in an appropriate state at the time the constructor is executed. This causes the daemon to crash since the command throws an exception. Fixes: canonical#4204 MULTI-2061
…cal#4205) Currently, disabling automatic checkpoints causes issues when the VM is not in an appropriate state at the time the constructor is executed. This causes the daemon to crash since the command throws an exception. Fixes: canonical#4204 MULTI-2061
…cal#4205) Currently, disabling automatic checkpoints causes issues when the VM is not in an appropriate state at the time the constructor is executed. This causes the daemon to crash since the command throws an exception. Fixes: canonical#4204 MULTI-2061
Currently, disabling automatic checkpoints causes issues when the VM is not in an appropriate state at the time the constructor is executed. This causes the daemon to crash since the command throws an exception.
Fixes: #4204
MULTI-2061