On 4/30/25 3:06 PM, Stefano Garzarella wrote:
On Mon, Apr 28, 2025 at 04:48:11PM -0700, Bobby Eshleman wrote:
This commit introduces a new vmtest.sh runner for vsock.
It uses virtme-ng/qemu to run tests in a VM. The tests validate G2H, H2G, and loopback. The testing tools from tools/testing/vsock/ are reused. Currently, only vsock_test is used.
VMCI and hyperv support is automatically built, though not used.
Only tested on x86.
To run:
$ tools/testing/selftests/vsock/vmtest.sh
I tried and it's working, but I have a lot of these messages in the output: dmesg: read kernel buffer failed: Operation not permitted
I'm on Fedora 41:
$ uname -r 6.14.4-200.fc41.x86_64
This sounds like the test tripping on selinux. I think this problem should not be handled by the script itself.
[...]
ERROR: trailing whitespace #174: FILE: tools/testing/selftests/vsock/vmtest.sh:47: +^Ivm_server_host_client^IRun vsock_test in server mode on the VM and in client mode on the host.^I$
WARNING: line length of 104 exceeds 100 columns #174: FILE: tools/testing/selftests/vsock/vmtest.sh:47:
- vm_server_host_client Run vsock_test in server mode on the VM and in client mode on the host.
ERROR: trailing whitespace #175: FILE: tools/testing/selftests/vsock/vmtest.sh:48: +^Ivm_client_host_server^IRun vsock_test in client mode on the VM and in server mode on the host.^I$
WARNING: line length of 104 exceeds 100 columns #175: FILE: tools/testing/selftests/vsock/vmtest.sh:48:
- vm_client_host_server Run vsock_test in client mode on the VM and in server mode on the host.
ERROR: trailing whitespace #176: FILE: tools/testing/selftests/vsock/vmtest.sh:49: +^Ivm_loopback^I^IRun vsock_test using the loopback transport in the VM.^I$
ERROR: trailing whitespace #443: FILE: tools/testing/selftests/vsock/vmtest.sh:316: +IFS="^I$
total: 4 errors, 4 warnings, 0 checks, 382 lines checked
I almost forgot: I think it's better to avoid the special formatting and replies on review for proper updating of the script's help.
Thanks,
Paolo