Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hv_vmbus(4) [freebsd man page]

HYPER-V(4)						   BSD Kernel Interfaces Manual 						HYPER-V(4)

NAME

     hv_vmbus -- Hyper-V Virtual Machine Bus (VMBus) Driver

SYNOPSIS

     To compile this driver into the kernel, place the following lines in the system kernel configuration file:

	   device hyperv

DESCRIPTION

     The hv_vmbus provides a high performance communication interface between guest and root partitions in Hyper-V.  Hyper-V is a hypervisor-based
     virtualization technology from Microsoft.	Hyper-V supports isolation in terms of a partition.  A partition is a logical unit of isolation,
     supported by the hypervisor, in which operating systems execute.

     The Microsoft hypervisor must have at least one parent, or root, partition, running Windows Server operating system.  The virtualization
     stack runs in the parent partition and has direct access to the hardware devices.	The root partition then creates the child partitions which
     host the guest operating systems.

     Child partitions do not have direct access to other hardware resources and are presented a virtual view of the resources, as virtual devices
     (VDevs).  Requests to the virtual devices are redirected either via the VMBus or the hypervisor to the devices in the parent partition, which
     handles the requests.

     The VMBus is a logical inter-partition communication channel.  The parent partition hosts Virtualization Service Providers (VSPs) which com-
     municate over the VMBus to handle device access requests from child partitions.  Child partitions host Virtualization Service Consumers
     (VSCs) which redirect device requests to VSPs in the parent partition via the VMBus.  The Hyper-V VMBus driver defines and implements the
     interface that facilitate high performance bi-directional communication between the VSCs and VSPs.  All VSCs utilize the VMBus driver.

SEE ALSO

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

HISTORY

     Support for hv_vmbus first appeared in FreeBSD 10.0.  The driver was developed through a joint effort between Citrix Incorporated, Microsoft
     Corporation, and Network Appliance Incorporated.

AUTHORS

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

BSD
								September 10, 2013							       BSD

Check Out this Related Man Page

MAC_PARTITION(4)					   BSD Kernel Interfaces Manual 					  MAC_PARTITION(4)

NAME

     mac_partition -- process partition policy

SYNOPSIS

     To compile the process partition policy into your kernel, place the following lines in your kernel configuration file:

	   options MAC
	   options MAC_PARTITION

     Alternately, to load the process partition module at boot time, place the following line in your kernel configuration file:

	   options MAC

     and in loader.conf(5):

	   mac_partition_load="YES"

DESCRIPTION

     The mac_partition policy module implements a process partition policy, which allows administrators to place running processes into
     ``partitions'', based on their numeric process partition (specified in the process's MAC label).  Processes with a specified partition can
     only see processes that are in the same partition.  If no partition is specified for a process, it can see all other processes in the system
     (subject to other MAC policy restrictions not defined in this man page).  No provisions for placing processes into multiple partitions are
     available.

   Label Format
     Partition labels take on the following format:

	   partition/value

     Where value can be any integer value or ``none''.	For example:

	   partition/1
	   partition/20
	   partition/none

SEE ALSO

     mac(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_none(4), mac_portacl(4), mac_seeotheruids(4),
     mac_test(4), maclabel(7), mac(9)

HISTORY

     The mac_partition policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project.

AUTHORS

     This software was contributed to the FreeBSD Project by Network Associates Labs, the Security Research Division of Network Associates Inc.
     under DARPA/SPAWAR contract N66001-01-C-8035 (``CBOSS''), as part of the DARPA CHATS research program.

BUGS

     See mac(9) concerning appropriateness for production use.	The TrustedBSD MAC Framework is considered experimental in FreeBSD.

     While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by
     entry point checks.  As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user.

BSD
								 December 9, 2002							       BSD
Man Page