Refactor virtio tests

[andreeaflorescu]

The virtio tests for block and network are using metrics to check for invalid states. The problem with using metrics in unit tests is that it makes it impossible to run the tests in parallel. The network implementation already has a TestMutator which can also be used to add per test counters. The same approach can be used for testing block devices.

For example, instead of checking that the value of METRICS.block.activate_fails is one when activation fails, we could instead define an activate_fails counter in the test mutators, increment it on bad activate and check this value in test.

This should be implemented after the refactoring/epoll_handler branch is merged to master.

[jeffreyxie0615]

Hi! Is this issue still open to be worked on? My partner and I are students from UT Austin, and we were wondering if we could tackle this as a good first issue for our virtualization class?

[roypat]

The virtio block and net tests in particular no longer run into the problem described here since the introduction of per-device metrics. Some other devices, specifically rng and vsock, do still have the issue, but in #4709 we've decided that the way for making those unittests parallelizable is by extending the per-device metrics concept to them. I'm close this ticket because of that