QEMU/Network: Difference between revisions

Jump to navigation Jump to search
perms
mNo edit summary
(perms)
 
| <kbd>user</kbd> || User networking, using a heavily modified SLiRP to proxy IP traffic to and from the guest. Requires no special permissions. || N/A (TODO)
|-
| <kbd>tap</kbd> || TAP networking.<br>This uses a Linux TAP device, and allows either local or full connectivity with the internet, <br>depending on what the bridge or network device it is connected to has.<br>Requires that the user QEMU is running as has permission to open the TAP device. || <kbd>ifname</kbd> - TAP interface name. (required)<br><kbd>script</kbd> - Script to run if the tap requires elevated permissions to bring up. Set to literal <kbd>no</kbd> to disable.<br><kbd>downscript</kbd> - Script to run if the tap requires elevated permissions to bring down. Set to literal <kbd>no</kbd> to disable.<br><kbd>vhost</kbd> - Boolean option (default off) to enable vhost dataplane acceleration if attached to a Virtio adapter.<br>
|-
| <kbd>bridge</kbd> || Bridge networking.<br>This uses <kbd>qemu-bridge-helper</kbd> (or another helper program you provide) to create a TAP linked to the bridge, and deletes it when the VM stops.<br>Only requires permissions if <kbd>qemu-bridge-helper</kbd> is not setuid. || <kbd>br</kbd> - The bridge to use. (required)<br><kbd>helper</kbd> - Path to an alternate helper (if not using qemu-bridge-helper).<br>
|-
| <kbd>l2tpv3</kbd> || L2TPv3 passthrough network.<br>Encapsulates all the Ethernet frames created by the guest onto the host network using the L2TPv3 protocol. || TODO

Navigation menu