test.nix: add a test to forcefully remove a usb blockdevice from the quemu host#182
Draft
test.nix: add a test to forcefully remove a usb blockdevice from the quemu host#182
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now that we have a working graceful attach and detach we can look into a forceful removal of the hardware (due to actual removal, hardware failure or other reasons).
This test does just that, a forceful removal of the blockdevice attached to the QEMU test VM.
There is one blemish in the current TestScript: The udev rule is not automatically being triggered when attaching a blockdevice with QEMU Machine Protocol (QMP). Using a manual
udevadm triggerthe rule does however work and creates the symlink we use to attach the device to usbvfiod.This will at least stay a draft until we handle the clean up of devices properly when we encounter a nusb error.