hyperv/kvp: Remove set but unused variables.Reported by: GCCReviewed by: Souradeep Chakrabarti <schakrabarti@microsoft.com>Differential Revision: https://reviews.freebsd.org/D40660
hyperv: Add VF bringup scripts and devd rules.How network VF works with hn(4) on Hyper-V in non-transparent mode:- Each network VF has a cooresponding hn(4).- The network VF and the it's cooresp
hyperv: Add VF bringup scripts and devd rules.How network VF works with hn(4) on Hyper-V in non-transparent mode:- Each network VF has a cooresponding hn(4).- The network VF and the it's cooresponding hn(4) have the same hardware address.- Once the network VF is up, e.g. ifconfig VF up: o All of the transmission should go 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). This reception will happen, even if the the cooresponding hn(4) is down. The cooresponding hn(4) will change the reception interface to the network VF, so that network layer and application layer will be tricked into thinking that these packets were received by the network VF. o The cooresponding hn(4) pretends the physical link is down.- Once the network VF is down or detached: o All of the transmission should go through the cooresponding hn(4). o All of the reception goes through the cooresponding hn(4). o The cooresponding hn(4) fallbacks to the original physical link detection logic.All these features are mainly used to help live migration, during whichthe network VF will be detached, while the network communication to theVM must not be cut off. In order to reach this level of live migrationtransparency, we use failover mode lagg(4) with the network VF and thecooresponding hn(4) attached to it.To ease user configuration for both network VF and non-network VF, thelagg(4) will be created by the following rules, and the configurationof the cooresponding hn(4) will be applied to the lagg(4) automatically.Sponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D11635
show more ...
hyperv/kvp: Fix pool direcrory and file permissionPR: 209385MFC after: 2 weeksSponsored by: Microsoft
hyperv/vss: Nuke unused variables.Submitted by: markjReported by: markjMFC after: 3 weeksSponsored by: Microsoft
hyperv/vss: Add driver and tools for VSSVSS stands for "Volume Shadow Copy Service". Unlike virtual machinesnapshot, it only takes snapshot for the virtual disks, so bothfilesystem and applicati
hyperv/vss: Add driver and tools for VSSVSS stands for "Volume Shadow Copy Service". Unlike virtual machinesnapshot, it only takes snapshot for the virtual disks, so bothfilesystem and applications have to aware of it, and cooperate thewhole VSS process.This driver exposes two device files to the userland: /dev/hv_fsvss_dev Normally userland programs should _not_ mess with this device file. It is currently used by the hv_vss_daemon(8), which freezes and thaws the filesystem. NOTE: currently only UFS is supported, if the system mounts _any_ other filesystems, the hv_vss_daemon(8) will veto the VSS process. If hv_vss_daemon(8) was disabled, then this device file must be opened, and proper ioctls must be issued to keep the VSS working. /dev/hv_appvss_dev Userland application can opened this device file to receive the VSS freeze notification, hold the VSS for a while (mainly to flush application data to filesystem), release the VSS process, and receive the VSS thaw notification i.e. applications can run again. The VSS will still work, even if this device file is not opened. However, only filesystem consistency is promised, if this device file is not opened or is not operated properly.hv_vss_daemon(8) is started by devd(8) by default. It can be disabledby editting /etc/devd/hyperv.conf.Submitted by: Hongjiang Zhang <honzhan microsoft com>Reviewed by: kib, mckusickMFC after: 3 weeksSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8224
hyperv/kvp: Don't mix message status codes and function return values.While I'm here, move message status codes to hv_utilreg.h, since theywill be used by the upcoming VSS stuffs.Submitted by: H
hyperv/kvp: Don't mix message status codes and function return values.While I'm here, move message status codes to hv_utilreg.h, since theywill be used by the upcoming VSS stuffs.Submitted by: Hongjiang Zhang <honzhan microsoft com>MFC after: 1 weekSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8391
hyperv/kvp_daemon: Make poll(2) block indefinitelySubmitted by: Jun Su <junsu microsoft com>Reviewed by: Dexuan Cui <decui microsoft com>, me, adrainApproved by: adrianSponsored by: Microsoft OS
hyperv/kvp_daemon: Make poll(2) block indefinitelySubmitted by: Jun Su <junsu microsoft com>Reviewed by: Dexuan Cui <decui microsoft com>, me, adrainApproved by: adrianSponsored by: Microsoft OSTCDifferential Revision: https://reviews.freebsd.org/D4762
Appease gcc-4.2It needs to die, but it resists mipsteriously.Submitted by: Oliver Pinter
Test errno against EEXIST as well.MFC after: 3 days
Rename variable name from 'index' to 'idx' to avoid shadowing index(3).Noticed by: dimMFC after: 2 weeks
Remove an extra copy of hv_kvp_daemon(8) [1].While I'm there also correct typos in OptionalObsoleteFiles and addinformation of the command line options for hv_kvp_daemon(8).Reported by: jmg [1]
Remove an extra copy of hv_kvp_daemon(8) [1].While I'm there also correct typos in OptionalObsoleteFiles and addinformation of the command line options for hv_kvp_daemon(8).Reported by: jmg [1]Reviewed by: jmgMFC after: 2 weeks
Use a char * as iterator over a bounded string.MFC after: 1 week
Use strlcpy(). I don't believe these are real problems but it's betterto use a safe idiom.Reported by: CoverityCID: 1238914MFC after: 1 week
Refactor the code a little bit to avoid NULL deference whenallocation was failed.Reported by: CoverityCID: 1238915MFC after: 1 week
Plug a file descriptor leak.Reported by: CoverityCID: 1238916MFC after: 1 week
Being able to access a path do not necessarily mean we have accessto a directory. So instead of doing this, we just call mkdir(2)directly and test if the returned value is 0 or errno is EISDIR.Re
Being able to access a path do not necessarily mean we have accessto a directory. So instead of doing this, we just call mkdir(2)directly and test if the returned value is 0 or errno is EISDIR.Reported by: CoverityCID: 1238925MFC after: 1 week
Import HyperV Key-Value Pair (KVP) driver and daemon code by Microsoft,many thanks for their continued support of FreeBSD.While I'm there, also implement a new build knob, WITHOUT_HYPERV todisabl
Import HyperV Key-Value Pair (KVP) driver and daemon code by Microsoft,many thanks for their continued support of FreeBSD.While I'm there, also implement a new build knob, WITHOUT_HYPERV todisable building and installing of the HyperV utilities when necessary.The HyperV utilities are only built for i386 and amd64 targets.This is a stable/10 candidate for inclusion with 10.1-RELEASE.Submitted by: Wei Hu <weh microsoft com>MFC after: 1 week