src/sys/modules/hyperv/utilities, branch releng/14.3

sys: Remove $FreeBSD$: one-line sh pattern

2023-08-16T17:54:58+00:00

Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/

arm64: Hyper-V: enablement for ARM64 in Hyper-V (Part 3, final)

2022-10-27T13:53:22+00:00

This is the last part for ARM64 Hyper-V enablement. This includes
commone files and make file changes to enable the ARM64 FreeBSD
guest on Hyper-V. With this patch, it should be able to build
the ARM64 image and install it on Hyper-V.

Reviewed by:	emaste, andrew, whu
Tested by:	Souradeep Chakrabarti 
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D36744

sys/modules: normalize .CURDIR-relative paths to SRCTOP

2017-03-04T10:10:17+00:00

This simplifies make output/logic

Tested with:	`cd sys/modules; make ALL_MODULES=` on amd64
MFC after:	1 month
Sponsored by:	Dell EMC Isilon

hyperv/ic: Rename cleaned up files.

2016-12-20T09:46:14+00:00

MFC after:	1 week
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D8850

hyperv/ic: Rname cleaned up file.

2016-12-20T07:14:24+00:00

MFC after:	1 week
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D8848

hyperv/vss: Add driver and tools for VSS

2016-11-15T02:36:12+00:00

VSS stands for "Volume Shadow Copy Service".  Unlike virtual machine
snapshot, it only takes snapshot for the virtual disks, so both
filesystem and applications have to aware of it, and cooperate the
whole 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 disabled
by editting /etc/devd/hyperv.conf.

Submitted by:	Hongjiang Zhang 
Reviewed by:	kib, mckusick
MFC after:	3 weeks
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D8224

hyperv/vmbus: Add vmbus method for GUID base device probing.

2016-07-13T05:01:12+00:00

Reduce the exposure of hv_device.

MFC after:	1 week
Sponsored by:	Microsoft OSTC
Differential Revision:	https://reviews.freebsd.org/D7024

hyperv/utils: Code rearrange and cleanup

2016-02-24T05:01:18+00:00

Split heartbeat, shutdown and timesync out of utils code
and name them properly.

Submitted by:	Jun Su 
Reviewed by:	adrian, sephe, Hongjiang Zhang 
MFC after:	1 week
Sponsored by:	Microsoft OSTC
Differential Revision:	https://reviews.freebsd.org/D5216

Import HyperV Key-Value Pair (KVP) driver and daemon code by Microsoft,

2014-09-13T02:15:31+00:00

many thanks for their continued support of FreeBSD.

While I'm there, also implement a new build knob, WITHOUT_HYPERV to
disable 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 
MFC after:	1 week

Fix make depend, apply a bit of style.

2013-09-28T07:04:03+00:00

Approved by:	re (marius)
Reviewed by:	grehan