blob: 224965d390bf96f43da5f7ae68ba0299c316b245 (
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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
network: 0.473
device: 0.375
graphic: 0.334
i386: 0.319
permissions: 0.311
mistranslation: 0.259
kernel: 0.245
semantic: 0.243
files: 0.235
hypervisor: 0.203
performance: 0.199
socket: 0.183
PID: 0.180
boot: 0.145
architecture: 0.139
virtual: 0.123
peripherals: 0.116
ppc: 0.106
register: 0.105
vnc: 0.086
user-level: 0.085
VMM: 0.082
TCG: 0.082
debug: 0.079
arm: 0.078
x86: 0.075
assembly: 0.053
risc-v: 0.045
KVM: 0.045
qemu-bridge-helper undocumented and broken
qemu output:
access denied by acl file
qemu-system-ppc64: bridge helper failed
Option description:
-netdev bridge,id=id[,br=bridge][,helper=helper]
Connect a host TAP network interface to a host bridge device.
Use the network helper helper to configure the TAP interface and attach it to the bridge. The default network
helper executable is /path/to/qemu-bridge-helper and the default bridge device is br0.
Examples:
#launch a QEMU instance with the default network helper to
#connect a TAP device to bridge br0
qemu-system-i386 linux.img -netdev bridge,id=n1 -device virtio-net,netdev=n1
#launch a QEMU instance with the default network helper to
#connect a TAP device to bridge qemubr0
qemu-system-i386 linux.img -netdev bridge,br=qemubr0,id=n1 -device virtio-net,netdev=n1
What is the acl file? What is the interface to qemu-bridge-helper?
Also this is what bridge.conf contains:
# Access control file for qemu bridge helper
# Syntax consists of:
# # comment (ignored)
# allow all
# allow <bridge_name>
# deny all
# deny <bridge_name>
# include /path/to/additional/ACL/file
# Users are blacklisted by default and 'deny' takes precedence over 'allow'.
# Including additional ACL files allows file access permissions to be used as
# a component of the policy to allow access or deny access to specific bridges.
How are users specified? Or is the mention of users bogus?
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/177
|