hv_kvp_daemon(8) [freebsd man page]

HV_KVP_DAEMON(8)					    BSD System Manager's Manual 					  HV_KVP_DAEMON(8)

NAME

     hv_kvp_daemon -- Hyper-V Key Value Pair Daemon

SYNOPSIS

     hv_kvp_daemon [-dn]

DESCRIPTION

     The hv_kvp_daemon daemon provides the ability to store, retrieve, modify and delete Key Value pairs for FreeBSD guest partitions running on
     Hyper-V.

     Hyper-V allows administrators to store custom metadata in the form of Key Value pairs inside the FreeBSD guest partition.	Administrators can
     use Windows Powershell scripts to add, read, modify and delete such Key Value pairs.

     The hv_kvp_daemon accepts Key Value pair management requests from the hv_utils(4) driver and performs the actual metadata management on the
     file-system.

     The same daemon and driver combination is also used to set and get IP addresses from a FreeBSD guest.

     The set functionality is particularly useful when the FreeBSD guest is assigned a static IP address and is failed over from one Hyper-V host
     to another.  After failover, Hyper-V uses the set IP functionality to automatically update the FreeBSD guest's IP address to its original
     static value.

     On the other hand, the get IP functionality is used to update the guest IP address in the Hyper-V management console window.

     The options are as follows:

     -d      Run as regular process instead of a daemon for debugging purpose.

     -n      Generate debugging output.

SEE ALSO

     hv_vmbus(4), hv_utils(4), hv_netvsc(4), hv_storvsc(4), hv_ata_pci_disengage(4), hv_kvp(4)

HISTORY

     Support for Hyper-V in the form of ports was first released in September 2013.  The daemon was developed through a joint effort between Cit-
     rix Inc., Microsoft Corp. and Network Appliance Inc..

AUTHORS

     FreeBSD support for hv_kvp_daemon was first added by Microsoft BSD Integration Services Team <bsdic@microsoft.com>.

BSD
								 October 27, 2014							       BSD

XBDBACK(4)						 BSD/xen Kernel Interfaces Manual						XBDBACK(4)

NAME

     xbdback -- Xen backend paravirtualized block device interface

SYNOPSIS

     pseudo-device xbdback

DESCRIPTION

     The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to
     a hard disk.  xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4).

     All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary
     identifier.  This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers.  For example,
     identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention.  For NetBSD, the guest device name spec-
     ified in the guest configuration file does not matter, and can be chosen arbitrarily.

     A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain.  In the XenStore, xbd and xbdback are identified by
     ``vbd'' (virtual block device) entries.

DIAGNOSTICS

     xbd backend: attach device %s (size %d) for domain %d  Gives the device used as xbdback interface for the given guest domain, and its size,
     in bytes.

     xbd backend 0x%x for domain %d using event channel %d, protocol %s  Gives the backend identifier, guest domain ID, event channel ID, and pro-
     tocol used for block level communication.

     xbdback %s: can't VOP_OPEN device 0x%x: %d  When this message appears in the system message buffer with error 16 (EBUSY), the device is
     likely to be already mounted.  It must be unmounted first, as the system will refuse to open it a second time.

SEE ALSO

     vnd(4), xbd(4), xenbus(4)

HISTORY

     The xbdback driver first appeared in NetBSD 4.0.

AUTHORS

     The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.

BSD
								   June 7, 2011 							       BSD