From: Izhar <[email protected]> This commit removes the mem_path option from instance man page as it is not available at the instance level anymore.
Signed-off-by: Izhar <[email protected]> --- man/gnt-instance.rst | 9 +-------- 1 files changed, 1 insertions(+), 8 deletions(-) diff --git a/man/gnt-instance.rst b/man/gnt-instance.rst index 7d9e58b..2a145ac 100644 --- a/man/gnt-instance.rst +++ b/man/gnt-instance.rst @@ -210,7 +210,7 @@ only value of memory an instance could have. With the memory is always available for an instance, but allows more memory to be used (up to the maximum memory) should it be free. -The ``-H (--hypervisor-parameters)`` option specified the hypervisor +The ``-H (--hypervisor-parameters)`` option specifies the hypervisor to use for the instance (must be one of the enabled hypervisors on the cluster) and optionally custom parameters for this instance. If not other options are used (i.e. the invocation is just -H *NAME*) the @@ -589,13 +589,6 @@ kvm\_flag -disable-kvm is passed. If unset no flag is passed, and the default running mode for your kvm binary will be used. -mem\_path - Valid for the KVM hypervisor. - - This option passes the -mem-path argument to kvm with the path (on - the node) to the mount point of the hugetlbfs file system, along - with the -mem-prealloc argument too. - use\_chroot Valid for the KVM hypervisor. -- 1.7.2.5
