blob: fef2d50ea1c82b98acf6a56532050a55b940df75 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
device: 0.785
socket: 0.784
network: 0.679
graphic: 0.648
semantic: 0.637
performance: 0.605
other: 0.554
PID: 0.534
files: 0.502
permissions: 0.444
boot: 0.422
debug: 0.405
vnc: 0.296
KVM: 0.136
Incorrect warnings when using vhost without numa
Description of problem:
Part A: Misleading error message. Running the above command for any architecture fails to initialize vhost, and prints the following, incorrect advice
```
qemu-system-mips: Failed initializing vhost-user memory map, consider using -object memory-backend-file share=on
qemu-system-mips: vhost_set_mem_table failed: Invalid argument (22)
qemu-system-mips: Error starting vhost: 22
```
Since the command line already contains `-object memory-backend-file,id=mem1,mem-path=/tmp/mem,size=256M,share=on` this error message should not be printed. For x86_64, this can be resolved by adding `-numa node,memdev=mem0` to the command line. As such, I think this error message should instead guide a user to adding that argument.
Part B: No documented configuration to run vhost-user for machines that don't support numa.
The mips malta machine does not support the `-numa` flag. It is unclear if this means that `vhost` cannot be used with this platform or if a non-numa configuration with a memory-backend-file can be used.
Steps to reproduce:
1. Run `vhost-user-vsock --socket=/tmp/vhost4.socket --uds-path=/tmp/foo` from https://github.com/rust-vmm/vhost-device.
1. Run the above QEMU command
|