You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sed -e "s@/opt/vde@$(PREFIX)@g" launchd/io.github.virtualsquare.vde-2.vde_switch.plist >"$(DESTDIR)/Library/LaunchDaemons/io.github.virtualsquare.vde-2.vde_switch.plist"
50
-
sed -e "s@/opt/vde@$(PREFIX)@g" launchd/io.github.lima-vm.vde_vmnet.plist >"$(DESTDIR)/Library/LaunchDaemons/io.github.lima-vm.vde_vmnet.plist"
44
+
sed -e "s@/opt/socket_vmnet@$(PREFIX)@g" launchd/io.github.lima-vm.socket_vmnet.plist >"$(DESTDIR)/Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist"
51
45
52
46
ifneq ($(BRIDGED),)
53
-
sed -e "s@/opt/vde@$(PREFIX)@g" -e "s/en0/$(BRIDGED)/g" launchd/io.github.virtualsquare.vde-2.vde_switch.bridged.en0.plist > "$(DESTDIR)/Library/LaunchDaemons/io.github.virtualsquare.vde-2.vde_switch.bridged.$(BRIDGED).plist"
54
-
sed -e "s@/opt/vde@$(PREFIX)@g" -e "s/en0/$(BRIDGED)/g" launchd/io.github.lima-vm.vde_vmnet.bridged.en0.plist > "$(DESTDIR)/Library/LaunchDaemons/io.github.lima-vm.vde_vmnet.bridged.$(BRIDGED).plist"
47
+
sed -e "s@/opt/socket_vmnet@$(PREFIX)@g" -e "s/en0/$(BRIDGED)/g" launchd/io.github.lima-vm.socket_vmnet.bridged.en0.plist > "$(DESTDIR)/Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.bridged.$(BRIDGED).plist"
### Is it possible to run `vde_vmnet` with SETUID?
97
+
### Is it possible to run `socket_vmnet` with SETUID?
122
98
123
99
Yes, but discouraged, as it allows non-root users to write arbitrary files, by specifying certain CLI args and environment variables.
124
100
125
101
Instead, consider using launchd or sudo.
126
102
127
-
See [`./etc_sudoers.d/vde_vmnet`](./etc_sudoers.d/vde_vmnet) to allow running `sudo vde_vmnet` with reduced set of args and environment variables.
103
+
See [`./etc_sudoers.d/socket_vmnet`](./etc_sudoers.d/socket_vmnet) to allow running `sudo socket_vmnet` with reduced set of args and environment variables.
104
+
105
+
### How is socket_vmnet related to vde_vmnet?
106
+
107
+
`socket_vmnet` was forked from [`vde_vmnet`](https://github.com/lima-vm/vde_vmnet) v0.6.0.
108
+
Unlike `vde_vmnet`, `socket_vmnet` does not depend on VDE.
128
109
129
-
### How is vde_vmnet related to QEMU-builtin vmnet support?
130
-
There are proposal to add builtin vmnet support for QEMU:
### How is socket_vmnet related to QEMU-builtin vmnet support?
111
+
There is a proposal to add builtin vmnet support for QEMU: [`[v22] Add vmnet.framework based network backend`](https://patchwork.kernel.org/project/qemu-devel/cover/[email protected]/).
133
112
134
-
However, QEMU-builtin vmnet is highly likely to require running the entire QEMU process as root.
113
+
However, QEMU-builtin vmnet requires running the entire QEMU process as root.
135
114
136
-
On the other hand, `vde_vmnet` does not require the entire QEMU process to run as root, though `vde_vmnet` has to run as root.
115
+
On the other hand, `socket_vmnet` does not require the entire QEMU process to run as root, though `socket_vmnet` has to run as root.
137
116
138
117
### How to use static IP addresses?
139
118
When `--vmnet-gateway=IP` is set to "192.168.105.1", the whole subnet (192.168.105.2-192.168.105.254) is used as the DHCP range.
0 commit comments