Skip to content

Conversation

@rbradford
Copy link
Member

Try unplugging and replugging.

Fixes: #1050

@sboeuf sboeuf force-pushed the 2020-05-12-test-unplug-virtio-fs branch 2 times, most recently from 22b05c7 to 24803c4 Compare May 13, 2020 07:32
rbradford added 2 commits May 13, 2020 09:33
Now that virtio-fs has unplug support try unplugging and readding the
virtio-fs device.

Fixes: cloud-hypervisor#1050

Signed-off-by: Rob Bradford <[email protected]>
@sboeuf sboeuf force-pushed the 2020-05-12-test-unplug-virtio-fs branch from 24803c4 to dc5dbbb Compare May 13, 2020 07:33
@sboeuf
Copy link
Member

sboeuf commented May 13, 2020

@rbradford FYI I fixed the integration test by adding a sleep(10) before doing the mount, because you cannot try to mount right after you triggered the new hotplug, you gotta give some time to the guest kernel to detect the hotplug.

@rbradford rbradford merged commit 80aa0a7 into cloud-hypervisor:master May 13, 2020
@rbradford rbradford deleted the 2020-05-12-test-unplug-virtio-fs branch May 26, 2020 13:07
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.

Integration test for virtio-fs PCI unplug

2 participants