diff options
Diffstat (limited to 'results/classifier/105/network/838974')
| -rw-r--r-- | results/classifier/105/network/838974 | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/results/classifier/105/network/838974 b/results/classifier/105/network/838974 new file mode 100644 index 00000000..6aea305a --- /dev/null +++ b/results/classifier/105/network/838974 @@ -0,0 +1,27 @@ +network: 0.905 +semantic: 0.872 +device: 0.802 +socket: 0.709 +vnc: 0.646 +mistranslation: 0.645 +graphic: 0.645 +instruction: 0.617 +other: 0.614 +KVM: 0.586 +boot: 0.526 +assembly: 0.359 + +Confusing error report for missing vde support + +The error that appears in qemu 0.15 is "parameter 'type' expects a network client type" when trying to use vde for networking as if the parameter is wrong, but the problem is that the executable was compiled without vde support. + +Thanks for reporting this bug. + +That certainly could be confusing. However, practically speaking, since qemu was compiled without that support, it becomes more difficult for qemu to tell the difference between a unsupported but otherwise-valid type, and an invalid type. + +Perhaps upstream would accept a (trivial) patch changing the message to always say "expects a valid network client type". Even more helpful would be for that message to be followed by a list of valid, supported network types. + +I think this has been fixed by this commit here: +https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d139e9a6cf01b8c31f59 +... so closing this ticket now. + |