Changeset View
Changeset View
Standalone View
Standalone View
etc/devd/hyperv.conf
Show All 33 Lines | notify 11 { | ||||
action "pkill -x hv_vss_daemon"; | action "pkill -x hv_vss_daemon"; | ||||
}; | }; | ||||
# | # | ||||
# Rules for non-transparent network VF. | # Rules for non-transparent network VF. | ||||
# | # | ||||
# How network VF works with hn(4) on Hyper-V in non-transparent mode: | # How network VF works with hn(4) on Hyper-V in non-transparent mode: | ||||
# | # | ||||
# - Each network VF has a cooresponding hn(4). | # - Each network VF has a corresponding hn(4). | ||||
# - The network VF and the it's cooresponding hn(4) have the same hardware | # - The network VF and the it's corresponding hn(4) have the same hardware | ||||
# address. | # address. | ||||
# - Once the network VF is up, e.g. ifconfig VF up: | # - Once the network VF is up, e.g. ifconfig VF up: | ||||
# o All of the transmission should go through the network VF. | # o All of the transmission should go through the network VF. | ||||
# o Most of the reception goes through the network VF. | # o Most of the reception goes through the network VF. | ||||
# o Small amount of reception may go through the cooresponding hn(4). | # o Small amount of reception may go through the corresponding hn(4). | ||||
# This reception will happen, even if the the cooresponding hn(4) is | # This reception will happen, even if the corresponding hn(4) is | ||||
# down. The cooresponding hn(4) will change the reception interface | # down. The corresponding hn(4) will change the reception interface | ||||
# to the network VF, so that network layer and application layer will | # to the network VF, so that network layer and application layer will | ||||
# be tricked into thinking that these packets were received by the | # be tricked into thinking that these packets were received by the | ||||
# network VF. | # network VF. | ||||
# o The cooresponding hn(4) pretends the physical link is down. | # o The corresponding hn(4) pretends the physical link is down. | ||||
# - Once the network VF is down or detached: | # - Once the network VF is down or detached: | ||||
# o All of the transmission should go through the cooresponding hn(4). | # o All of the transmission should go through the corresponding hn(4). | ||||
# o All of the reception goes through the cooresponding hn(4). | # o All of the reception goes through the corresponding hn(4). | ||||
# o The cooresponding hn(4) fallbacks to the original physical link | # o The corresponding hn(4) fallbacks to the original physical link | ||||
# detection logic. | # detection logic. | ||||
# | # | ||||
# All these features are mainly used to help live migration, during which | # All these features are mainly used to help live migration, during which | ||||
# the network VF will be detached, while the network communication to the | # the network VF will be detached, while the network communication to the | ||||
# VM must not be cut off. In order to reach this level of live migration | # VM must not be cut off. In order to reach this level of live migration | ||||
# transparency, we use failover mode lagg(4) with the network VF and the | # transparency, we use failover mode lagg(4) with the network VF and the | ||||
# cooresponding hn(4) attached to it. | # corresponding hn(4) attached to it. | ||||
# | # | ||||
# To ease user configuration for both network VF and non-network VF, the | # To ease user configuration for both network VF and non-network VF, the | ||||
# lagg(4) will be created by the following rules, and the configuration | # lagg(4) will be created by the following rules, and the configuration | ||||
# of the cooresponding hn(4) will be applied to the lagg(4) automatically. | # of the corresponding hn(4) will be applied to the lagg(4) automatically. | ||||
# | # | ||||
# NOTE: | # NOTE: | ||||
# If live migration is not needed at all, the following rules could be | # If live migration is not needed at all, the following rules could be | ||||
# commented out, and the network VF interface could be used exclusively. | # commented out, and the network VF interface could be used exclusively. | ||||
# Most often the cooresponding hn(4) could be completely ignored. | # Most often the corresponding hn(4) could be completely ignored. | ||||
# | # | ||||
# | # | ||||
# Default workflow for the network VF bringup: | # Default workflow for the network VF bringup: | ||||
# 1) ETHERNET/IFATTACH -> VF interface up (delayed by rc.conf hyperv_vf_delay | # 1) ETHERNET/IFATTACH -> VF interface up (delayed by rc.conf hyperv_vf_delay | ||||
# seconds). This operation will trigger HYPERV_NIC_VF/VF_UP. | # seconds). This operation will trigger HYPERV_NIC_VF/VF_UP. | ||||
# 2) HYPERV_NIC_VF/VF_UP: | # 2) HYPERV_NIC_VF/VF_UP: | ||||
# a) Create laggX coresponding to hnX. | # a) Create laggX coresponding to hnX. | ||||
# b) Add hnX and VF to laggX. | # b) Add hnX and VF to laggX. | ||||
Show All 26 Lines |