-
Notifications
You must be signed in to change notification settings - Fork 168
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
Abort the managedsave process and check the events #6104
base: master
Are you sure you want to change the base?
Conversation
Check after aborting the managesave process, the vm should keep running and there is related events. Signed-off-by: Yalan Zhang <[email protected]>
(1/1) type_specific.io-github-autotest-libvirt.save_and_restore.abort_managedsave: PASS (52.58 s) |
import logging | ||
import re | ||
import os |
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.
This should be in order alpha
from virttest.libvirt_xml import vm_xml | ||
from provider.save import save_base |
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.
Need a blank between this two lines
LOG.debug(f'Step1: run stress on the vm:') | ||
sh_cmd1 = "dnf install -y stress" | ||
session.cmd(sh_cmd1, ignore_all_errors=True) | ||
sh_cmd2 = "stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --vm-keep" |
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.
sh_cmd2 = "stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --vm-keep"
Could this stress cmd be in cfg file, it would be more easier to find when we want to increase or reduce stress
Check after aborting the managesave process, the vm should keep running and there is related events.