mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-08-23 00:11:16 +00:00
docs: Auto format networking doc
Signed-off-by: Muminul Islam <muislam@microsoft.com>
This commit is contained in:
parent
767b4f0e59
commit
884d528b31
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
cloud-hypervisor can emulate one or more virtual network interfaces, represented at the hypervisor host by [tap devices](https://www.kernel.org/doc/Documentation/networking/tuntap.txt). This guide briefly describes, in a manual and distribution neutral way, how to setup and use networking with cloud-hypervisor.
|
cloud-hypervisor can emulate one or more virtual network interfaces, represented at the hypervisor host by [tap devices](https://www.kernel.org/doc/Documentation/networking/tuntap.txt). This guide briefly describes, in a manual and distribution neutral way, how to setup and use networking with cloud-hypervisor.
|
||||||
|
|
||||||
## Multiple queue support for net devices ##
|
## Multiple queue support for net devices
|
||||||
|
|
||||||
While multiple vcpus defined for guest, to gain the benefit of vcpu scalable to improve performance, it suggests to define multiple queue pairs for net devices, one Tx/Rx queue pair per one vcpu, that means the number of queue pairs at least is equal to the vcpu count. In that case, after virtnet driver set cpu affinity for virtqueues in guest kernel, vcpus could handle interrupt from different virtqueue pairs in parallel.
|
While multiple vcpus defined for guest, to gain the benefit of vcpu scalable to improve performance, it suggests to define multiple queue pairs for net devices, one Tx/Rx queue pair per one vcpu, that means the number of queue pairs at least is equal to the vcpu count. In that case, after virtnet driver set cpu affinity for virtqueues in guest kernel, vcpus could handle interrupt from different virtqueue pairs in parallel.
|
||||||
|
|
||||||
@ -35,7 +35,7 @@ Use one `--net` command-line argument from cloud-hypervisor to specify the emula
|
|||||||
The `--net` argument takes 1 or more space-separated strings of key value pairs containing the following 4 keys or fields:
|
The `--net` argument takes 1 or more space-separated strings of key value pairs containing the following 4 keys or fields:
|
||||||
|
|
||||||
| Name | Purpose | Optional |
|
| Name | Purpose | Optional |
|
||||||
| -----------|----------------------------| ----------|
|
| ---------- | ---------------------- | -------- |
|
||||||
| tap | tap device name | Yes |
|
| tap | tap device name | Yes |
|
||||||
| mac | vNIC mac address | Yes |
|
| mac | vNIC mac address | Yes |
|
||||||
| ip | tap IP IP address | yes |
|
| ip | tap IP IP address | yes |
|
||||||
@ -104,6 +104,7 @@ bridge name bridge id STP enabled interfaces
|
|||||||
ich-dpl 8000.067afc1b9a67 no ich1
|
ich-dpl 8000.067afc1b9a67 no ich1
|
||||||
ich-int 8000.725412ffce6f no ich0
|
ich-int 8000.725412ffce6f no ich0
|
||||||
```
|
```
|
||||||
|
|
||||||
This completes the layer 2 wiring: The cloud-hypervisor is now connected to the hypervisor host via the 2 linux bridges.
|
This completes the layer 2 wiring: The cloud-hypervisor is now connected to the hypervisor host via the 2 linux bridges.
|
||||||
|
|
||||||
## IP (Layer 3) provisioning
|
## IP (Layer 3) provisioning
|
||||||
@ -116,6 +117,7 @@ On the hypervisor host add the network gateway IP address of each network to the
|
|||||||
root@host:~# ip addr add 192.168.4.1/24 dev ich-int
|
root@host:~# ip addr add 192.168.4.1/24 dev ich-int
|
||||||
root@host:~# ip addr add 10.0.1.1/24 dev ich-dpl
|
root@host:~# ip addr add 10.0.1.1/24 dev ich-dpl
|
||||||
```
|
```
|
||||||
|
|
||||||
The routing table of the hypervisor host should now also have corresponding routing entries:
|
The routing table of the hypervisor host should now also have corresponding routing entries:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
@ -127,6 +129,7 @@ Destination Gateway Genmask Flags Metric Ref Use Iface
|
|||||||
192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 ich-int
|
192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 ich-int
|
||||||
192.168.178.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan1
|
192.168.178.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan1
|
||||||
```
|
```
|
||||||
|
|
||||||
### Virtual Machine
|
### Virtual Machine
|
||||||
|
|
||||||
Within the virtual machine set the vNIC's to up state and provision the corresponding IP addresses on the 2 vNIC's. The steps outlined below use the ip command as an example. Alternative distribution specific procedures can also apply.
|
Within the virtual machine set the vNIC's to up state and provision the corresponding IP addresses on the 2 vNIC's. The steps outlined below use the ip command as an example. Alternative distribution specific procedures can also apply.
|
||||||
|
Loading…
Reference in New Issue
Block a user