mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
kfraser@localhost.localdomain
e080ffba8d
When calling destroyDevice code path (e.g. xm block-detach dom devid), allow specifying an integer device id or a device name such as xvdN or /dev/xvdN. Allowing the /dev/xvdN form is useful when detaching devices from dom0. Bootloaders may do this to unmount a disk previously mounted in dom0. Move examination of device ID format into the DevController, permitting device controllers to determine a valid device ID instead of higher level code. Signed-off-by: Jim Fehlig <jfehlig@novell.com>
## # readme.txt <description to the sHype/Xen access control architecture> # # Author: # Reiner Sailer 08/30/2006 <sailer@watson.ibm.com> # # # This file is a toc for information regarding # the access control policy and tools in Xen. ## 1. Xen User Guide describes how to configure, install, and deploy the sHype Access Control Module in Xen. See chapter "sHype/Xen Access Control". 2. 'xm' man page describes the commands related to Xen management, including the commands to manage security policies and labels. Read the access control subcommand section of the xm manual first. 3. policy.txt describes examples for access control policies in Xen. First read the policy description in the Xen User Guide. 4. policytools.txt describes the available tools for creating and managing security policies in Xen.