-
Notifications
You must be signed in to change notification settings - Fork 196
vfio: Extend the current VFIO test for GPU and other devices #5729
base: main
Are you sure you want to change the base?
Conversation
c6d17fe
to
0edd498
Compare
/test-vfio |
/test-vfio |
933bbc1
to
73871b1
Compare
/test-vfio |
/test-vfio |
/test-vfio |
/test-vfio |
/test-vfio |
/test |
Added cold_plug_vfio test besides hot_plug_vfio test. |
/retest-s390x |
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, thanks @zvonkok !
/test |
@GabyCT PTAL Thanks! |
/test-vfio |
@jepio if the config variable is not available it will be not set, updating the sed command ... |
I don't think the sed expression is wrong, I think there is some logic error here:
wouldn't you want this to check against |
@jepio if you look at the config file generated there is no
The cold-plug test-case is started without the |
Need to update the logic, a VFIO test can have both hot-plug and cold-plug set to the same value. One may want to test
first and then
|
So essentially we only need one VFIO_PORT setting since we test hot and cold plug in one run. |
/test-vfio |
Fix default port assignment with an explicit value in the TOML It was implicit before and now the runtime will bail out if we did not set it explicitly. Update the configuration and set it. This will make the intent more clear. Fixes: kata-containers#5726 Signed-off-by: Zvonko Kaiser <[email protected]>
/test-vfio |
Looks like there's an actual bug in handling |
Yep, we need a "simple" runtime fix before merging this. |
cold-plug vfio_mode=guest-kernel works as expected, |
During testing why it fails for |
/test-vfio |
The current VFIO test only works with a virtualized network device.
Extend the VFIO tests so that "any" device that is passed-through can be tested.