| .. | .. |
|---|
| 8 | 8 | ======== |
|---|
| 9 | 9 | |
|---|
| 10 | 10 | The net_failover driver provides an automated failover mechanism via APIs |
|---|
| 11 | | -to create and destroy a failover master netdev and mananges a primary and |
|---|
| 11 | +to create and destroy a failover master netdev and manages a primary and |
|---|
| 12 | 12 | standby slave netdevs that get registered via the generic failover |
|---|
| 13 | | -infrastructrure. |
|---|
| 13 | +infrastructure. |
|---|
| 14 | 14 | |
|---|
| 15 | 15 | The failover netdev acts a master device and controls 2 slave devices. The |
|---|
| 16 | 16 | original paravirtual interface is registered as 'standby' slave netdev and |
|---|
| .. | .. |
|---|
| 29 | 29 | ============================================= |
|---|
| 30 | 30 | |
|---|
| 31 | 31 | net_failover enables hypervisor controlled accelerated datapath to virtio-net |
|---|
| 32 | | -enabled VMs in a transparent manner with no/minimal guest userspace chanages. |
|---|
| 32 | +enabled VMs in a transparent manner with no/minimal guest userspace changes. |
|---|
| 33 | 33 | |
|---|
| 34 | 34 | To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY |
|---|
| 35 | 35 | feature on the virtio-net interface and assign the same MAC address to both |
|---|