€•àdŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ+/translations/zh_CN/networking/net_failover”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/zh_TW/networking/net_failover”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/it_IT/networking/net_failover”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/ja_JP/networking/net_failover”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/ko_KR/networking/net_failover”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/sp_SP/networking/net_failover”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h¡hhhžhhŸŒE/var/lib/git/docbuild/linux/Documentation/networking/net_failover.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ NET_FAILOVER”h]”hŒ NET_FAILOVER”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒOverview”h]”hŒOverview”…””}”(hhÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhÉhžhhŸh³h KubhŒ paragraph”“”)”}”(hŒåThe net_failover driver provides an automated failover mechanism via APIs to create and destroy a failover master netdev and manages a primary and standby slave netdevs that get registered via the generic failover infrastructure.”h]”hŒåThe net_failover driver provides an automated failover mechanism via APIs to create and destroy a failover master netdev and manages a primary and standby slave netdevs that get registered via the generic failover infrastructure.”…””}”(hhÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K hhÉhžhubhÛ)”}”(hXîThe failover netdev acts a master device and controls 2 slave devices. The original paravirtual interface is registered as 'standby' slave netdev and a passthru/vf device with the same MAC gets registered as 'primary' slave netdev. Both 'standby' and 'failover' netdevs are associated with the same 'pci' device. The user accesses the network interface via 'failover' netdev. The 'failover' netdev chooses 'primary' netdev as default for transmits when it is available with link up and running.”h]”hXThe failover netdev acts a master device and controls 2 slave devices. The original paravirtual interface is registered as ‘standby’ slave netdev and a passthru/vf device with the same MAC gets registered as ‘primary’ slave netdev. Both ‘standby’ and ‘failover’ netdevs are associated with the same ‘pci’ device. The user accesses the network interface via ‘failover’ netdev. The ‘failover’ netdev chooses ‘primary’ netdev as default for transmits when it is available with link up and running.”…””}”(hhêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhhÉhžhubhÛ)”}”(hŒïThis can be used by paravirtual drivers to enable an alternate low latency datapath. It also enables hypervisor controlled live migration of a VM with direct attached VF by failing over to the paravirtual datapath when the VF is unplugged.”h]”hŒïThis can be used by paravirtual drivers to enable an alternate low latency datapath. It also enables hypervisor controlled live migration of a VM with direct attached VF by failing over to the paravirtual datapath when the VF is unplugged.”…””}”(hhøhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhhÉhžhubeh}”(h]”Œoverview”ah ]”h"]”Œoverview”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒ-virtio-net accelerated datapath: STANDBY mode”h]”hŒ-virtio-net accelerated datapath: STANDBY mode”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjhžhhŸh³h KubhÛ)”}”(hŒšnet_failover enables hypervisor controlled accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes.”h]”hŒšnet_failover enables hypervisor controlled accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhjhžhubhÛ)”}”(hŒ®To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY feature on the virtio-net interface and assign the same MAC address to both virtio-net and VF interfaces.”h]”hŒ®To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY feature on the virtio-net interface and assign the same MAC address to both virtio-net and VF interfaces.”…””}”(hj-hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K"hjhžhubhÛ)”}”(hŒHHere is an example libvirt XML snippet that shows such configuration: ::”h]”hŒEHere is an example libvirt XML snippet that shows such configuration:”…””}”(hj;hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K&hjhžhubhŒ literal_block”“”)”}”(hX
”h]”hX
”…””}”hjKsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jIhŸh³h K)hjhžhubhÛ)”}”(hXIn this configuration, the first device definition is for the virtio-net interface and this acts as the 'persistent' device indicating that this interface will always be plugged in. This is specified by the 'teaming' tag with required attribute type having value 'persistent'. The link state for the virtio-net device is set to 'down' to ensure that the 'failover' netdev prefers the VF passthrough device for normal communication. The virtio-net device will be brought UP during live migration to allow uninterrupted communication.”h]”hX(In this configuration, the first device definition is for the virtio-net interface and this acts as the ‘persistent’ device indicating that this interface will always be plugged in. This is specified by the ‘teaming’ tag with required attribute type having value ‘persistent’. The link state for the virtio-net device is set to ‘down’ to ensure that the ‘failover’ netdev prefers the VF passthrough device for normal communication. The virtio-net device will be brought UP during live migration to allow uninterrupted communication.”…””}”(hjYhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K;hjhžhubhÛ)”}”(hX$The second device definition is for the VF passthrough interface. Here the 'teaming' tag is provided with type 'transient' indicating that this device may periodically be unplugged. A second attribute - 'persistent' is provided and points to the alias name declared for the virtio-net device.”h]”hX0The second device definition is for the VF passthrough interface. Here the ‘teaming’ tag is provided with type ‘transient’ indicating that this device may periodically be unplugged. A second attribute - ‘persistent’ is provided and points to the alias name declared for the virtio-net device.”…””}”(hjghžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KChjhžhubhÛ)”}”(hŒiBooting a VM with the above configuration will result in the following 3 interfaces created in the VM: ::”h]”hŒfBooting a VM with the above configuration will result in the following 3 interfaces created in the VM:”…””}”(hjuhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KHhjhžhubjJ)”}”(hX¹4: ens10: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff inet 192.168.12.53/24 brd 192.168.12.255 scope global dynamic ens10 valid_lft 42482sec preferred_lft 42482sec inet6 fe80::97d8:db2:8c10:b6d6/64 scope link valid_lft forever preferred_lft forever 5: ens10nsby: mtu 1500 qdisc fq_codel master ens10 state DOWN group default qlen 1000 link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff 7: ens11: mtu 1500 qdisc mq master ens10 state UP group default qlen 1000 link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff”h]”hX¹4: ens10: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff inet 192.168.12.53/24 brd 192.168.12.255 scope global dynamic ens10 valid_lft 42482sec preferred_lft 42482sec inet6 fe80::97d8:db2:8c10:b6d6/64 scope link valid_lft forever preferred_lft forever 5: ens10nsby: mtu 1500 qdisc fq_codel master ens10 state DOWN group default qlen 1000 link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff 7: ens11: mtu 1500 qdisc mq master ens10 state UP group default qlen 1000 link/ether 52:54:00:00:12:53 brd ff:ff:ff:ff:ff:ff”…””}”hjƒsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jIhŸh³h KLhjhžhubhÛ)”}”(hŒ¡Here, ens10 is the 'failover' master interface, ens10nsby is the slave 'standby' virtio-net interface, and ens11 is the slave 'primary' VF passthrough interface.”h]”hŒ­Here, ens10 is the ‘failover’ master interface, ens10nsby is the slave ‘standby’ virtio-net interface, and ens11 is the slave ‘primary’ VF passthrough interface.”…””}”(hj‘hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KWhjhžhubhÛ)”}”(hXòOne point to note here is that some user space network configuration daemons like systemd-networkd, ifupdown, etc, do not understand the 'net_failover' device; and on the first boot, the VM might end up with both 'failover' device and VF acquiring IP addresses (either same or different) from the DHCP server. This will result in lack of connectivity to the VM. So some tweaks might be needed to these network configuration daemons to make sure that an IP is received only on the 'failover' device.”h]”hXþOne point to note here is that some user space network configuration daemons like systemd-networkd, ifupdown, etc, do not understand the ‘net_failover’ device; and on the first boot, the VM might end up with both ‘failover’ device and VF acquiring IP addresses (either same or different) from the DHCP server. This will result in lack of connectivity to the VM. So some tweaks might be needed to these network configuration daemons to make sure that an IP is received only on the ‘failover’ device.”…””}”(hjŸhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KZhjhžhubhÛ)”}”(hŒaBelow is the patch snippet used with 'cloud-ifupdown-helper' script found on Debian cloud images:”h]”hŒeBelow is the patch snippet used with ‘cloud-ifupdown-helper’ script found on Debian cloud images:”…””}”(hj­hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KbhjhžhubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hX:: @@ -27,6 +27,8 @@ do_setup() { local working="$cfgdir/.$INTERFACE" local final="$cfgdir/$INTERFACE" + if [ -d "/sys/class/net/${INTERFACE}/master" ]; then exit 0; fi + if ifup --no-act "$INTERFACE" > /dev/null 2>&1; then # interface is already known to ifupdown, no need to generate cfg log "Skipping configuration generation for $INTERFACE" ”h]”(hŒterm”“”)”}”(hŒ::”h]”hŒ::”…””}”(hjÈhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆhŸh³h KohjÂubhŒ definition”“”)”}”(hhh]”(j¼)”}”(hhh]”jÁ)”}”(hŒd@@ -27,6 +27,8 @@ do_setup() { local working="$cfgdir/.$INTERFACE" local final="$cfgdir/$INTERFACE" ”h]”(jÇ)”}”(hŒ@@ -27,6 +27,8 @@ do_setup() {”h]”hŒ@@ -27,6 +27,8 @@ do_setup() {”…””}”(hjâhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆhŸh³h KhhjÞubj×)”}”(hhh]”hÛ)”}”(hŒDlocal working="$cfgdir/.$INTERFACE" local final="$cfgdir/$INTERFACE"”h]”hŒLlocal working=â€$cfgdir/.$INTERFACE†local final=â€$cfgdir/$INTERFACE—…””}”(hjóhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kghjðubah}”(h]”h ]”h"]”h$]”h&]”uh1jÖhjÞubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÀhŸh³h KhhjÛubah}”(h]”h ]”h"]”h$]”h&]”uh1j»hjØubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒ?if [ -d "/sys/class/net/${INTERFACE}/master" ]; then exit 0; fi”h]”hÛ)”}”(hjh]”hŒCif [ -d “/sys/class/net/${INTERFACE}/master†]; then exit 0; fi”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kjhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒ·if ifup --no-act "$INTERFACE" > /dev/null 2>&1; then # interface is already known to ifupdown, no need to generate cfg log "Skipping configuration generation for $INTERFACE" ”h]”j¼)”}”(hhh]”jÁ)”}”(hŒ¯if ifup --no-act "$INTERFACE" > /dev/null 2>&1; then # interface is already known to ifupdown, no need to generate cfg log "Skipping configuration generation for $INTERFACE" ”h]”(jÇ)”}”(hŒ4if ifup --no-act "$INTERFACE" > /dev/null 2>&1; then”h]”hŒ8if ifup --no-act “$INTERFACE†> /dev/null 2>&1; then”…””}”(hj<hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆhŸh³h Kohj8ubj×)”}”(hhh]”hÛ)”}”(hŒx# interface is already known to ifupdown, no need to generate cfg log "Skipping configuration generation for $INTERFACE"”h]”hŒ|# interface is already known to ifupdown, no need to generate cfg log “Skipping configuration generation for $INTERFACE—…””}”(hjMhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KmhjJubah}”(h]”h ]”h"]”h$]”h&]”uh1jÖhj8ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÀhŸh³h Kohj5ubah}”(h]”h ]”h"]”h$]”h&]”uh1j»hj1ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ+”uh1jhŸh³h KjhjØubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÖhjÂubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÀhŸh³h Kohj½ubah}”(h]”h ]”h"]”h$]”h&]”uh1j»hjhžhhŸNh Nubeh}”(h]”Œ,virtio-net-accelerated-datapath-standby-mode”ah ]”h"]”Œ-virtio-net accelerated datapath: standby mode”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒBLive Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode”h]”hŒBLive Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode”…””}”(hj˜hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj•hžhhŸh³h KrubhÛ)”}”(hŒÏnet_failover also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices by automatic failover to the paravirtual datapath when the VF is unplugged.”h]”hŒÏnet_failover also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices by automatic failover to the paravirtual datapath when the VF is unplugged.”…””}”(hj¦hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kthj•hžhubhÛ)”}”(hXHHere is a sample script that shows the steps to initiate live migration from the source hypervisor. Note: It is assumed that the VM is connected to a software bridge 'br0' which has a single VF attached to it along with the vnet device to the VM. This is not the VF that was passthrough'd to the VM (seen in the vf.xml file). ::”h]”hXKHere is a sample script that shows the steps to initiate live migration from the source hypervisor. Note: It is assumed that the VM is connected to a software bridge ‘br0’ which has a single VF attached to it along with the vnet device to the VM. This is not the VF that was passthrough’d to the VM (seen in the vf.xml file).”…””}”(hj´hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kxhj•hžhubjJ)”}”(hXR# cat vf.xml
# Source Hypervisor migrate.sh #!/bin/bash DOMAIN=vm-01 PF=ens6np0 VF=ens6v1 # VF attached to the bridge. VF_NUM=1 TAP_IF=vmtap01 # virtio-net interface in the VM. VF_XML=vf.xml MAC=52:54:00:00:12:53 ZERO_MAC=00:00:00:00:00:00 # Set the virtio-net interface up. virsh domif-setlink $DOMAIN $TAP_IF up # Remove the VF that was passthrough'd to the VM. virsh detach-device --live --config $DOMAIN $VF_XML ip link set $PF vf $VF_NUM mac $ZERO_MAC # Add FDB entry for traffic to continue going to the VM via # the VF -> br0 -> vnet interface path. bridge fdb add $MAC dev $VF bridge fdb add $MAC dev $TAP_IF master # Migrate the VM virsh migrate --live --persistent $DOMAIN qemu+ssh://$REMOTE_HOST/system # Clean up FDB entries after migration completes. bridge fdb del $MAC dev $VF bridge fdb del $MAC dev $TAP_IF master”h]”hXR# cat vf.xml
# Source Hypervisor migrate.sh #!/bin/bash DOMAIN=vm-01 PF=ens6np0 VF=ens6v1 # VF attached to the bridge. VF_NUM=1 TAP_IF=vmtap01 # virtio-net interface in the VM. VF_XML=vf.xml MAC=52:54:00:00:12:53 ZERO_MAC=00:00:00:00:00:00 # Set the virtio-net interface up. virsh domif-setlink $DOMAIN $TAP_IF up # Remove the VF that was passthrough'd to the VM. virsh detach-device --live --config $DOMAIN $VF_XML ip link set $PF vf $VF_NUM mac $ZERO_MAC # Add FDB entry for traffic to continue going to the VM via # the VF -> br0 -> vnet interface path. bridge fdb add $MAC dev $VF bridge fdb add $MAC dev $TAP_IF master # Migrate the VM virsh migrate --live --persistent $DOMAIN qemu+ssh://$REMOTE_HOST/system # Clean up FDB entries after migration completes. bridge fdb del $MAC dev $VF bridge fdb del $MAC dev $TAP_IF master”…””}”hjÂsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jIhŸh³h Khj•hžhubhÛ)”}”(hŒ¾On the destination hypervisor, a shared bridge 'br0' is created before migration starts, and a VF from the destination PF is added to the bridge. Similarly an appropriate FDB entry is added.”h]”hŒÂOn the destination hypervisor, a shared bridge ‘br0’ is created before migration starts, and a VF from the destination PF is added to the bridge. Similarly an appropriate FDB entry is added.”…””}”(hjÐhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K©hj•hžhubhÛ)”}”(hŒ¥The following script is executed on the destination hypervisor once migration completes, and it reattaches the VF to the VM and brings down the virtio-net interface.”h]”hŒ¥The following script is executed on the destination hypervisor once migration completes, and it reattaches the VF to the VM and brings down the virtio-net interface.”…””}”(hjÞhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K­hj•hžhubj¼)”}”(hhh]”jÁ)”}”(hŒ×:: # reattach-vf.sh #!/bin/bash bridge fdb del 52:54:00:00:12:53 dev ens36v0 bridge fdb del 52:54:00:00:12:53 dev vmtap01 master virsh attach-device --config --live vm01 vf.xml virsh domif-setlink vm01 vmtap01 down”h]”(jÇ)”}”(hŒ::”h]”hŒ::”…””}”(hjóhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆhŸh³h K·hjïubj×)”}”(hhh]”(hÛ)”}”(hŒ# reattach-vf.sh #!/bin/bash”h]”hŒ# reattach-vf.sh #!/bin/bash”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K²hjubhÛ)”}”(hŒ¶bridge fdb del 52:54:00:00:12:53 dev ens36v0 bridge fdb del 52:54:00:00:12:53 dev vmtap01 master virsh attach-device --config --live vm01 vf.xml virsh domif-setlink vm01 vmtap01 down”h]”hŒ¶bridge fdb del 52:54:00:00:12:53 dev ens36v0 bridge fdb del 52:54:00:00:12:53 dev vmtap01 master virsh attach-device --config --live vm01 vf.xml virsh domif-setlink vm01 vmtap01 down”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kµhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÖhjïubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÀhŸh³h K·hjìubah}”(h]”h ]”h"]”h$]”h&]”uh1j»hj•hžhhŸh³h Nubeh}”(h]”Œ@live-migration-of-a-vm-with-sr-iov-vf-virtio-net-in-standby-mode”ah ]”h"]”ŒBlive migration of a vm with sr-iov vf & virtio-net in standby mode”ah$]”h&]”uh1h´hh¶hžhhŸh³h Krubeh}”(h]”Œ net-failover”ah ]”h"]”Œ net_failover”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jeŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j?j<j jj’jj7j4uŒ nametypes”}”(j?‰j ‰j’‰j7‰uh}”(j<h¶jhÉjjj4j•uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hÛ)”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…””}”(hjÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhjÉubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”K'Œsource”h³uh1jÇhjhžhhŸh³h K'ubjÈ)”}”(hhh]”hÛ)”}”(hŒ`Possible incomplete section title. Treating the overline as ordinary text because it's so short.”h]”hŒbPossible incomplete section title. Treating the overline as ordinary text because it’s so short.”…””}”(hjèhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhjåubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jâŒline”KeŒsource”h³uh1jÇhjhžhhŸh³h KgubjÈ)”}”(hhh]”hÛ)”}”(hŒ`Blank line missing before literal block (after the "::")? Interpreted as a definition list item.”h]”hŒdBlank line missing before literal block (after the “::â€)? Interpreted as a definition list item.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhjubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jâŒline”KpŒsource”h³uh1jÇhjØubjÈ)”}”(hhh]”hÛ)”}”(hŒ`Possible incomplete section title. Treating the overline as ordinary text because it's so short.”h]”hŒbPossible incomplete section title. Treating the overline as ordinary text because it’s so short.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhjubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jâŒline”K±Œsource”h³uh1jÇhj•hžhhŸh³h K³ubjÈ)”}”(hhh]”hÛ)”}”(hŒ`Blank line missing before literal block (after the "::")? Interpreted as a definition list item.”h]”hŒdBlank line missing before literal block (after the “::â€)? Interpreted as a definition list item.”…””}”(hj9hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhj6ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jâŒline”K¸Œsource”h³uh1jÇhjubeŒtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.