-
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
vIOMMU: Add a vm lifecycle test #5413
Conversation
iommu_dict = {'model': 'smmuv3'} | ||
variants: | ||
- e1000e: | ||
no smmuv3 |
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.
only x86 for e1000e?
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.
yes, updated.
This PR adds: VIRT-294807 - [vIOMMU] Lifecycle test for vm with iommu device Signed-off-by: Yingshun Cui <[email protected]>
I will update test result on arm. |
The first time run with libvirt-10.0.0 on ARM:
Then rerun the failed cases one by one:
So I guess this is due to the PF is not back to the host in short time. Could you double check and add codes to make it stabler? |
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.
See my above comment
@dzhengfy I can't reproduce the problem you mentioned and all the above cases passed in the machine you provided. I'm not sure if it's an environment issue or a random issue, no clue for now. And there is no actions related to PF status change in this test, so can we keep it mind and check if it happens again in the further?
|
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
This PR adds:
VIRT-294807 - [vIOMMU] Lifecycle test for vm with iommu device
Test results: some cases are failed due to known issues.