| commit | 24bfaae13958b823a4f33b70fca52f086851641f | |
| author | Thomas Huth <thuth@redhat.com> | |
| Mon, 21 Dec 2020 14:34:23 +0000 (21 15:34 +0100) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Tue, 22 Dec 2020 08:23:09 +0000 (22 09:23 +0100) | ||
| tree | 64306c5eb4ec479bbb1c3d7a3160019527216402 | treesnapshot (tar.gz zip) |
| parent | b3834073dad120a7ffddc22fd860acf967b62150 | commitdiff |
tests/acceptance: Add a test with the Fedora 31 kernel and initrd
This initrd contains a virtio-net and a virtio-gpu kernel module,
so we can check that we can set a MAC address for the network device
and whether we can hot-plug and -unplug a virtio-crypto device.
But the most interesting part is maybe that we can also successfully
write some stuff into the emulated framebuffer of the virtio-gpu
device and make sure that we can read back that data from a screenshot.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20201221143423.23607-1-thuth@redhat.com>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Tested-by: Willian Rampazzo <willianr@redhat.com>
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
This initrd contains a virtio-net and a virtio-gpu kernel module,
so we can check that we can set a MAC address for the network device
and whether we can hot-plug and -unplug a virtio-crypto device.
But the most interesting part is maybe that we can also successfully
write some stuff into the emulated framebuffer of the virtio-gpu
device and make sure that we can read back that data from a screenshot.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20201221143423.23607-1-thuth@redhat.com>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Tested-by: Willian Rampazzo <willianr@redhat.com>
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| tests/acceptance/machine_s390_ccw_virtio.py | diffblobblamehistory |