1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
<table class="head">
<tr>
<td class="head-ltitle">HYPER-V(4)</td>
<td class="head-vol">Device Drivers Manual</td>
<td class="head-rtitle">HYPER-V(4)</td>
</tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">hv_kvp</code> — <span class="Nd">Hyper-V
Key Value Pair Driver</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp">To compile this driver into the kernel, place the following lines
in the system kernel configuration file:</p>
<div class="Bd Pp Bd-indent"><code class="Cd">device hyperv</code></div>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">hv_kvp</code> driver provides the ability to
store, retrieve, modify and delete key value pairs for
<span class="Ux">FreeBSD</span> guest partitions running on Hyper-V. Hyper-V
allows administrators to store custom metadata in the form of key value
pairs inside the <span class="Ux">FreeBSD</span> guest partition.
Administrators can use Windows Powershell scripts to add, read, modify and
delete such key value pairs.</p>
<p class="Pp">The driver is bare bones and merely forwards requests to its
counterpart user mode daemon, <a class="Xr">hv_kvp_daemon(8)</a>. The daemon
maintains pools of key value pairs and does the actual metadata
management.</p>
<p class="Pp">The same driver and daemon combination are also used to set and
get IP addresses from a <span class="Ux">FreeBSD</span> guest.</p>
<p class="Pp">The set functionality is particularly useful when the
<span class="Ux">FreeBSD</span> 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
<span class="Ux">FreeBSD</span> guest's IP address to its original static
value.</p>
<p class="Pp">On the other hand, the get IP functionality is used to update the
guest IP address in the Hyper-V management console window.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
ALSO</a></h1>
<p class="Pp"><a class="Xr">hv_ata_pci_disengage(4)</a>,
<a class="Xr">hv_netvsc(4)</a>, <a class="Xr">hv_storvsc(4)</a>,
<a class="Xr">hv_utils(4)</a>, <a class="Xr">hv_vmbus(4)</a>,
<a class="Xr">hv_kvp_daemon(8)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">Support for <code class="Nm">hv_kvp</code> first appeared in
<span class="Ux">FreeBSD 10.0</span>. The driver was developed through a
joint effort between Citrix Incorporated, Microsoft Corporation and Network
Appliance Incorporated.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
<p class="Pp"><span class="Ux">FreeBSD</span> support for
<code class="Nm">hv_kvp</code> was first added by <span class="An">Microsoft
BSD Integration Services Team</span>
<<a class="Mt" href="mailto:bsdic@microsoft.com">bsdic@microsoft.com</a>>.</p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">September 10, 2013</td>
<td class="foot-os">FreeBSD 15.0</td>
</tr>
</table>
|
