diff options
Diffstat (limited to 'results/classifier/108/other/676934')
| -rw-r--r-- | results/classifier/108/other/676934 | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/results/classifier/108/other/676934 b/results/classifier/108/other/676934 new file mode 100644 index 00000000..2c4ad77c --- /dev/null +++ b/results/classifier/108/other/676934 @@ -0,0 +1,33 @@ +network: 0.812 +socket: 0.755 +device: 0.684 +graphic: 0.502 +other: 0.501 +semantic: 0.455 +performance: 0.319 +PID: 0.308 +boot: 0.300 +permissions: 0.293 +vnc: 0.242 +debug: 0.198 +files: 0.085 +KVM: 0.056 + +Ability to use -net socket with unix sockets + +It would be a nice feature (simplifying access control for example) to be able to do something like: + +qemu -net socket,listen=unix:/tmp/qemunet +qemu -net socket,connect=unix:/tmp/qemunet + +For now one has to use TCP connections even for guests running on the same host, which involves setting up iptables to restrict access. + +Aren't these at different levels of the stack? Network devices deal in packets not connections. It sounds like you want to use something like vsock which provides a virtual socket device to the guest. + +This is just about connecting the NIC backends for 2 QEMUs together using a UNIX socket, instead of the current TCP/UDP socket. It should be fairly trivial to support i would expect. Though ideally we'd port the netdev socket backend to use QIOChannel too + + +This is an automated cleanup. This bug report got closed because it +is a duplicate. + + |