VirtualBox

Changeset 107390 in vbox


Ignore:
Timestamp:
Dec 19, 2024 6:29:28 PM (2 months ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
166433
Message:

Docs: bugref:10705. bugref: 10829. The docs build has been modified to split generated refentry dita files and the user manual files and the following commits from doc's team git repo has been applied:

0946136c74dda0483704db891345cb39548b4e28 Started consolidating known issues and troubleshooting information
845b847e6a8e778b38a57867e25ee5e086a73800 Added individual topics for list of known issues, integrated into Troubleshooting section.
bb574836aac775889bd61e4a72f489617fcb7d18 Removed EFI firmware from experimental features for 7.2
6d2e68b244869991e713d170ecd239739d99ba56 Moved known issues into Known Issues section
e2630c896561587718b5c3197c384a38d07014d5 Merge branch 'VBP-1461_experimental-features' into 'main'
0512e2cce51f49ccdc56f3381a2a0c924f2bd278 Feedback on known issues
a77d6c980f6ff5cad9d32b2fb9290990093a03fa Restructured host and guest OS topics
988af5cc9628f5de0806531bc98686f691a911fd Updates with feedbback from Jacob
982a61c9f25b22b745ec483e763e3d88efe59c40 Included feedback from Jacob
93181c8c6cc2d9a26bcccb1145cb0423c0d9f4c9 Updated known issues with feedback from Klaus
8bc369561c383f09b409fe5e44f507440b3735fb Created Legacy Guest OS section
d7932f55accdab7a03666302d58b8c941cd48be2 Moved known issues to more appropriate places for the info
2a4aa094ba8a7ac6894d2a777316eabf41746580 Further moving of known issues
baeabd5308c5519a4dc26b4197be9b00e419a85a Updated links to cli_topics

Location:
trunk/doc/manual
Files:
20 added
11 deleted
256 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/Makefile.kmk

    r106916 r107390  
    179179        $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita \
    180180        $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita/topics \
     181        $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita/cli_topics \
    181182        $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita/topics/images \
    182183        $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita/topics/licensing \
    … …  
    674675 # @note This produces more files than listed in the output, but we currently let kmk be ignorant of that.
    675676 define def_vbox_refentry_file_to_dita
    676   VBOX_USER_MANUAL_CONVERTED_REFENTRY_DITA_FILES_$1 += $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/$(2).ditamap
    677   $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/$(2).ditamap \
    678   + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/$(2).ditamap.kmk \
    679   + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).dita \
    680   + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).xml: \
     677  VBOX_USER_MANUAL_CONVERTED_REFENTRY_DITA_FILES_$1 += $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/$(2).ditamap
     678  $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/$(2).ditamap \
     679  + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/$(2).ditamap.kmk \
     680  + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).dita \
     681  + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).xml: \
    681682                $$(VBOX_PATH_MANUAL_SRC)/docbook-refentry-to-manual-dita-pre.xsl \
    682683                $$(VBOX_PATH_MANUAL_SRC)/docbook-refentry-to-manual-dita.xsl \
    … …  
    693694        $$(call MSG_TOOL,xsltproc docbook-refentry-to-manual-dita[-pre].xsl,,$$(firstword $$(filter %.xml,$$^)),$$@)
    694695        $$(QUIET)$$(RM) -f -- "$$@" \
    695                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).xml" \
    696                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).dita"
     696                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).xml" \
     697                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).dita"
    697698        $$(QUIET)$$(call VBOX_XSLTPROC_WITH_CAT) \
    698                 --output "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).xml" \
     699                --output "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).xml" \
    699700                $$(VBOX_PATH_MANUAL_SRC)/docbook-refentry-to-manual-dita-pre.xsl \
    700701                $$(qfirstfile , $$(qwildcard , $$(VBOX_PATH_MANUAL_SRC)/$(1)/$(2).xml) $(3) $$(VBOX_PATH_MANUAL_SRC)/en_US/$(2).xml)
    701702        $$(QUIET)$$(call VBOX_XSLTPROC_WITH_CAT) \
    702703                --stringparam "g_fReplaceHyphens" "true" \
    703                 --output "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).dita" \
     704                --output "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).dita" \
    704705                $$(VBOX_PATH_MANUAL_SRC)/docbook-refentry-to-manual-dita.xsl \
    705                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).xml"
     706                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).xml"
    706707        $$(QUIET)$$(VBOX_BLD_PYTHON) $$(VBOX_PATH_MANUAL_SRC)/add_file_to_id_only_references.py \
    707708                --mapping-file "$$(VBOX_USER_MANUAL_ID_MAPPING_FILE_$1)" \
    708                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).dita"
     709                --refentry_file_list "$$(VBOX_MANUAL_XML_REFENTRY_FILES) man_vboximg-mount man_VBoxHeadless" \
     710                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).dita"
    709711        $$(QUIET)$$(ASH) \
    710712                "$$(VBOX_PATH_MANUAL_SRC)/dita-refentry-flat-to-single-topic.sh" \
    711                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).dita" \
     713                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).dita" \
    712714                "$$(VBOX_PATH_MANUAL_SRC)/dita-refentry-flat-topic-ids.xsl" \
    713715                "$$(VBOX_PATH_MANUAL_SRC)/dita-refentry-flat-to-single-topic.xsl" \
    714                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/$(2).ditamap.kmk" \
     716                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/$(2).ditamap.kmk" \
    715717                "VBOX_USER_MANUAL_CONVERTED_REFENTRY_DITA_FILES2_$(1)" \
    716                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics" \
     718                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics" \
    717719                -- $$(subst $$(REDIRECT),$$(REDIRECT_EXT),$$(call VBOX_XSLTPROC_WITH_CAT)) $(VBOX_XSLTPROC_WORKAROUND) \
    718720                --path "$$(VBOX_DITA_TECHNICAL_CONTENT_DTD_PATH)"
    … …  
    720722                --path "$$(VBOX_DITA_TECHNICAL_CONTENT_DTD_PATH)" \
    721723                --stringparam g_sMode map \
    722                 --output "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/$(2).ditamap" \
     724                --output "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/$(2).ditamap" \
    723725                $$(VBOX_PATH_MANUAL_SRC)/dita-refentry-flat-to-single-topic.xsl \
    724                 "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/flat-$(2).dita"
     726                "$$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/flat-$(2).dita"
    725727
    726728 endef # def_vbox_refentry_file_to_dita
    … …  
    777779                $(VBOX_USER_MANUAL_CONVERTED_REFENTRY_DITA_FILES_en_US) \
    778780                $(VBOX_USER_MANUAL_CONVERTED_REFENTRY_DITA_FILES2_en_US) \
    779                 $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita/topics/vboxmanage-cmd-overview.dita
     781                $(VBOX_PATH_MANUAL_OUTBASE)/en_US/dita/cli_topics/vboxmanage-cmd-overview.dita
    780782        $(call MSG_L1,Packing documentation $@)
    781783        $(QUIET)$(RM) -f $@
    … …  
    793795 # @param 1    Language
    794796 define def_vbox_generate_vboxmanage_overview
    795   VBOX_USER_MANUAL_DITA_STAGED_FILES_$1 += $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/vboxmanage-cmd-overview.dita
    796   $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/vboxmanage-cmd-overview.dita \
    797   + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/topics/vboxmanage-cmd-overview.dita.files.xml: \
     797  VBOX_USER_MANUAL_DITA_STAGED_FILES_$1 += $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/vboxmanage-cmd-overview.dita
     798  $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/vboxmanage-cmd-overview.dita \
     799  + $$(VBOX_PATH_MANUAL_OUTBASE)/$(1)/dita/cli_topics/vboxmanage-cmd-overview.dita.files.xml: \
    798800                $$(VBOX_PATH_MANUAL_SRC)/$(1)/vboxmanage-cmd-overview.xsl \
    799801                $$(VBOX_PATH_MANUAL_SRC)/vboxmanage-cmd-overview.xsl \
    … …  
    804806        $$(APPEND) -tn "[email protected]" '<?xml version="1.0"?>' '<files>'
    805807        $$(SED) -n \
    806                 -e 's/^.*topicref .*topics\/man_VBoxManage-\([^.]*\)\.ditamap.*$$(DOLLAR)/<file>vboxmanage-\1-synopsis.dita<\/file>/p' \
     808                -e 's/^.*topicref .*topics\man_VBoxManage-\([^.]*\)\.ditamap.*$$(DOLLAR)/<file>vboxmanage-\1-synopsis.dita<\/file>/p' \
    807809                --append "[email protected]" \
    808810                $(VBOX_PATH_MANUAL_SRC)/$(1)/dita/UserManual.ditamap

  • trunk/doc/manual/add_file_to_id_only_references.py

    r106061 r107390  
    1 # -*- coding: utf-8 -*-
    2 # $Id$
    3 
    4 """
    5 Makes id-only reference in the given file into dita-compliant file#id
    6 references, using the mapping database generated by build_id_to_file_mapping.py.
    7 """
    8 
    9 __copyright__ = \
    10 """
    11 Copyright (C) 2023-2024 Oracle and/or its affiliates.
    12 
    13 This file is part of VirtualBox base platform packages, as
    14 available from https://www.virtualbox.org.
    15 
    16 This program is free software; you can redistribute it and/or
    17 modify it under the terms of the GNU General Public License
    18 as published by the Free Software Foundation, in version 3 of the
    19 License.
    20 
    21 This program is distributed in the hope that it will be useful, but
    22 WITHOUT ANY WARRANTY; without even the implied warranty of
    23 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    24 General Public License for more details.
    25 
    26 You should have received a copy of the GNU General Public License
    27 along with this program; if not, see <https://www.gnu.org/licenses>.
    28 
    29 SPDX-License-Identifier: GPL-3.0-only
    30 """
    31 __version__ = "$Revision$"
    32 
     1#!/usr/bin/env python3
    332
    343# Standard python imports.
    … …  
    4514    Modifies the href attributes in this file.
    4615    """
     16    current_file_is_refentry = False
     17    if any(current_file_name.lower() in s.lower() for s in refentry_files):
     18        current_file_is_refentry = True
    4719    sModified = '';
    4820    offPrev   = 0;
    … …  
    5022        sId = oMatch.group(1)[1:-1];
    5123        if sId in dIdToFile:
    52             sModified += sContent[offPrev : oMatch.start(1)] + '"' + dIdToFile[sId] + '#' + sId + '"';
     24            reference_is_refentry = False
     25            if any(os.path.splitext(dIdToFile[sId])[0].lower() in s.lower() for s in refentry_files):
     26                reference_is_refentry = True
     27            if current_file_is_refentry and not reference_is_refentry:
     28                 sModified += sContent[offPrev : oMatch.start(1)] + '"../topics/' + dIdToFile[sId] + '#' + sId + '"';
     29            else:
     30                sModified += sContent[offPrev : oMatch.start(1)] + '"' + dIdToFile[sId] + '#' + sId + '"';
     31            if sId == "vboxmanage-modifyvm-vrde":
     32                print("========*******=======")
     33                print(reference_is_refentry)
     34                print(current_file_name)
     35                print(current_file_is_refentry)
     36                print(dIdToFile[sId])
     37                print(f"ppppppp{sId}")
     38                print(refentry_files)
     39                print("========xxxxxxx=======")
     40
    5341            offPrev = oMatch.end(1);
    5442    if offPrev < len(sContent):
    … …  
    7765
    7866def main(asArgs):
    79     """
    80     C-like main function.
    81     """
    82     #
    83     # Process arguments.
    84     #
    8567    dIdToFile  = None;
    8668    fEndOfArgs = False;
    … …  
    10183            elif sArg in ('--verbose', '-v' ):
    10284                fVerbose = True;
     85            elif sArg in ('--refentry_file_list', '-f' ):
     86                iArg += 1;
     87                if iArg >= len(asArgs):
     88                    return syntax('Expected a list of refentry files following "--refentry_file_list"!');
     89                global refentry_files
     90                refentry_files = asArgs[iArg].split(' ')
    10391            elif sArg in ('--mapping-file', '-m'):
    10492                iArg += 1;
    … …  
    129117            except Exception as oXcpt: # pylint: disable=broad-exception-caught
    130118                return error('Failed to open and read "%s": %s' % (sArg, oXcpt,));
    131 
     119            global current_file_name
     120            current_file_name = os.path.splitext(os.path.basename(sArg))[0]
     121            prefix = "flat-"
     122            if current_file_name.startswith(prefix):
     123                current_file_name = current_file_name[len(prefix):]
    132124            sModified = modifyDitaFile(dIdToFile, sContent);
    133 
    134125            if sModified != sContent:
    135126                if fVerbose:
    … …  
    147138
    148139if __name__ == "__main__":
    149     sys.exit(main(sys.argv));
     140    main(sys.argv)
    150141

  • trunk/doc/manual/en_US/dita/UserManual.ditamap

    r106819 r107390  
    22<!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap.dtd">
    33<!-- The bookmap ID is imperative and matched the Jarvis GUID required to build and pretty much do anything -->
    4 <bookmap id="EN-VBOX-7-1-USER" xml:lang="en-US">
     4<bookmap id="EN-VBOX-7-2-USER" xml:lang="en-US">
    55   <booktitle>
    66      <mainbooktitle>Oracle VirtualBox: User Guide for Release 7.1</mainbooktitle>
    … …  
    1010         <published>
    1111            <completed>
    12           <month>September</month>
    13                <year>2024</year>
    14             </completed>
    15          </published>
    16       </publisherinformation>
     12          <month>December</month>
     13          <year>2024</year>
     14        </completed>
     15      </published>
     16    </publisherinformation>
    1717
    1818      <bookrights>
    1919         <copyrfirst>
    20             <year>2022</year>
    21          </copyrfirst>
    22          <bookowner>
    23             <organization>Oracle and/or its affiliates. All rights reserved.</organization>
    24          </bookowner>
    25       </bookrights>
    26    </bookmeta>
     20        <year>2024</year>
     21      </copyrfirst>
     22      <bookowner>
     23        <organization>Oracle and/or its affiliates. All rights reserved.</organization>
     24      </bookowner>
     25    </bookrights>
     26  </bookmeta>
    2727
    2828   <!-- Chunking should be set with chunk="to-content" in each chapter.  -->
    … …  
    3333          <figurelist/>
    3434          <tablelist/>
    35        </booklists>
    36       <preface href="topics/preface.dita" chunk="to-content">
    37          <topicref href="topics/preface-audience.dita"/>
    38          <topicref href="topics/preface-reldocs.dita"/>
    39          <topicref href="topics/preface-conventions.dita"/>
    40          <topicref href="topics/preface-doc-accessibility.dita"/>
    41          <topicref href="topics/preface-accessibility.dita"/>
    42          <topicref href="topics/preface-diversity.dita"/>
    43       </preface>
    44     </frontmatter>
    45       <chapter href="topics/Introduction.dita" chunk="to-content">
    46          <topicref href="topics/virt-why-useful.dita"/>
    47          <topicref href="topics/virtintro.dita"/>
     35    </booklists>
     36    <preface href="topics/preface.dita" chunk="to-content">
     37      <topicref href="topics/preface-audience.dita"/>
     38      <topicref href="topics/preface-reldocs.dita"/>
     39      <topicref href="topics/preface-conventions.dita"/>
     40      <topicref href="topics/preface-doc-accessibility.dita"/>
     41      <topicref href="topics/preface-accessibility.dita"/>
     42      <topicref href="topics/preface-diversity.dita"/>
     43    </preface>
     44  </frontmatter>
     45  <chapter href="topics/Introduction.dita" chunk="to-content">
     46    <topicref href="topics/virt-why-useful.dita"/>
     47    <topicref href="topics/virtintro.dita"/>
    4848    <topicref href="topics/features-overview.dita">
    4949      <topicref href="topics/frontends.dita"/>
    5050    </topicref>
    51          <topicref href="topics/hostossupport.dita">
     51    <topicref href="topics/guest-os.dita">
    5252         <topicref href="topics/host-guest-matrix.dita"/>
    53             <topicref href="topics/arm-host-limitations.dita"/>
    54             <topicref href="topics/hostcpurequirements.dita"/>
     53      <topicref href="topics/guest-os-x86-64.dita"/>
     54      <topicref href="topics/guest-os-Arm.dita"/>
     55      <topicref href="topics/intro-64bitguests.dita"/>
    5556         </topicref>
    5657         <topicref href="topics/intro-installing.dita"/>
    … …  
    9293            <topicref href="topics/ovf-export-appliance.dita"/>
    9394         </topicref>
    94          <topicref href="topics/cloud-integration.dita">
    95             <topicref href="topics/cloud-integration-steps.dita"/>
    96             <topicref href="topics/cloud-create-api-keypair.dita"/>
    97             <topicref href="topics/cloud-upload-public-key.dita"/>
    98             <topicref href="topics/cloud-create-cloud-profile.dita"/>
    99       <topicref href="topics/cloud-using-cloud-profile-manager.dita">
    100         <topicref href="topics/cloud-profile-creating.dita"/>
    101         <topicref href="topics/cloud-profile-importing.dita"/>
    102       </topicref>
    103             <topicref href="topics/cloud-vbox-oci-tasks.dita"/>
    104             <topicref href="topics/cloud-vm.dita">
    105                <topicref href="topics/cloud-vm-oci-group.dita"/>
    106                <topicref href="topics/cloud-vm-new.dita"/>
    107                <topicref href="topics/cloud-vm-add.dita"/>
    108                <topicref href="topics/cloud-vm-clone.dita"/>
    109                <topicref href="topics/cloud-vm-settings.dita"/>
    110                <topicref href="topics/cloud-vm-control.dita"/>
    111                <topicref href="topics/cloud-vm-monitor.dita"/>
    112                <topicref href="topics/cloud-vm-remove.dita"/>
    113                <topicref href="topics/cloud-vm-instance-console.dita"/>
    114             </topicref>
    115             <topicref href="topics/cloud-export-oci.dita">
    116                <topicref href="topics/cloud-export-oci-prepare-vm.dita"/>
    117             </topicref>
    118             <topicref href="topics/cloud-import-oci.dita">
    119                <topicref href="topics/import-instance-sequence.dita"/>
    120             </topicref>
    121             <topicref href="topics/cloud-using-cloud-networks.dita"/>
    122             <topicref href="topics/cloud-using-cli.dita"/>
    123          </topicref>
    12495         <topicref href="topics/soft-keyb.dita">
    12596            <topicref href="topics/soft-keyb-using.dita"/>
    … …  
    133104      </chapter>
    134105      <chapter href="topics/installation.dita" chunk="to-content">
     106    <topicref href="topics/installation-packages.dita">
     107      <topicref href="topics/hostcpurequirements.dita"/>
     108      <topicref href="topics/arm-host-limitations.dita"/>
     109    </topicref>
    135110         <topicref href="topics/installation_windows.dita">
    136111            <topicref href="topics/install-win-prereq.dita"/>
    … …  
    176151      </chapter>
    177152      <chapter href="topics/BasicConcepts.dita" chunk="to-content">
    178              <topicref href="topics/guest-os.dita">
    179              <topicref href="topics/guest-os-x86-64.dita"/>
    180              <topicref href="topics/guest-os-Arm.dita"/>
    181             <topicref href="topics/guest-os-legacy.dita"/>
    182             <topicref href="topics/intro-macosxguests.dita"/>
    183             <topicref href="topics/intro-64bitguests.dita"/>
    184          </topicref>
    185153         <topicref href="topics/basic-unattended.dita">
    186154            <topicref href="topics/unattended-guest-install-example.dita"/>
    … …  
    248216            <topicref href="topics/sf_mount_auto.dita"/>
    249217         </topicref>
    250          <topicref href="topics/guestadd-clipboard.dita">
    251             <topicref href="topics/guestadd-clipboard-limitations.dita"/>
    252          </topicref>
     218    <topicref href="topics/guestadd-clipboard.dita"/>
    253219         <topicref href="topics/guestadd-dnd.dita">
    254220            <topicref href="topics/guestadd-dnd-formats.dita"/>
    255             <topicref href="topics/guestadd-dnd-limitations.dita"/>
    256221         </topicref>
    257222         <topicref href="topics/guestadd-video.dita">
    … …  
    271236         </topicref>
    272237         <topicref href="topics/guestadd-resizing.dita">
    273             <topicref href="topics/guestadd-resizing-linux.dita">
    274                <topicref href="topics/guestadd-resizing-linux-limitations.dita"/>
     238      <topicref href="topics/guestadd-resizing-linux.dita"/>
     239    </topicref>
     240  </chapter>
     241  <chapter href="topics/cloud-integration.dita" chunk="to-content">
     242    <topicref href="topics/cloud-integration-steps.dita"/>
     243    <topicref href="topics/cloud-create-api-keypair.dita"/>
     244    <topicref href="topics/cloud-upload-public-key.dita"/>
     245    <topicref href="topics/cloud-create-cloud-profile.dita"/>
     246    <topicref href="topics/cloud-using-cloud-profile-manager.dita">
     247      <topicref href="topics/cloud-profile-creating.dita"/>
     248      <topicref href="topics/cloud-profile-importing.dita"/>
     249    </topicref>
     250    <topicref href="topics/cloud-vbox-oci-tasks.dita"/>
     251    <topicref href="topics/cloud-vm.dita">
     252      <topicref href="topics/cloud-vm-oci-group.dita"/>
     253      <topicref href="topics/cloud-vm-new.dita"/>
     254      <topicref href="topics/cloud-vm-add.dita"/>
     255      <topicref href="topics/cloud-vm-clone.dita"/>
     256      <topicref href="topics/cloud-vm-settings.dita"/>
     257      <topicref href="topics/cloud-vm-control.dita"/>
     258      <topicref href="topics/cloud-vm-monitor.dita"/>
     259      <topicref href="topics/cloud-vm-remove.dita"/>
     260      <topicref href="topics/cloud-vm-instance-console.dita"/>
    275261            </topicref>
    276          </topicref>
     262    <topicref href="topics/cloud-export-oci.dita">
     263      <topicref href="topics/cloud-export-oci-prepare-vm.dita"/>
     264         </topicref>
     265    <topicref href="topics/cloud-import-oci.dita">
     266      <topicref href="topics/import-instance-sequence.dita"/>
     267    </topicref>
     268    <topicref href="topics/cloud-using-cloud-networks.dita"/>
     269    <topicref href="topics/cloud-using-cli.dita"/>
    277270      </chapter>
    278271      <chapter href="topics/storage.dita" chunk="to-content">
    … …  
    323316      <topicref href="topics/vrde.dita">
    324317         <topicref href="topics/rdp-viewers.dita"/>
    325          <topicref href="topics/vboxheadless.dita"/>
     318      <topicref href="topics/headless-mode.dita"/>
    326319         <topicref href="topics/headless-vm-steps.dita"/>
    327          <topicref href="topics/vboxheadless-separate-mode.dita"/>
     320      <topicref href="topics/separate-mode.dita"/>
    328321         <topicref href="topics/usb-over-rdp.dita"/>
    329322         <topicref href="topics/vbox-auth.dita"/>
    … …  
    335328      </topicref>
    336329      <topicref href="topics/teleporting.dita"/>
    337       <topicref format="ditamap" href="topics/man_VBoxHeadless.ditamap"/>
     330      <topicref format="ditamap" href="cli_topics/man_VBoxHeadless.ditamap"/>
    338331   </chapter>
    339332
    … …  
    342335      <topicref href="topics/vboxmanage-intro.dita"/>
    343336      <!-- Commands Overview -->
    344       <topicref href="topics/vboxmanage-cmd-overview.dita"/>
     337      <!-- <topicref href="cli_topics/vboxmanage-cmd-overview.dita"/> -->
    345338      <!-- The remainder of the topics in this chapter are generated from docbook XML files.-->
    346       <topicref format="ditamap" href="topics/man_VBoxManage-common.ditamap"/>
     339      <topicref format="ditamap" href="cli_topics/man_VBoxManage-common.ditamap"/>
    347340      <!-- Note! We sort these alphabetical unless someone can define a
    348341                 maintainable ordering (previously it seemed to be total
    349342                 random and included several duplicates). -->
    350       <topicref format="ditamap" href="topics/man_VBoxManage-adoptstate.ditamap"/>
    351       <topicref format="ditamap" href="topics/man_VBoxManage-bandwidthctl.ditamap"/>
    352       <topicref format="ditamap" href="topics/man_VBoxManage-checkmediumpwd.ditamap"/>
    353       <topicref format="ditamap" href="topics/man_VBoxManage-clonemedium.ditamap"/>
    354       <topicref format="ditamap" href="topics/man_VBoxManage-clonevm.ditamap"/>
    355       <topicref format="ditamap" href="topics/man_VBoxManage-closemedium.ditamap"/>
    356       <topicref format="ditamap" href="topics/man_VBoxManage-cloud.ditamap"/>
    357       <topicref format="ditamap" href="topics/man_VBoxManage-cloudprofile.ditamap"/>
    358       <topicref format="ditamap" href="topics/man_VBoxManage-controlvm.ditamap"/>
    359       <topicref format="ditamap" href="topics/man_VBoxManage-convertfromraw.ditamap"/>
    360       <topicref format="ditamap" href="topics/man_VBoxManage-createmedium.ditamap"/>
    361       <topicref format="ditamap" href="topics/man_VBoxManage-createvm.ditamap"/>
    362       <topicref format="ditamap" href="topics/man_VBoxManage-debugvm.ditamap"/>
    363       <topicref format="ditamap" href="topics/man_VBoxManage-dhcpserver.ditamap"/>
    364       <topicref format="ditamap" href="topics/man_VBoxManage-discardstate.ditamap"/>
    365       <topicref format="ditamap" href="topics/man_VBoxManage-encryptmedium.ditamap"/>
    366       <topicref format="ditamap" href="topics/man_VBoxManage-encryptvm.ditamap"/>
    367       <topicref format="ditamap" href="topics/man_VBoxManage-export.ditamap"/>
    368       <topicref format="ditamap" href="topics/man_VBoxManage-extpack.ditamap"/>
    369       <topicref format="ditamap" href="topics/man_VBoxManage-getextradata.ditamap"/>
    370       <topicref format="ditamap" href="topics/man_VBoxManage-guestcontrol.ditamap"/>
    371       <topicref format="ditamap" href="topics/man_VBoxManage-guestproperty.ditamap"/>
    372       <topicref format="ditamap" href="topics/man_VBoxManage-hostonlyif.ditamap"/>
    373       <topicref format="ditamap" href="topics/man_VBoxManage-hostonlynet.ditamap"/>
    374       <topicref format="ditamap" href="topics/man_VBoxManage-import.ditamap"/>
    375       <topicref format="ditamap" href="topics/man_VBoxManage-list.ditamap"/>
    376       <topicref format="ditamap" href="topics/man_VBoxManage-mediumio.ditamap"/>
    377       <topicref format="ditamap" href="topics/man_VBoxManage-mediumproperty.ditamap"/>
    378       <topicref format="ditamap" href="topics/man_VBoxManage-metrics.ditamap"/>
    379       <topicref format="ditamap" href="topics/man_VBoxManage-modifymedium.ditamap"/>
    380       <topicref format="ditamap" href="topics/man_VBoxManage-modifynvram.ditamap"/>
    381       <topicref format="ditamap" href="topics/man_VBoxManage-modifyvm.ditamap"/>
    382       <topicref format="ditamap" href="topics/man_VBoxManage-movevm.ditamap"/>
    383       <topicref format="ditamap" href="topics/man_VBoxManage-natnetwork.ditamap"/>
    384       <topicref format="ditamap" href="topics/man_VBoxManage-registervm.ditamap"/>
    385       <topicref format="ditamap" href="topics/man_VBoxManage-setextradata.ditamap"/>
    386       <topicref format="ditamap" href="topics/man_VBoxManage-setproperty.ditamap"/>
    387       <topicref format="ditamap" href="topics/man_VBoxManage-sharedfolder.ditamap"/>
    388       <topicref format="ditamap" href="topics/man_VBoxManage-showmediuminfo.ditamap"/>
    389       <topicref format="ditamap" href="topics/man_VBoxManage-showvminfo.ditamap"/>
    390       <topicref format="ditamap" href="topics/man_VBoxManage-signova.ditamap"/>
    391       <topicref format="ditamap" href="topics/man_VBoxManage-snapshot.ditamap"/>
    392       <topicref format="ditamap" href="topics/man_VBoxManage-startvm.ditamap"/>
    393       <topicref format="ditamap" href="topics/man_VBoxManage-storageattach.ditamap"/>
    394       <topicref format="ditamap" href="topics/man_VBoxManage-storagectl.ditamap"/>
    395       <topicref format="ditamap" href="topics/man_VBoxManage-unattended.ditamap"/>
    396       <topicref format="ditamap" href="topics/man_VBoxManage-unregistervm.ditamap"/>
    397       <topicref format="ditamap" href="topics/man_VBoxManage-updatecheck.ditamap"/>
    398       <topicref format="ditamap" href="topics/man_VBoxManage-usbdevsource.ditamap"/>
    399       <topicref format="ditamap" href="topics/man_VBoxManage-usbfilter.ditamap"/>
     343      <topicref format="ditamap" href="cli_topics/man_VBoxManage-adoptstate.ditamap"/>
     344      <topicref format="ditamap" href="cli_topics/man_VBoxManage-bandwidthctl.ditamap"/>
     345      <topicref format="ditamap" href="cli_topics/man_VBoxManage-checkmediumpwd.ditamap"/>
     346      <topicref format="ditamap" href="cli_topics/man_VBoxManage-clonemedium.ditamap"/>
     347      <topicref format="ditamap" href="cli_topics/man_VBoxManage-clonevm.ditamap"/>
     348      <topicref format="ditamap" href="cli_topics/man_VBoxManage-closemedium.ditamap"/>
     349      <topicref format="ditamap" href="cli_topics/man_VBoxManage-cloud.ditamap"/>
     350      <topicref format="ditamap" href="cli_topics/man_VBoxManage-cloudprofile.ditamap"/>
     351      <topicref format="ditamap" href="cli_topics/man_VBoxManage-controlvm.ditamap"/>
     352      <topicref format="ditamap" href="cli_topics/man_VBoxManage-convertfromraw.ditamap"/>
     353      <topicref format="ditamap" href="cli_topics/man_VBoxManage-createmedium.ditamap"/>
     354      <topicref format="ditamap" href="cli_topics/man_VBoxManage-createvm.ditamap"/>
     355      <topicref format="ditamap" href="cli_topics/man_VBoxManage-debugvm.ditamap"/>
     356      <topicref format="ditamap" href="cli_topics/man_VBoxManage-dhcpserver.ditamap"/>
     357      <topicref format="ditamap" href="cli_topics/man_VBoxManage-discardstate.ditamap"/>
     358      <topicref format="ditamap" href="cli_topics/man_VBoxManage-encryptmedium.ditamap"/>
     359      <topicref format="ditamap" href="cli_topics/man_VBoxManage-encryptvm.ditamap"/>
     360      <topicref format="ditamap" href="cli_topics/man_VBoxManage-export.ditamap"/>
     361      <topicref format="ditamap" href="cli_topics/man_VBoxManage-extpack.ditamap"/>
     362      <topicref format="ditamap" href="cli_topics/man_VBoxManage-getextradata.ditamap"/>
     363      <topicref format="ditamap" href="cli_topics/man_VBoxManage-guestcontrol.ditamap"/>
     364      <topicref format="ditamap" href="cli_topics/man_VBoxManage-guestproperty.ditamap"/>
     365      <topicref format="ditamap" href="cli_topics/man_VBoxManage-hostonlyif.ditamap"/>
     366      <topicref format="ditamap" href="cli_topics/man_VBoxManage-hostonlynet.ditamap"/>
     367      <topicref format="ditamap" href="cli_topics/man_VBoxManage-import.ditamap"/>
     368      <topicref format="ditamap" href="cli_topics/man_VBoxManage-list.ditamap"/>
     369      <topicref format="ditamap" href="cli_topics/man_VBoxManage-mediumio.ditamap"/>
     370      <topicref format="ditamap" href="cli_topics/man_VBoxManage-mediumproperty.ditamap"/>
     371      <topicref format="ditamap" href="cli_topics/man_VBoxManage-metrics.ditamap"/>
     372      <topicref format="ditamap" href="cli_topics/man_VBoxManage-modifymedium.ditamap"/>
     373      <topicref format="ditamap" href="cli_topics/man_VBoxManage-modifynvram.ditamap"/>
     374      <topicref format="ditamap" href="cli_topics/man_VBoxManage-modifyvm.ditamap"/>
     375      <topicref format="ditamap" href="cli_topics/man_VBoxManage-movevm.ditamap"/>
     376      <topicref format="ditamap" href="cli_topics/man_VBoxManage-natnetwork.ditamap"/>
     377      <topicref format="ditamap" href="cli_topics/man_VBoxManage-registervm.ditamap"/>
     378      <topicref format="ditamap" href="cli_topics/man_VBoxManage-setextradata.ditamap"/>
     379      <topicref format="ditamap" href="cli_topics/man_VBoxManage-setproperty.ditamap"/>
     380      <topicref format="ditamap" href="cli_topics/man_VBoxManage-sharedfolder.ditamap"/>
     381      <topicref format="ditamap" href="cli_topics/man_VBoxManage-showmediuminfo.ditamap"/>
     382      <topicref format="ditamap" href="cli_topics/man_VBoxManage-showvminfo.ditamap"/>
     383      <topicref format="ditamap" href="cli_topics/man_VBoxManage-signova.ditamap"/>
     384      <topicref format="ditamap" href="cli_topics/man_VBoxManage-snapshot.ditamap"/>
     385      <topicref format="ditamap" href="cli_topics/man_VBoxManage-startvm.ditamap"/>
     386      <topicref format="ditamap" href="cli_topics/man_VBoxManage-storageattach.ditamap"/>
     387      <topicref format="ditamap" href="cli_topics/man_VBoxManage-storagectl.ditamap"/>
     388      <topicref format="ditamap" href="cli_topics/man_VBoxManage-unattended.ditamap"/>
     389      <topicref format="ditamap" href="cli_topics/man_VBoxManage-unregistervm.ditamap"/>
     390      <topicref format="ditamap" href="cli_topics/man_VBoxManage-updatecheck.ditamap"/>
     391      <topicref format="ditamap" href="cli_topics/man_VBoxManage-usbdevsource.ditamap"/>
     392      <topicref format="ditamap" href="cli_topics/man_VBoxManage-usbfilter.ditamap"/>
    400393      <!-- End sorted manpage topics. -->
    401       <topicref format="ditamap" href="topics/man_vboximg-mount.ditamap"/>
     394      <topicref format="ditamap" href="cli_topics/man_vboximg-mount.ditamap"/>
    402395   </chapter>
    403396
    … …  
    526519         <topicref href="topics/vboxsvc-session-0-known-issues.dita"/>
    527520      </topicref>
    528       <topicref format="ditamap" href="topics/user_isomakercmd-man.ditamap"/>
     521      <topicref format="ditamap" href="cli_topics/user_isomakercmd-man.ditamap"/>
    529522   </chapter>
    530523   <chapter href="topics/TechnicalBackground.dita" chunk="to-content">
    … …  
    545538
    546539   <chapter href="topics/Troubleshooting.dita" chunk="to-content">
    547       <topicref href="topics/ts_procs-tools.dita">
    548540         <topicref href="topics/ts_categorize-isolate.dita"/>
    549541         <topicref href="topics/collect-debug-info.dita"/>
    … …  
    551543         <topicref href="topics/ts_debugger.dita"/>
    552544         <topicref href="topics/ts_guest-core-format.dita"/>
    553       </topicref>
     545    <topicref href="topics/ts_win-host-com-server.dita"/>
     546    <topicref href="topics/ts_linux-guest-x11-services.dita"/>
     547    <topicref href="topics/ts_legacy-os.dita">
     548      <topicref href="topics/ts_boot-issues-ide.dita"/>
     549      <topicref href="topics/ts_win7-guest-usb3-support.dita"/>
     550      <topicref href="topics/ts_win-guest-bluescreen.dita"/>
     551      <topicref href="topics/ts_linux-buggy.dita"/>
     552      <topicref href="topics/ts_solaris-10-guest-slow-boot-smp.dita"/>
     553      <topicref href="topics/ts_solaris-no-e1000-bm.dita"/>
     554      </topicref>
     555    <topicref href="topics/known-issues.dita">
    554556      <topicref href="topics/ts_general.dita">
    555557         <topicref href="topics/ts_config-periodic-flush.dita"/>
    … …  
    559561         <topicref href="topics/ts_win-cpu-usage-rept.dita"/>
    560562         <topicref href="topics/ts_host-powermgmt.dita"/>
     563        <topicref href="topics/ts_guest-smp-limitations.dita"/>
     564        <topicref href="topics/ts_virtual-disk-compacting.dita"/>
     565        <topicref href="topics/ts_scale-mode.dita"/>
     566        <topicref href="topics/guestadd-dnd-limitations.dita"/>
    561567      </topicref>
    562568      <topicref href="topics/ts_win-guests.dita">
    563          <topicref href="topics/ts_win7-guest-usb3-support.dita"/>
    564          <topicref href="topics/ts_win-guest-bluescreen.dita"/>
    565          <topicref href="topics/ts_win-guest-bluescreen-smp.dita"/>
    566569         <topicref href="topics/ts_win2k-guest-install.dita"/>
    567570         <topicref href="topics/ts_win-guest-bluescreen-record-info.dita"/>
    … …  
    572575         <topicref href="topics/ts_win-guest-active-dir-domain.dita"/>
    573576         <topicref href="topics/ts_win31-ram-limitations.dita"/>
     577        <topicref href="topics/ts_guest-control.dita"/>
     578        <topicref href="topics/ts_slow-transmission-win-xp-guests.dita"/>
    574579      </topicref>
    575580      <topicref href="topics/ts_lin-x11-guests.dita">
    576581         <topicref href="topics/ts_linux-guest-high-cpu.dita"/>
    577          <topicref href="topics/ts_linux-buggy.dita"/>
    578          <topicref href="topics/ts_linux-guest-x11-services.dita"/>
    579       </topicref>
    580       <topicref href="topics/ts_sol-guests.dita">
    581          <topicref href="topics/ts_solaris-10-guest-slow-boot-smp.dita"/>
    582          <topicref href="topics/ts_solaris-no-e1000-bm.dita"/>
     582        <topicref href="topics/guestadd-resizing-linux-limitations.dita"/>
     583      </topicref>
     584      <topicref href="topics/ts_arm-guests.dita">
     585        <topicref href="topics/ts_saved-states.dita"/>
    583586      </topicref>
    584587      <topicref href="topics/ts_win-hosts.dita">
    585          <topicref href="topics/ts_win-dnd-uipi.dita"/>
    586          <topicref href="topics/ts_win-host-com-server.dita"/>
    587588         <topicref href="topics/ts_win-host-cd-dvd-changes.dita"/>
    588589         <topicref href="topics/ts_win-host-rdp-client.dita"/>
    … …  
    590591         <topicref href="topics/ts_win-host-bridged-network-adapters.dita"/>
    591592         <topicref href="topics/ts_win-host-host-only-network-adapters.dita"/>
     593        <topicref href="topics/ts_hyperv.dita"/>
    592594      </topicref>
    593595      <topicref href="topics/ts_lin-hosts.dita">
    … …  
    602604      <topicref href="topics/ts_sol-hosts.dita">
    603605         <topicref href="topics/ts_sol-host-zfs.dita"/>
     606        <topicref href="topics/ts_solaris-limitations.dita"/>
     607      </topicref>
     608      <topicref href="topics/ts_macos-hosts.dita">
     609        <topicref href="topics/ts_int-net.dita"/>
     610        <topicref href="topics/ts_macos-limitations.dita"/>
     611      </topicref>
    604612      </topicref>
    605613   </chapter>
    … …  
    637645      </topicref>
    638646   </chapter>
    639 
    640    <chapter href="topics/KnownIssues.dita" chunk="to-content">
    641       <topicref href="topics/ExperimentalFeatures.dita"/>
    642       <topicref href="topics/KnownProblems.dita"/>
    643    </chapter>
    644 
     647  <chapter href="topics/reference.dita" chunk="to-content">
     648    <topicref href="topics/ExperimentalFeatures.dita">
     649      <topicref href="topics/macosxguests.dita"/>
     650    </topicref>
     651    <topicref href="topics/privacy.dita"/>
     652  </chapter>
    645653   <!-- Change Log -->
    646654   <chapter href="topics/ChangeLog.dita" chunk="to-content">
    … …  
    655663   </chapter>
    656664
    657    <chapter href="topics/privacy.dita" chunk="to-content"/>
    658 
    659 
    660665</bookmap>

  • trunk/doc/manual/en_US/dita/topics/ExperimentalFeatures.dita

    r105941 r107390  
    2525      <li>
    2626        <p>
    27           EFI firmware
    28         </p>
    29       </li>
    30       <li>
    31         <p>
    3227          Host CD/DVD drive passthrough
    3328        </p>

  • trunk/doc/manual/en_US/dita/topics/Security.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/TechnicalBackground.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/Troubleshooting.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99797 r107390  
    55 
    66  <body>
    7     <p>
    8     This chapter provides answers to commonly asked questions. In order
    9     to improve your user experience with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, it is
    10     recommended to read this section to learn more about common pitfalls
    11     and get recommendations on how to use the product.
    12   </p>
     7    <p>Identify and address common issues that can occur while working with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p>
    138  </body>
    149</topic>

  • trunk/doc/manual/en_US/dita/topics/VirtualBoxAPI.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/additions-os2.dita

    r99797 r107390  
    66  <body>
    77    <p>
    8         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also ships with a set of drivers that improve
    9         running OS/2 in a virtual machine. Due to restrictions of OS/2
    10         itself, this variant of the Guest Additions has a limited
    11         feature set. See <xref href="KnownIssues.dita">Known Limitations</xref> for details.
    12       </p>
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also ships with a set of drivers that improve running OS/2 in a virtual machine. Due to restrictions of OS/2 itself, this variant of the Guest Additions has a limited feature set. Specifically, seamless windows and automatic guest resizing are not implemented in Guest Additions for OS/2 because of inherent limitations of the OS/2 graphics system.</p>
    139    <p>
    1410        The OS/2 Guest Additions are provided on the same ISO CD-ROM as

  • trunk/doc/manual/en_US/dita/topics/arm-host-limitations.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/auth-config-using.dita

    r105303 r107390  
    1111    <ul>
    1212      <li>
    13         <p> When using remote iSCSI storage and the storage server requires authentication, an
    14           initiator secret can optionally be supplied with the <userinput>VBoxManage
    15             storageattach</userinput> command. As long as no settings password is provided, by using
    16           the command line option <codeph>--settingspwfile</codeph>, then this secret is stored
    17             <i>unencrypted</i> in the machine configuration and is therefore potentially readable on
    18           the host. See <xref href="storage-iscsi.dita">iSCSI Servers</xref> and <xref
    19             href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>. </p>
     13        <p> When using remote iSCSI storage and the storage server requires authentication, an initiator secret can optionally be supplied with the <userinput>VBoxManage storageattach</userinput> command. As long as no settings password is provided, by using the command line option <codeph>--settingspwfile</codeph>, then this secret is stored <i>unencrypted</i> in the machine configuration and is therefore potentially readable on the host. See <xref href="storage-iscsi.dita">iSCSI Servers</xref> and <xref href="../cli_topics/vboxmanage-storageattach.dita"/>.</p>
    2014      </li>
    2115      <li>

  • trunk/doc/manual/en_US/dita/topics/clone.dita

    r105388 r107390  
    4646    <p>The duration of the clone operation depends on the size and number of attached disk images. In addition, the
    4747      clone operation saves all the differencing disk images of a snapshot. </p>
    48     <p>You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See <xref
    49         href="vboxmanage-clonevm.dita"/>. </p>
     48    <p>You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See <xref href="../cli_topics/vboxmanage-clonevm.dita"/>.</p>
    5049  </body>
    5150 

  • trunk/doc/manual/en_US/dita/topics/cloningvdis.dita

    r105335 r107390  
    55 
    66  <body>
    7     <p>You can duplicate hard disk image files on the same host to quickly produce a second virtual machine with the
    8       same OS setup. However, you should <i>only</i> make copies of virtual disk images using the utility supplied with
    9         <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See <xref href="vboxmanage-clonemedium.dita"/>. This is
    10       because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a UUID to each disk image, which is also
    11       stored inside the image, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will refuse to work with two
    12       images that use the same number. If you do accidentally try to reimport a disk image which you copied normally,
    13       you can make a second copy using the <userinput>VBoxManage clonevm</userinput> command and import that instead. </p>
     7    <p>You can duplicate hard disk image files on the same host to quickly produce a second virtual machine with the same OS setup. However, you should <i>only</i> make copies of virtual disk images using the utility supplied with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See <xref href="../cli_topics/vboxmanage-clonemedium.dita"/>. This is because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a UUID to each disk image, which is also stored inside the image, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will refuse to work with two images that use the same number. If you do accidentally try to reimport a disk image which you copied normally, you can make a second copy using the <userinput>VBoxManage clonevm</userinput> command and import that instead. </p>
    148    <p>Note that Linux distributions identify the boot hard disk from the ID of the drive. The ID <ph
    159        conkeyref="vbox-conkeyref-phrases/product-name"/> reports for a drive is determined from the UUID of the virtual

  • trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita

    r105303 r107390  
    7777      </li>
    7878      <li>
    79         <p>Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See <xref
    80             href="vboxmanage-cloudprofile.dita"/>. </p>
     79        <p>Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See <xref href="../cli_topics/vboxmanage-cloudprofile.dita"/>. </p>
    8180      </li>
    8281      <li>

  • trunk/doc/manual/en_US/dita/topics/cloud-export-oci.dita

    r105814 r107390  
    8383      </li>
    8484    </ol>
    85     <p>You can also use the <userinput>VBoxManage export</userinput> command to export a VM to <ph
    86         conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-export.dita"/>. </p>
     85    <p>You can also use the <userinput>VBoxManage export</userinput> command to export a VM to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="../cli_topics/vboxmanage-export.dita"/>.</p>
    8786  </body>
    8887</topic>

  • trunk/doc/manual/en_US/dita/topics/cloud-import-oci.dita

    r105573 r107390  
    2828      </li>
    2929    </ol>
    30     <p>You can also use the <userinput>VBoxManage import</userinput> command to import an instance from <ph
    31         conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-import.dita"/>. </p>
     30    <p>You can also use the <userinput>VBoxManage import</userinput> command to import an instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="../cli_topics/vboxmanage-import.dita"/>.</p>
    3231  </body>
    3332</topic>

  • trunk/doc/manual/en_US/dita/topics/cloud-profile-creating.dita

    r105791 r107390  
    66        <ol id="ol_v4q_hgm_gcc">
    77            <li>
    8                 <p>Click the <b outputclass="bold">Add</b> icon and specify a <b outputclass="bold">Name</b> for the
    9                     profile. </p>
     8                <p>Click <b outputclass="bold">Add</b> and specify a <b outputclass="bold">Name</b> for the profile. </p>
    109            </li>
    1110            <li>
    12                 <p>Click <b outputclass="bold">Properties</b> and specify the following property values for the profile: </p>
     11                <p>Select the new profile, and then click <b outputclass="bold">Properties</b>. Specify the following property values for the profile: </p>
    1312                <ul id="ul_w4q_hgm_gcc">
    1413                    <li>
    … …  
    4645            </li>
    4746        </ol>
     47        <p>You can also use <codeph>VBoxManage cloudprofile</codeph> to create a cloud profile. See  <xref href="cloud-using-cli.dita"/>.</p>
    4848    </body>
    4949</topic>

  • trunk/doc/manual/en_US/dita/topics/cloud-profile-importing.dita

    r105618 r107390  
    11<?xml version="1.0" encoding="UTF-8"?>
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    3 <topic id="cloud_profile_creating">
     3<topic id="cloud_profile_importing">
    44    <title>Importing a Cloud Profile</title>
    55    <body>
    6         <p>Follow these steps to import an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration file into
    7             the Cloud Profile Manager: </p>
     6        <p>Follow these steps to import an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration file into the Cloud Profile Manager: </p>
    87        <ol id="ol_yvv_mgm_gcc">
    98            <li>
    10                 <p>Ensure that a <filepath>config</filepath> file is present in your <ph
    11                         conkeyref="vbox-conkeyref-phrases/oci"/> configuration directory. For example, this is
    12                         <filepath>$HOME/.oci/config</filepath> on a Linux host. </p>
     9                <p>Ensure that a <filepath>config</filepath> file is present in your <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration directory. For example, this is <filepath>$HOME/.oci/config</filepath> on a Linux host. </p>
    1310            </li>
    1411            <li>
    15                 <p>Click the <b outputclass="bold">Import</b> icon to open a dialog that prompts you to import cloud
    16                     profiles from external files. </p>
     12                <p>Click the <b outputclass="bold">Import</b> icon to open a dialog that prompts you to import cloud profiles from external files. </p>
    1713                <note id="note_zvv_mgm_gcc">
    18                     <p>This action overwrites any cloud profiles that are in your <ph
    19                             conkeyref="vbox-conkeyref-phrases/product-name"/> global settings directory. </p>
     14                    <p>This action overwrites any cloud profiles that are in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global settings directory. </p>
    2015                </note>
    2116            </li>
    2217            <li>
    2318                <p>Click <b outputclass="bold">Import</b>. </p>
    24                 <p>Your cloud profile settings are saved to the <filepath>oci_config</filepath> file in your <ph
    25                         conkeyref="vbox-conkeyref-phrases/product-name"/> global settings directory. </p>
     19                <p>Your cloud profile settings are saved to the <filepath>oci_config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global settings directory. </p>
    2620            </li>
    2721            <li>

  • trunk/doc/manual/en_US/dita/topics/cloud-using-cli.dita

    r105289 r107390  
    88      with <ph conkeyref="vbox-conkeyref-phrases/oci"/> and perform common cloud operations. </p>
    99    <p><b outputclass="bold">Creating a Cloud Profile</b>
    10       </p>
    11     <p>To create a cloud profile called <codeph>vbox-oci</codeph>: </p>
     10    </p>
     11    <p>To create a cloud profile called <codeph>vbox-oci</codeph> for <ph conkeyref="vbox-conkeyref-phrases/oci"/> as the cloud provider: </p>
    1212    <pre xml:space="preserve">VBoxManage cloudprofile --provider "OCI" --profile="vbox-oci" add \
    1313--clouduser="ocid1.user.oc1..."  --keyfile="/home/username/.oci/oci_api_key.pem" \
    1414--tenancy="ocid1.tenancy.oc1..."  --compartment="ocid1.compartment.oc1..."  --region="us-ashburn-1"
    1515</pre>
    16     <p>The new cloud profile is added to the <filepath>oci_config</filepath> file in your <ph
    17         conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory. For example, this is
    18         <filepath>$HOME/.VirtualBox/oci_config</filepath> on a Windows host. </p>
     16    <p>The new cloud profile is added to the <filepath>oci_config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory. For example, this is <filepath>$HOME/.VirtualBox/oci_config</filepath> on a Windows host.</p>
    1917    <p><b outputclass="bold">Listing Cloud Instances</b>
    20       </p>
     18    </p>
    2119    <p>To list the instances in your <ph conkeyref="vbox-conkeyref-phrases/oci"/> compartment: </p>
    2220    <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" list instances
    … …  
    5553    <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance metricdata \
    5654--id="ocid1.instance.oc1..." --metric-name="CpuUtilization"</pre> 
    57     <p>For more details about the available commands for cloud operations, see <xref href="vboxmanage-cloud.dita"/>. </p>
     55    <p>For more details about the available commands for cloud operations, see <xref href="../cli_topics/vboxmanage-cloud.dita"/>.</p>
    5856  </body>
    5957 

  • trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita

    r105303 r107390  
    2121            <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" network setup</pre>
    2222            <p>where <codeph>vbox-oci</codeph> is the name of your cloud profile. </p>
    23             <p>Other options are available for the <userinput>VBoxManage cloud network setup</userinput> command, to
    24               enable you to configure details for the VCN. For example, you can configure the operating system used for
    25               the cloud gateway instance and the IP address range used by the tunneling network. See <xref
    26                 href="vboxmanage-cloud.dita"/>. </p>
     23            <p>Other options are available for the <userinput>VBoxManage cloud network setup</userinput> command, to enable you to configure details for the VCN. For example, you can configure the operating system used for the cloud gateway instance and the IP address range used by the tunneling network. See <xref href="../cli_topics/vboxmanage-cloud.dita"/>. </p>
    2724            <p>For best results, use an Oracle Linux 7 instance for the cloud gateway. This is the default option. </p>
    2825          </li>

  • trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita

    r105618 r107390  
    55 
    66  <body>
    7     <p>To open the Cloud Profile Manager click <b outputclass="bold">File</b>, <b outputclass="bold">Cloud Profile
    8         Manager</b> in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
     7    <p>To open the Cloud Profile Manager click <b outputclass="bold">File</b>, <b>Tools</b>, <b outputclass="bold">Cloud Profile Manager</b> in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
    98    <p>You can use the Cloud Profile Manager in the following ways: </p>
    109    <ul>

  • trunk/doc/manual/en_US/dita/topics/cloud-vm-clone.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/cloud-vm-monitor.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105941 r107390  
    2323              instance.</p></li>
    2424        <li><p><cmdname>VBoxManage cloud instance metricdata</cmdname> shows metrics data for an instance.</p></li></ul>
    25         <p>See also <xref href="vboxmanage-cloud.dita"/>.</p>
     25        <p>See also <xref href="../cli_topics/vboxmanage-cloud.dita"/>.</p>
    2626      </li></ul>
    2727    <note><p>To monitor a cloud VM, the Compute Instance Monitoring plugin must be enabled and running on the

  • trunk/doc/manual/en_US/dita/topics/collect-debug-info.dita

    r105303 r107390  
    55 
    66  <body>
    7     <p>
    8         For problem determination, it is often important to collect
    9         debugging information which can be analyzed by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    10         support. This section contains information about what kind of
    11         information can be obtained.
    12       </p>
    13     <p>
    14         Every time <ph conkeyref="vbox-conkeyref-phrases/product-name"/> starts up a VM, a so-called
    15         <i>release log file</i> is created, containing
    16         lots of information about the VM configuration and runtime
    17         events. The log file is called <filepath>VBox.log</filepath> and
    18         resides in the VM log file folder, which is
    19         <filepath>$HOME/VirtualBox
    20         VMs/<varname>VM-name</varname>/Logs</filepath> by
    21         default.
    22       </p>
    23     <p>
    24         When starting a VM, the configuration file of the last run will
    25         be renamed to <filepath>.1</filepath>, up to
    26         <filepath>.3</filepath>. Sometimes when there is a problem, it
    27         is useful to have a look at the logs. Also when requesting
    28         support for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, supplying the corresponding log file
    29         is mandatory.
    30       </p>
    31     <p>
    32         For convenience, for each virtual machine, <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> can show
    33         these logs in a window. Select a virtual machine from the
    34         machine list on the left and click
    35         <b outputclass="bold">Logs</b> in the machine tools menu.
    36       </p>
    37     <p>
    38         The release log file, <filepath>VBox.log</filepath>, contains a
    39         wealth of diagnostic information, such as Host OS type and
    40         version, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version and build. It also includes a
    41         complete dump of the guest's configuration (CFGM), detailed
    42         information about the host CPU type and supported features,
    43         whether hardware virtualization is enabled, information about
    44         VT-x/AMD-V setup, state transitions (such as creating, running,
    45         paused, stopping), guest BIOS messages, Guest Additions
    46         messages, device-specific log entries and, at the end of
    47         execution, final guest state and condensed statistics.
    48       </p>
    49     <p>
    50         In case of crashes, it is very important to collect
    51         <i>crash dumps</i>. This is true for both host and
    52         guest crashes. For information about enabling core dumps on
    53         Linux, Oracle Solaris, and macOS systems, refer to the following
    54         core dump article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website:
    55       </p>
    56     <p><ph>http://www.virtualbox.org/wiki/Core_dump</ph>.
    57       </p>
    58     <p> You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete
    59       virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>. </p>
    60     <p>
    61         For network related problems, it is often helpful to capture a
    62         trace of network traffic. If the traffic is routed through an
    63         adapter on the host, it is possible to use Wireshark or a
    64         similar tool to capture the traffic there. However, this often
    65         also includes a lot of traffic unrelated to the VM.
    66       </p>
    67     <p>
    68         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides an ability to capture network traffic
    69         only on a specific VM's network adapter. Refer to the following
    70         network tracing article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website for
    71         information on enabling this capture:
    72       </p>
    73     <p><ph>http://www.virtualbox.org/wiki/Network_tips</ph>.
    74       </p>
    75     <p>
    76         The trace files created by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> are in
    77         <filepath>.pcap</filepath> format and can be easily analyzed
    78         with Wireshark.
    79       </p>
     7    <p>For problem determination, it is often important to collect debugging information which can be analyzed by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> support. This section contains information about what kind of information can be obtained.</p>
     8    <p>Every time <ph conkeyref="vbox-conkeyref-phrases/product-name"/> starts up a VM, a so-called <i>release log file</i> is created, containing lots of information about the VM configuration and runtime events. The log file is called <filepath>VBox.log</filepath> and resides in the VM log file folder, which is <filepath>$HOME/VirtualBox VMs/<varname>VM-name</varname>/Logs</filepath> by default.</p>
     9    <p>When starting a VM, the configuration file of the last run will be renamed to <filepath>.1</filepath>, up to <filepath>.3</filepath>. Sometimes when there is a problem, it is useful to have a look at the logs. Also when requesting support for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, supplying the corresponding log file is mandatory. </p>
     10    <p>For convenience, for each virtual machine, <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> can show these logs in a window. Select a virtual machine from the machine list on the left and click <b outputclass="bold">Logs</b> in the machine tools menu. </p>
     11    <p>The release log file, <filepath>VBox.log</filepath>, contains a wealth of diagnostic information, such as Host OS type and version, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version and build. It also includes a complete dump of the guest's configuration (CFGM), detailed information about the host CPU type and supported features, whether hardware virtualization is enabled, information about VT-x/AMD-V setup, state transitions (such as creating, running, paused, stopping), guest BIOS messages, Guest Additions messages, device-specific log entries and, at the end of execution, final guest state and condensed statistics. </p>
     12    <p>In case of crashes, it is very important to collect <i>crash dumps</i>. This is true for both host and guest crashes. For information about enabling core dumps on Linux, Oracle Solaris, and macOS systems, refer to the following core dump article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website:</p>
     13    <p><ph>http://www.virtualbox.org/wiki/Core_dump</ph>.</p>
     14    <p>You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete virtual machine. See <xref href="../cli_topics/vboxmanage-debugvm.dita"/>.</p>
     15    <p>For network related problems, it is often helpful to capture a trace of network traffic. If the traffic is routed through an adapter on the host, it is possible to use Wireshark or a similar tool to capture the traffic there. However, this often also includes a lot of traffic unrelated to the VM. </p>
     16    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides an ability to capture network traffic only on a specific VM's network adapter. Refer to the following network tracing article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website for information on enabling this capture: </p>
     17    <p><ph>http://www.virtualbox.org/wiki/Network_tips</ph>.</p>
     18    <p> The trace files created by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> are in <filepath>.pcap</filepath> format and can be easily analyzed with Wireshark.</p>
    8019  </body>
    8120 

  • trunk/doc/manual/en_US/dita/topics/cpuhotplug.dita

    r105335 r107390  
    2929    <pre xml:space="preserve">$ VBoxManage controlvm <varname>VM-name</varname> plugcpu 3
    3030$ VBoxManage controlvm <varname>VM-name</varname> unplugcpu 3</pre>
    31     <p>See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref> and <xref href="vboxmanage-controlvm.dita"
    32         >VBoxManage controlvm</xref> for details. </p>
     31    <p>See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/> and <xref href="../cli_topics/vboxmanage-controlvm.dita"/> for details.</p>
    3332    <p>With Linux guests, the following applies: </p>
    3433    <p>To prevent ejection while the CPU is still used it has to be ejected from within the guest before. The Linux

  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-virtual-hard-disk.dita

    r105814 r107390  
    55 
    66  <body>
    7     <p>There are many ways in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can
    8       provide hard disk space to a VM, see <xref href="storage.dita#storage"/>. </p>
    9     <p>The most common way is to use a virtual hard disk. This is a large image file on your
    10       physical hard disk, whose contents <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    11       presents to your VM as if it were a complete hard disk. You can copy this file to another
    12       host, and use it with another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM. </p>
    13     <p>To prevent your physical hard disk on the host OS from filling up, <ph
    14         conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
    15       image file must be large enough to hold the contents of the guest OS and the applications you
    16       want to install. For a Windows or Linux guest, you will probably need several gigabytes for
    17       any serious use. The size limit of the image file can be changed later, see <xref
    18         href="vboxmanage-modifymedium.dita"/>. </p>
     7    <p>There are many ways in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide hard disk space to a VM, see <xref href="storage.dita#storage"/>. </p>
     8    <p>The most common way is to use a virtual hard disk. This is a large image file on your physical hard disk, whose contents <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to your VM as if it were a complete hard disk. You can copy this file to another host, and use it with another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM. </p>
     9    <p>To prevent your physical hard disk on the host OS from filling up, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the image file must be large enough to hold the contents of the guest OS and the applications you want to install. For a Windows or Linux guest, you will probably need several gigabytes for any serious use. The size limit of the image file can be changed later, see <xref href="../cli_topics/vboxmanage-modifymedium.dita"/>.</p>
    1910    <p>
    2011      <note id="note_vc4_gjs_pbc">
    … …  
    2718      <title>Create a Virtual Hard Disk</title>
    2819    </section>
    29     <p>Follow these steps to create a virtual hard disk to use with this VM. To prevent your
    30       physical hard disk on the host OS from filling up, <ph
    31         conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
    32       image file must be large enough to hold the contents of the guest OS and the applications you
    33       want to install. For a Windows or Linux guest, you will probably need several gigabytes for
    34       any serious use. The limit of the image file size can be changed later, see <xref
    35         href="vboxmanage-modifymedium.dita"/>. <ol id="ol_z2h_q5q_pbc">
     20    <p>Follow these steps to create a virtual hard disk to use with this VM. To prevent your physical hard disk on the host OS from filling up, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the image file must be large enough to hold the contents of the guest OS and the applications you want to install. For a Windows or Linux guest, you will probably need several gigabytes for any serious use. The limit of the image file size can be changed later, see <xref href="../cli_topics/vboxmanage-modifymedium.dita"/>. <ol id="ol_z2h_q5q_pbc">
    3621        <li>
    37           <p>Select <b outputclass="bold">Create a Virtual Hard Disk Now</b>. This creates a new
    38             empty virtual hard disk image, located in the VM's machine folder. </p>
     22          <p>Select <b outputclass="bold">Create a Virtual Hard Disk Now</b>. This creates a new empty virtual hard disk image, located in the VM's machine folder. </p>
    3923        </li>
    4024        <li>
    … …  
    4226          <ul id="ul_i3n_y1r_pbc">
    4327            <li>
    44               <p><b outputclass="bold">Disk Size</b>. Use the slider to select a maximum size for
    45                 the hard disk in the new VM. </p>
     28              <p><b outputclass="bold">Disk Size</b>. Use the slider to select a maximum size for the hard disk in the new VM. </p>
    4629            </li>
    47             <li><p><b outputclass="bold">Pre-Allocate Full Size.</b> This setting determines the type of image file used
    48                 for the disk image. Select this setting to use a <i>fixed-size file</i> for the disk image. Otherwise,
    49                   <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will use a <i>dynamically allocated file</i> for
    50                 the disk image. </p><p>The different types of image file behave as follows: </p><ul id="ul_j3n_y1r_pbc">
     30            <li><p><b outputclass="bold">Pre-Allocate Full Size.</b> This setting determines the type of image file used for the disk image. Select this setting to use a <i>fixed-size file</i> for the disk image. Otherwise, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will use a <i>dynamically allocated file</i> for the disk image. </p><p>The different types of image file behave as follows: </p><ul id="ul_j3n_y1r_pbc">
    5131                <li>
    52                   <p><b outputclass="bold">Dynamically allocated file.</b> This type of image file only grows in size
    53                     when the guest actually stores data on its virtual hard disk. Therefore, this file is small
    54                     initially. As the drive is filled with data, the file grows to the specified size. </p>
     32                  <p><b outputclass="bold">Dynamically allocated file.</b> This type of image file only grows in size when the guest actually stores data on its virtual hard disk. Therefore, this file is small initially. As the drive is filled with data, the file grows to the specified size. </p>
    5533                </li>
    5634                <li>
    57                   <p><b outputclass="bold">Fixed-size file.</b> This type of image file immediately occupies the file
    58                     specified, even if only a fraction of that virtual hard disk space is actually in use. While
    59                     occupying much more space, a fixed-size file incurs less overhead and is therefore slightly faster
    60                     than a dynamically allocated file. </p>
     35                  <p><b outputclass="bold">Fixed-size file.</b> This type of image file immediately occupies the file specified, even if only a fraction of that virtual hard disk space is actually in use. While occupying much more space, a fixed-size file incurs less overhead and is therefore slightly faster than a dynamically allocated file. </p>
    6136                </li>
    6237              </ul>For more details about the differences, see <xref href="vdidetails.dita#vdidetails"/>. </li>

  • trunk/doc/manual/en_US/dita/topics/efi.dita

    r105289 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="efi">
    4   <title>Alternative Firmware (EFI)</title>
    5  
     4  <title>Alternative Firmware (UEFI)</title>
    65  <body>
    7     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for the Extensible Firmware
    8       Interface (EFI), which is an industry standard intended to replace the legacy BIOS as the primary interface for
    9       bootstrapping computers and certain system services later. </p>
    10     <p>By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the BIOS firmware for virtual machines. To
    11       use EFI for a given virtual machine, you can enable EFI in the machine's <b outputclass="bold">Settings</b>
    12       window. See <xref href="settings-motherboard.dita#settings-motherboard"/>. Alternatively, use the
    13         <userinput>VBoxManage</userinput> command line interface as follows: </p>
     6    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes support for the Unified Extensible Firmware Interface (UEFI), which is an industry standard intended to replace the legacy BIOS as the primary interface for bootstrapping computers and certain system services later.</p>
     7    <p>By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the BIOS firmware for virtual machines. To use UEFI for a given virtual machine, you can enable EFI in the machine's <b outputclass="bold">Settings</b>. See <xref href="settings-motherboard.dita#settings-motherboard"/>. Alternatively, use the <userinput>VBoxManage</userinput> command line interface as follows:</p>
    148    <pre xml:space="preserve">VBoxManage modifyvm "VM name" --firmware efi</pre>
    15     <p>To switch back to using the BIOS: </p>
     9    <p>To switch back to using the BIOS:</p>
    1610    <pre xml:space="preserve">VBoxManage modifyvm "VM name" --firmware bios</pre>
    17     <p>One notable user of EFI is Apple Mac OS X. More recent Linux versions and Windows releases, starting with Vista,
    18       also offer special versions that can be booted using EFI. </p>
    19     <p>Another possible use of EFI in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is development and testing
    20       of EFI applications, without booting any OS. </p>
    21     <p>Note that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI support is experimental and will be
    22       enhanced as EFI matures and becomes more widespread. Mac OS X, Linux, and newer Windows guests are known to work
    23       fine. Windows 7 guests are unable to boot with the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI
    24       implementation. </p>
     11    <p>Most modern macOS and Windows releases require UEFI.</p>
     12    <p>Another possible use of UEFI in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is development and testing of UEFI applications, without booting any OS.</p>
    2513  </body>
    2614</topic>

  • trunk/doc/manual/en_US/dita/topics/features-overview.dita

    r105941 r107390  
    1212      <li>
    1313        <p><b outputclass="bold">Portability. </b>
    14           <ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on a large number of 64-bit host operating systems. See <xref href="hostossupport.dita#hostossupport"/>. </p>
     14          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on a large number of 64-bit host operating systems. See <xref href="installation-packages.dita"/>.</p>
    1515        <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a so-called <i>hosted</i> hypervisor, sometimes
    1616          referred to as a <i>type 2</i> hypervisor. Whereas a <i>bare-metal</i> or <i>type 1</i> hypervisor runs
    … …  
    145145      </li>
    146146    </ul>
     147    <p>Note that any feature that is marked as <i>experimental</i> is not supported. Feedback and suggestions about such features are welcome. </p>
    147148  </body>
    148149 

  • trunk/doc/manual/en_US/dita/topics/frontends.dita

    r105941 r107390  
    2929          the headless front end requires no graphics support. This is useful, for example, if you
    3030          want to host your virtual machines on a headless Linux server that has no X Window system
    31           installed. See <xref href="vboxheadless.dita">VBoxHeadless, the Remote Desktop
     31          installed. See <xref href="headless-mode.dita">VBoxHeadless, the Remote Desktop
    3232            Server</xref>. </p>
    3333      </li>
    3434      <li>
    3535        <p><b>Separate mode.</b> A front end that is based on <userinput>VBoxHeadless</userinput>,
    36           but does not require VRDE or an RDP viewer. See <xref href="vboxheadless-separate-mode.dita">Separate Mode</xref>.</p>
     36          but does not require VRDE or an RDP viewer. See <xref href="separate-mode.dita">Separate Mode</xref>.</p>
    3737      </li>
    3838    </ul>

  • trunk/doc/manual/en_US/dita/topics/guest-os-Arm.dita

    r105941 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="guest-os-arm">
    4   <title>Arm Guest Operating Systems</title>
     4  <title>Guest OSs That Run on Arm64 Hosts</title>
    55  <body>
    6     <p>Oracle Premier Support covers the running of the following guest OSs in a VM with an Arm64 platform architecture.</p>
    7     <p>
    8       <ul id="ul_bcg_bpf_3cc">
    9         <li>Oracle Linux 9 <ul>
    10             <li>Red Hat Enterprise Linux 9</li>
    11             <li>CentOS Stream 9</li>
    12           </ul></li>
    13         <li>Oracle Linux 8<ul>
    14             <li>Red Hat Enterprise Linux 8</li>
    15           </ul></li>
    16         <li>Oracle Linux 7<ul>
    17             <li>Red Hat Enterprise Linux 7</li>
    18           </ul></li>
    19       </ul>
    20     </p>
     6    <p>The following table shows the Guest OSs that run on hosts with an aarch64 processor and the tier of Oracle support offered for each. See also <xref href="guest-os-x86-64.dita"/>.</p>
     7    <table frame="all" rowsep="1" colsep="1">
     8      <title>Arm64 Hosts Will Run VMs with These OSs</title>
     9      <desc>Guest OSs that run on Arm64 hosts and their levels of support available from Oracle.</desc>
     10      <tgroup cols="2">
     11        <colspec colname="c3" colnum="1" colwidth="1*" align="left"/>
     12        <colspec colname="c4" colnum="2" colwidth="1*" align="left"/>
     13        <thead>
     14          <row>
     15            <entry>Guest Operating System (all 64-bit Arm)</entry>
     16            <entry>Oracle Support Available</entry>
     17          </row>
     18        </thead>
     19        <tbody>
     20          <row>
     21            <entry>Windows 11 (64-bit). Released versions only.</entry>
     22            <entry morerows="2">Premier</entry>
     23          </row>
     24          <row>
     25            <entry>Oracle Linux 9, Red Hat Enterprise Linux 9, CentOS Stream 9</entry>
     26          </row>
     27          <row>
     28            <entry>Oracle Linux 8, Red Hat Enterprise Linux 8</entry>
     29          </row>
     30          <row>
     31            <entry>CentOS Stream 8</entry>
     32            <entry morerows="10">Limited</entry>
     33          </row>
     34          <row>
     35            <entry>Oracle Linux 7, Red Hat Enterprise Linux 7, CentOS Linux 7</entry>
     36          </row>
     37          <row>
     38            <entry>Debian 12</entry>
     39          </row>
     40          <row>
     41            <entry>Debian 11</entry>
     42          </row>
     43          <row>
     44            <entry>Ubuntu 24.10 LTS (Oracular Oriole)</entry>
     45          </row>
     46          <row>
     47            <entry>Ubuntu 24.04 LTS (Noble Numbat)</entry>
     48          </row>
     49          <row>
     50            <entry>Ubuntu 22.04 LTS (Jammy Jellyfish)</entry>
     51          </row>
     52          <row>
     53            <entry>Ubuntu 20.04 LTS (Focal Fossa)</entry>
     54          </row>
     55          <row>
     56            <entry>Ubuntu 18.04 LTS (Bionic Beaver)</entry>
     57          </row>
     58          <row>
     59            <entry>SUSE Linux Enterprise Server 15</entry>
     60          </row>
     61          <row>
     62            <entry>SUSE Linux Enterprise Server 12</entry>
     63          </row>
     64        </tbody>
     65      </tgroup>
     66    </table>
    2167  </body>
    2268</topic>

  • trunk/doc/manual/en_US/dita/topics/guest-os-x86-64.dita

    r105941 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="guest-os-x86">
    4   <title>x86 and x86-64 Guest Operating Systems</title>
     4  <title>Guest OSs That Run on x86_64 Hosts</title>
    55  <body>
    6     <p>Oracle Premier Support covers the running of the following guest OSs in a VM with an x86 or x86-64 platform architecture, as appropriate.</p>
    7     <p>
    8       <ul id="ul_bcg_bpf_3cc">
    9         <li>Windows 11 (64-bit). Released versions only.</li>
    10         <li>Windows 10 (32-bit and 64-bit). Released versions only.</li>
    11         <li>Windows Server 2025 (64-bit)</li>
    12         <li>Windows Server 2022 (64-bit)</li>
    13         <li>Oracle Solaris 11 (32-bit and 64-bit) </li>
    14         <li>Oracle Linux 9 (64-bit)<ul>
    15             <li>Red Hat Enterprise Linux 9 (64-bit)</li>
    16             <li>CentOS Stream 9 (64-bit)</li>
    17           </ul></li>
    18         <li>Oracle Linux 8 (64-bit)<ul>
    19             <li>Red Hat Enterprise Linux 8 (64-bit)</li>
    20           </ul></li>
    21         <li>Oracle Linux 7 (64-bit)<ul>
    22             <li>Red Hat Enterprise Linux 7 (64-bit)</li>
    23           </ul></li>
    24       </ul>
    25     </p>
     6    <p>The following table shows the Guest OSs that run on hosts with an x86_64 processor and the tier of Oracle support offered for each. See also <xref href="guest-os-Arm.dita"/>.</p>
     7    <table frame="all" rowsep="1" colsep="1">
     8      <title>Windows (x86_64), Linux (x86_64), macOS (x86_64), Solaris (x86_64) Hosts Will Run VMs with These OSs</title>
     9      <desc>Guest OSs that run on x86 hosts and their levels of support available from Oracle.</desc>
     10      <tgroup cols="2">
     11        <colspec colname="c3" colnum="1" colwidth="1*" align="left"/>
     12        <colspec colname="c4" colnum="2" colwidth="1*" align="left"/>
     13        <thead>
     14          <row>
     15            <entry>Guest Operating System (all x86)</entry>
     16            <entry>Oracle Support Available</entry>
     17          </row>
     18        </thead>
     19        <tbody>
     20          <row>
     21            <entry>Windows 11 (64-bit). Released versions only.</entry>
     22            <entry morerows="6">Premier</entry>
     23          </row>
     24          <row>
     25            <entry>Windows 10 (32-bit and 64-bit). Released versions only.</entry>
     26          </row>
     27          <row>
     28            <entry>Windows Server 2025 (64-bit)</entry>
     29          </row>
     30          <row>
     31            <entry>Windows Server 2022 (64-bit)</entry>
     32          </row>
     33          <row>
     34            <entry>Oracle Solaris 11 (32-bit and 64-bit)</entry>
     35          </row>
     36          <row>
     37            <entry>Oracle Linux 9 (64-bit), Red Hat Enterprise Linux 9 (64-bit), CentOS Stream 9 (64-bit)</entry>
     38          </row>
     39          <row>
     40            <entry>Oracle Linux 8 (64-bit), Red Hat Enterprise Linux 8 (64-bit)</entry>
     41          </row>
     42          <row>
     43            <entry>Windows 8.1 and 8 (32-bit and 64-bit)</entry>
     44            <entry morerows="24">Limited</entry>
     45          </row>
     46          <row>
     47            <entry>Windows 7 (32-bit and 64-bit)</entry>
     48          </row>
     49          <row>
     50            <entry>Windows Vista SP2 and later (32-bit and 64-bit)</entry>
     51          </row>
     52          <row>
     53            <entry>Windows XP (32-bit)</entry>
     54          </row>
     55          <row>
     56            <entry>Windows Vista (32-bit)</entry>
     57          </row>
     58          <row>
     59            <entry>Windows Server 2019 (64-bit)</entry>
     60          </row>
     61          <row>
     62            <entry>Windows Server 2016 (64-bit)</entry>
     63          </row>
     64          <row>
     65            <entry>Windows Server 2012 and 2012 R2 (64-bit)</entry>
     66          </row>
     67          <row>
     68            <entry>Windows Server 2008 and 2008 R2 (32-bit and 64-bit)</entry>
     69          </row>
     70          <row>
     71            <entry>Windows Server 2003 (32-bit and 64-bit)</entry>
     72          </row>
     73          <row>
     74            <entry>Oracle Solaris 10 8/11 Update 10 and later (32-bit and 64-bit)</entry>
     75          </row>
     76          <row>
     77            <entry>CentOS Stream 8 (64-bit)</entry>
     78          </row>
     79          <row>
     80            <entry>Oracle Linux 7 (64-bit), Red Hat Enterprise Linux 7 (64-bit), CentOS Linux 7 (64-bit)</entry>
     81          </row>
     82          <row>
     83            <entry>Oracle Linux 6 (32-bit and 64-bit), Red Hat Enterprise Linux 6 (32-bit and 64-bit), CentOS 6 (32-bit and 64-bit)</entry>
     84          </row>
     85          <row>
     86            <entry>Oracle Linux 5 (32-bit and 64-bit), Red Hat Enterprise Linux 5 (32-bit and 64-bit), CentOS 5 (32-bit and 64-bit)</entry>
     87          </row>
     88          <row>
     89            <entry>Ubuntu 24.10 LTS (Oracular Oriole) (64-bit)</entry>
     90          </row>
     91          <row>
     92            <entry>Ubuntu 24.04 LTS (Noble Numbat) (64-bit)</entry>
     93          </row>
     94          <row>
     95            <entry>Ubuntu 22.04 LTS (Jammy Jellyfish) (64-bit)</entry>
     96          </row>
     97          <row>
     98            <entry>Ubuntu 20.04 LTS (Focal Fossa) (64-bit)</entry>
     99          </row>
     100          <row>
     101            <entry>Ubuntu 18.04 LTS (Bionic Beaver) (64-bit)</entry>
     102          </row>
     103          <row>
     104            <entry>Ubuntu 16.04 LTS (Xenial Xerus) (32-bit and 64-bit)</entry>
     105          </row>
     106          <row>
     107            <entry>Ubuntu 14.04.5 LTS (Trusty Tahr) (32-bit and 64-bit)</entry>
     108          </row>
     109          <row>
     110            <entry>SUSE Linux Enterprise Server 15 (64-bit)</entry>
     111          </row>
     112          <row>
     113            <entry>SUSE Linux Enterprise Server 12 (64-bit)</entry>
     114          </row>
     115          <row>
     116            <entry>OS/2 Warp 4.5</entry>
     117          </row>
     118        </tbody>
     119      </tgroup>
     120    </table>
    26121  </body>
    27122</topic>

  • trunk/doc/manual/en_US/dita/topics/guest-os.dita

    r105792 r107390  
    77    <p>You can run most operating systems (OSs) successfully on a virtual machine (VM) in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
    88    <p>The virtual hardware determines the choice of guest OSs available, as does the host machine. Ensure you take all aspects of VM configuration into consideration when creating a VM. </p>
    9     <p>Oracle Premier Support provides help, including guest additions where required, to run a subset of OSs in a appropriately configured VMs.</p>
     9    <p>Oracle provides guest additions and premier support for selected OSs.</p>
     10    <p>Other guest OSs can be used with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but only qualify for limited support. Therefore, resolution of customer issues for such guest OSs cannot be assured.</p>
    1011  </body>
    1112</topic>

  • trunk/doc/manual/en_US/dita/topics/guestadd-3d.dita

    r99797 r107390  
    5757          </p>
    5858        <note>
    59           <p>
    60               For the basic Direct3D acceleration to work in a Windows
    61               Guest, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to replace Windows system
    62               files in the virtual machine. As a result, the Guest
    63               Additions installation program offers Direct3D
    64               acceleration as an option that must be explicitly enabled.
    65               Also, you must install the Guest Additions in Safe Mode.
    66               This does <i>not</i> apply to the WDDM
    67               Direct3D video driver available for Windows Vista and
    68               later. See <xref href="KnownIssues.dita">Known Limitations</xref> for details.
    69             </p>
     59          <p> For the basic Direct3D acceleration to work in a Windows Guest, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to replace Windows system files in the virtual machine. As a result, the Guest Additions installation program offers Direct3D acceleration as an option that must be explicitly enabled. Also, you must install the Guest Additions in Safe Mode. This does <i>not</i> apply to the WDDM Direct3D video driver available for Windows Vista and later.</p>
    7060        </note>
    7161      </li>

  • trunk/doc/manual/en_US/dita/topics/guestadd-balloon.dita

    r99797 r107390  
    6767      </p>
    6868    <pre xml:space="preserve">VBoxManage controlvm "VM name" guestmemoryballoon n</pre>
    69     <p>
    70         where <varname>VM name</varname> is the name or UUID of
    71         the virtual machine in question and <varname>n</varname>
    72         is the amount of memory to allocate from the guest in megabytes.
    73         See <xref href="vboxmanage-controlvm.dita"/>.
    74       </p>
     69    <p> where <varname>VM name</varname> is the name or UUID of the virtual machine in question and <varname>n</varname> is the amount of memory to allocate from the guest in megabytes. See <xref href="../cli_topics/vboxmanage-controlvm.dita"/>.</p>
    7570    <p>
    7671        You can also set a default balloon that will automatically be
    … …  
    7974      </p>
    8075    <pre xml:space="preserve">VBoxManage modifyvm "VM name" --guest-memory-balloon n</pre>
    81     <p>
    82         By default, no balloon memory is allocated. This is a VM
    83         setting, like other <userinput>modifyvm</userinput> settings, and
    84         therefore can only be set while the machine is shut down. See
    85         <xref href="vboxmanage-modifyvm.dita"/>.
    86       </p>
     76    <p> By default, no balloon memory is allocated. This is a VM setting, like other <userinput>modifyvm</userinput> settings, and therefore can only be set while the machine is shut down. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>. </p>
    8777  </body>
    8878 

  • trunk/doc/manual/en_US/dita/topics/guestadd-clipboard.dita

    r105941 r107390  
    2727          the guest, and from the guest to the host. </p>
    2828      </li>
    29       <li><b>Enable Clipboard File Transfers</b>. Allows files, in addition to text, to be copied to or from the VM.
    30       </li>
     29      <li><b>Enable Clipboard File Transfers</b>. Allows files, in addition to text, to be copied to or from the VM. <ul>
     30          <li>
     31            <p>On Linux hosts and guests, Shared Clipboard file transfers are limited to files only, one file per transfer. Transferring symbolic links is not supported.</p>
     32          </li>
     33          <li>
     34            <p>Shared Clipboard file transfers are only tested and supported with the official default file managers of the guest and host operating systems.</p>
     35          </li>
     36        </ul></li>
    3137    </ul>   
    3238    <p>To use the <userinput>VBoxManage</userinput> command to control the current clipboard mode, see <xref

  • trunk/doc/manual/en_US/dita/topics/guestadd-dnd-limitations.dita

    r105619 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="guestadd-dnd-limitations">
    4   <title>Known Limitations</title>
     4  <title>Drag Limitations</title>
    55 
    66  <body>
    7     <p>The following limitations are known for drag and drop: </p>
    8     <p>On Windows hosts, dragging and dropping content between UAC-elevated (User Account Control) programs and
    9       non-UAC-elevated programs is not allowed. If you start <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with
    10       Administrator privileges then drag and drop will not work with Windows Explorer, which runs with regular user
    11       privileges by default. </p>
    12     <p>On Linux hosts and guests, programs can query for drag and drop data while the drag operation is still in
    13       progress. For example, on LXDE using the PCManFM file manager. This currently is not supported. As a workaround, a
    14       different file manager, such as Nautilus, can be used instead. </p>
     7    <dl>
     8      <dlentry>
     9        <dt>Details</dt>
     10        <dd>
     11          <p>On Linux hosts and guests, programs can query for dragged data while the drag operation is still in progress. For example, on LXDE using the PCManFM file manager. This feature does not work with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p>
     12        </dd>
     13      </dlentry>
     14      <dlentry>
     15        <dt>Workaround</dt>
     16        <dd>
     17          <p>A different file manager, such as Nautilus, can be used to force programs to wait until a drag operation is complete before querying the data. </p>
     18        </dd>
     19      </dlentry>
     20    </dl>
    1521  </body>
    1622 

  • trunk/doc/manual/en_US/dita/topics/guestadd-dnd.dita

    r105619 r107390  
    2828        outputclass="bold">Drag and Drop</b> menu item in the <b outputclass="bold">Devices</b> menu of the virtual
    2929      machine, or the <userinput>VBoxManage</userinput> command. </p>
     30    <p>On Windows hosts, dragging content between UAC-elevated (User Account Control) programs and non UAC-elevated programs isn't allowed. For example, if you start <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with Administrator privileges then dragging to or from Windows Explorer, which runs with regular user privileges by default, is not possible.</p>
    3031    <p>The following drag and drop modes are available: </p>
    3132    <ul>

  • trunk/doc/manual/en_US/dita/topics/guestadd-guestcontrol.dita

    r99797 r107390  
    2424      guest directories is available.
    2525    </p>
    26     <p>
    27       To use these features, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> command line. See
    28       <xref href="vboxmanage-guestcontrol.dita"/>.
    29     </p>
     26    <p> To use these features, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> command line. See <xref href="../cli_topics/vboxmanage-guestcontrol.dita"/>. </p>
    3027  </body>
    3128 

  • trunk/doc/manual/en_US/dita/topics/guestadd-guestprops.dita

    r105303 r107390  
    5151      virtual machine's <b outputclass="bold">Machine</b> menu.
    5252    </p>
    53     <p> A more flexible way to use this channel is with the <userinput>VBoxManage
    54                 guestproperty</userinput> command. See <xref href="vboxmanage-guestproperty.dita"/>.
    55             For example, to have <i>all</i> the available guest properties for a given running VM
    56             listed with their respective values, use this command: </p>
     53    <p> A more flexible way to use this channel is with the <userinput>VBoxManage guestproperty</userinput> command. See <xref href="../cli_topics/vboxmanage-guestproperty.dita"/>. For example, to have <i>all</i> the available guest properties for a given running VM listed with their respective values, use this command: </p>
    5754    <pre xml:space="preserve">$ VBoxManage guestproperty enumerate "Windows Vista III"
    5855VirtualBox Command Line Management Interface Version <varname>version-number</varname>

  • trunk/doc/manual/en_US/dita/topics/guestadd-pagefusion.dita

    r99797 r107390  
    8686      </p>
    8787    <pre xml:space="preserve">VBoxManage modifyvm "VM name" --page-fusion on</pre>
    88     <p> You can observe Page Fusion operation using some metrics. <codeph>RAM/VMM/Shared</codeph>
    89       shows the total amount of fused pages, whereas the per-VM metric
    90         <codeph>Guest/RAM/Usage/Shared</codeph> will return the amount of fused memory for a given
    91       VM. See <xref href="vboxmanage-metrics.dita"/> for information on how to query metrics. </p>
     88    <p> You can observe Page Fusion operation using some metrics. <codeph>RAM/VMM/Shared</codeph> shows the total amount of fused pages, whereas the per-VM metric <codeph>Guest/RAM/Usage/Shared</codeph> will return the amount of fused memory for a given VM. See <xref href="../cli_topics/vboxmanage-metrics.dita"/> for information on how to query metrics.</p>
    9289    <note>
    9390      <p>

  • trunk/doc/manual/en_US/dita/topics/guestadd-resizing-linux-limitations.dita

    r98549 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="guestadd-resizing-linux-limitations">
    4   <title>Known Limitations</title>
     4  <title>Error When Removing a Monitor</title>
    55 
    66  <body>
    7     <p><userinput>VBoxDRMClient</userinput> is not able to handle
    8           arbitrary guest monitor topologies. Specifically, disabling a
    9           guest monitor that is not the last one invalidates the monitor
    10           topology due to limitations in the
    11           <codeph>vmwgfx.ko</codeph> Linux kernel module. For example,
    12           when the guest is configured to have four monitors it is not
    13           recommended to disable the second or third monitor.
    14         </p>
     7    <dl>
     8      <dlentry>
     9        <dt>Details</dt>
     10        <dd>
     11          <p><userinput>VBoxDRMClient</userinput> can't handle arbitrary guest monitor topologies. Disabling a guest monitor other than the last one invalidates the monitor topology because of limitations in the <codeph>vmwgfx.ko</codeph> Linux kernel module.</p>
     12        </dd>
     13      </dlentry>
     14      <dlentry>
     15        <dt>Workaround</dt>
     16        <dd>
     17          <p>Always remove the last monitor in a the topology. For example, when the guest is configured to have four monitors, avoid disabling the second or third monitor.</p>
     18        </dd>
     19      </dlentry>
     20    </dl>
    1521  </body>
    1622 

  • trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita

    r105499 r107390  
    7070            Controller</b> under the Storage Tree box and then select <b outputclass="bold">Add SATA Controller</b>. The
    7171          new controller appears as a separate PCI device in the virtual machine, and you can add virtual disks to it. </p>
    72         <p>To change the IDE compatibility mode settings for the SATA controller, see <xref
    73             href="vboxmanage-storagectl.dita"/>. </p>
     72        <p>To change the IDE compatibility mode settings for the SATA controller, see <xref href="../cli_topics/vboxmanage-storagectl.dita"/>. </p>
    7473      </li>
    7574      <li>

  • trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita

    r105335 r107390  
    99      applies to all of the aforementioned image formats (VDI, VMDK, VHD, or HDD) and irrespective of whether an image
    1010      is fixed-size or dynamically allocated. </p>
    11     <p>By default, images are in <i>normal</i> mode. To mark an existing image with one of the nonstandard modes listed
    12       below, use <userinput>VBoxManage modifymedium</userinput>. See <xref href="vboxmanage-modifymedium.dita"/>.
    13       Alternatively, use <userinput>VBoxManage storageattach</userinput> to attach the image to a VM and specify the
    14         <codeph>--mtype</codeph> argument. See <xref href="vboxmanage-storageattach.dita"/>. </p>
     11    <p>By default, images are in <i>normal</i> mode. To mark an existing image with one of the nonstandard modes listed below, use <userinput>VBoxManage modifymedium</userinput>. See <xref href="../cli_topics/vboxmanage-modifymedium.dita"/>. Alternatively, use <userinput>VBoxManage storageattach</userinput> to attach the image to a VM and specify the <codeph>--mtype</codeph> argument. See <xref href="../cli_topics/vboxmanage-storageattach.dita"/>.</p>
    1512    <p>The available virtual disk image modes are as follows: </p>
    1613    <ul>
    … …  
    8683          the machine. This is also why immutable images behave as described above when snapshots are also present,
    8784          which use differencing images as well. </p>
    88         <p>If the automatic discarding of the differencing image on VM startup does not fit your needs, you can turn it
    89           off using the <codeph>autoreset</codeph> parameter of <userinput>VBoxManage modifymedium</userinput>. See
    90             <xref href="vboxmanage-modifymedium.dita"/>. </p>
     85        <p>If the automatic discarding of the differencing image on VM startup does not fit your needs, you can turn it off using the <codeph>autoreset</codeph> parameter of <userinput>VBoxManage modifymedium</userinput>. See <xref href="../cli_topics/vboxmanage-modifymedium.dita"/>.</p>
    9186      </li>
    9287      <li>

  • trunk/doc/manual/en_US/dita/topics/host-guest-matrix.dita

    r106204 r107390  
    77            <table frame="all" rowsep="1" colsep="1">
    88                <title>Host and Guest (VM) Platform Combinations Available in VirtualBox</title>
    9                 <desc>Matrix of available host platforms and the Virtual machines they run.</desc>
     9                <desc>Summary matrix of available host platforms and the Virtual machines they run.</desc>
    1010                <tgroup cols="4">
    1111                    <colspec colname="c1" colnum="1" colwidth="1*" align="left"/>
    … …  
    2525                            <entry>x86-64 (for example Intel or AMD)</entry>
    2626                            <entry>
    27                                 <p>Windows </p>
     27                                <p>Windows</p>
    2828                                <p>Windows Server</p>
    2929                                <p>macOS (requires Intel hardware)</p>
    … …  
    4141                        <row>
    4242                            <entry>Arm64</entry>
    43                             <entry>macOS (requires Apple silicon hardware)</entry>
     43                            <entry>
     44                                <p>Windows 11</p>
     45                                <p>macOS (requires Apple silicon hardware)</p>
     46                            </entry>
    4447                            <entry>Arm64</entry>
    45                             <entry>Linux (various distributions)</entry>
     48                            <entry>
     49                                <p>Linux (various distributions)</p>
     50                                <p>Windows 11</p>
     51                            </entry>
    4652                        </row>
    4753                    </tbody>

  • trunk/doc/manual/en_US/dita/topics/install-ext-pack-manager.dita

    r105293 r107390  
    2323      </li>
    2424    </ol>
    25     <p>Alternatively, you can use the <userinput>VBoxManage</userinput> command line to install and manage an <ph
    26         conkeyref="vbox-conkeyref-phrases/vbox-ext"/>. See <xref href="vboxmanage-extpack.dita"/>. </p>
     25    <p>Alternatively, you can use the <userinput>VBoxManage</userinput> command line to install and manage an <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>. See <xref href="../cli_topics/vboxmanage-extpack.dita"/>.</p>
    2726  </body>
    2827 

  • trunk/doc/manual/en_US/dita/topics/install-linux-performing.dita

    r105289 r107390  
    55 
    66  <body>
    7     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is available in a number of package formats native to
    8       various common Linux distributions. See <xref href="hostossupport.dita#hostossupport"/>. In addition, there is an
    9       alternative generic installer (.run) which you can use on supported Linux distributions. </p>
     7    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is available in a number of package formats native to various common Linux distributions. See <xref href="installation-packages.dita"/>. In addition, there is an alternative generic installer (.run) which you can use on supported Linux distributions. </p>
    108  </body>
    119</topic>

  • trunk/doc/manual/en_US/dita/topics/install-linux-prereq.dita

    r106204 r107390  
    55 
    66  <body>
    7     <p>For the various versions of Linux that are supported as host operating systems, see <xref
    8         href="hostossupport.dita#hostossupport"/>. </p>
     7    <p>For the various versions of Linux that are supported as host operating systems, see <xref href="installation-packages.dita"/>.</p>
    98    <p>You may need to install the following package on your Linux system before starting the installation. Some systems will do this for you automatically when you install <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
    109    <ul>

  • trunk/doc/manual/en_US/dita/topics/install-solaris-host.dita

    r105289 r107390  
    55 
    66  <body>
    7     <p>For the specific versions of Oracle Solaris that are supported as host operating systems, see <xref
    8         href="hostossupport.dita#hostossupport"/>. </p>
     7    <p>For the specific versions of Oracle Solaris that are supported as host operating systems, see <xref href="installation-packages.dita"/>.</p>
    98    <p>If you have a previously installed instance of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on your
    109      Oracle Solaris host, please uninstall it first before installing a new instance. See <xref

  • trunk/doc/manual/en_US/dita/topics/install-win-prereq.dita

    r105289 r107390  
    55 
    66  <body>
    7     <p>For the various versions of Windows that are supported as host operating systems, please refer to <xref
    8         href="hostossupport.dita#hostossupport"/>. </p>
     7    <p>For the various versions of Windows that are supported as host operating systems, please refer to <xref href="installation-packages.dita"/>.</p>
    98    <p>In addition, Windows Installer must be present on your system. This should be the case for all supported Windows
    109      platforms. </p>

  • trunk/doc/manual/en_US/dita/topics/intro-removing.dita

    r105289 r107390  
    55 
    66  <body>
    7     <p>You can remove a VM from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or move the VM and its associated
    8       files, such as disk images, to another location on the host. </p>
     7    <p>You can remove a VM from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or move the VM and its associated files, such as disk images, to another location on the host.</p>
    98    <ul>
    109      <li>
    11         <p><b outputclass="bold">Removing a VM.</b> To remove a VM, right-click the VM in the <ph
    12             conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> machine list and select <b
    13             outputclass="bold">Remove</b>. </p>
    14         <p>
    15           The confirmation dialog enables you to specify whether to only
    16           remove the VM from the list of machines or to remove the files
    17           associated with the VM.
    18         </p>
    19         <p>
    20           Note that the <b outputclass="bold">Remove</b> menu
    21           item is disabled while a VM is running.
    22         </p>
     10        <p><b outputclass="bold">Removing a VM.</b> To remove a VM, right-click the VM in the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> machine list and select <b outputclass="bold">Remove</b>.</p>
     11        <p> The confirmation dialog enables you to specify whether to only remove the VM from the list of machines or to remove the files associated with the VM.</p>
     12        <p> Note that the <b outputclass="bold">Remove</b> menu item is disabled while a VM is running.</p>
    2313      </li>
    2414      <li>
    … …  
    2616          right-click the VM in the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>'s machine list
    2717          and select <b outputclass="bold">Move</b>. </p>
    28         <p>The file dialog prompts you to specify a new location for the VM. </p>
    29         <p>When you move a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration files are updated
    30           automatically to use the new location on the host. </p>
    31         <p>Note that the <b outputclass="bold">Move</b> menu item is disabled while a VM is running. </p>
    32         <p>You can also use the <userinput>VBoxManage movevm</userinput> command to move a VM. See <xref
    33             href="vboxmanage-movevm.dita"/>. </p>
     18        <p>The file dialog prompts you to specify a new location for the VM.</p>
     19        <p>When you move a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration files are updated automatically to use the new location on the host.</p>
     20        <p>Note that the <b outputclass="bold">Move</b> menu item is disabled while a VM is running.</p>
     21        <p>You can also use the <userinput>VBoxManage movevm</userinput> command to move a VM. See <xref href="../cli_topics/vboxmanage-movevm.dita"/>.</p>
    3422      </li>
    3523    </ul>
    36     <p>For information about removing or moving a disk image file from <ph
    37         conkeyref="vbox-conkeyref-phrases/product-name"/>, see <xref
    38         href="virtual-media-manager.dita#virtual-media-manager"/>. </p>
     24    <p>For information about removing or moving a disk image file from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, see <xref href="virtual-media-manager.dita#virtual-media-manager"/>.</p>
    3925  </body>
    4026 

  • trunk/doc/manual/en_US/dita/topics/intro-resize-window.dita

    r105289 r107390  
    1717        <p>The aspect ratio of the guest screen is preserved when resizing the window. To ignore the aspect ratio, press
    1818            <b outputclass="bold">Shift</b> during the resize operation. </p>
    19         <p>See <xref href="KnownIssues.dita">Known Limitations</xref> for additional remarks. </p>
    2019      </li>
    2120      <li>

  • trunk/doc/manual/en_US/dita/topics/iocaching.dita

    r105499 r107390  
    4949      controller: </p>
    5050    <pre xml:space="preserve">VBoxManage storagectl "VM name" --name &lt;controllername&gt; --hostiocache off</pre>
    51     <p>See <xref href="vboxmanage-storagectl.dita"/>. </p>
     51    <p>See <xref href="../cli_topics/vboxmanage-storagectl.dita"/>.</p>
    5252    <p>For the above reasons, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses SATA controllers by default for
    5353      new virtual machines. </p>

  • trunk/doc/manual/en_US/dita/topics/iscsi-intnet.dita

    r105335 r107390  
    55 
    66  <body>
    7     <p>As an experimental feature, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables access to an iSCSI
    8       target running in a virtual machine which is configured to use Internal Networking mode. See <xref
    9         href="storage-iscsi.dita">iSCSI Servers</xref>, <xref href="network_internal.dita">Internal Networking</xref>,
    10       and <xref href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>. </p>
     7    <p>As an experimental feature, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables access to an iSCSI target running in a virtual machine which is configured to use Internal Networking mode. See <xref href="storage-iscsi.dita">iSCSI Servers</xref>, <xref href="network_internal.dita">Internal Networking</xref>, and <xref href="../cli_topics/vboxmanage-storageattach.dita"/>.</p>
    118    <p>The IP stack accessing Internal Networking must be configured in the virtual machine which accesses the iSCSI
    129      target. A free static IP and a MAC address not used by other virtual machines must be chosen. In the example

  • trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita

    r105499 r107390  
    1414      <p>For the basic Direct3D acceleration to work in a Windows guest, you have to install the WDDM video driver
    1515        available for Windows Vista or later. </p>
    16       <p>
    17             For Windows 8 and later, only the WDDM Direct3D video driver
    18             is available. For basic Direct3D acceleration to work in
    19             Windows XP guests, you have to install the Guest Additions
    20             in Safe Mode. See <xref href="KnownIssues.dita">Known Limitations</xref> for
    21             details.
    22           </p>
     16      <p> For Windows 8 and later, only the WDDM Direct3D video driver is available. For basic Direct3D acceleration to work in Windows XP guests, you have to install the Guest Additions in Safe Mode.</p>
    2317    </note>
    2418    <p>If you prefer to mount the Guest Additions manually, you can perform the following steps: </p>

  • trunk/doc/manual/en_US/dita/topics/natforward.dita

    r105499 r107390  
    2121      be found in the <b outputclass="bold">Network</b> settings dialog for network adaptors configured to use NAT.
    2222      Here, you can map host ports to guest ports to allow network traffic to be routed to a specific port in the guest. </p>
    23     <p>Alternatively, the command line tool <userinput>VBoxManage</userinput> can be used. See <xref
    24         href="vboxmanage-modifyvm.dita"/>. </p>
     23    <p>Alternatively, the command line tool <userinput>VBoxManage</userinput> can be used. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    2524    <p>You will need to know which ports on the guest the service uses and to decide which ports to use on the host. You
    2625      may want to use the same ports on the guest and on the host. You can use any ports on the host which are not
    … …  
    4544    <p>This example forwards all TCP traffic arriving on the localhost interface at 127.0.0.1 through port 2222 to port
    4645      22 in the guest. </p>
    47     <p>It is possible to configure incoming NAT connections while the VM is running, see <xref
    48         href="vboxmanage-controlvm.dita"/>. </p>
     46    <p>It is possible to configure incoming NAT connections while the VM is running, see <xref href="../cli_topics/vboxmanage-controlvm.dita"/>.</p>
    4947  </body>
    5048 

  • trunk/doc/manual/en_US/dita/topics/nested-virt.dita

    r105335 r107390  
    1919      </li>
    2020      <li>
    21         <p>Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage modifyvm</userinput> command to
    22           enable or disable nested virtualization. See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. </p>
     21        <p>Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage modifyvm</userinput> command to enable or disable nested virtualization. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    2322      </li>
    2423    </ul>

  • trunk/doc/manual/en_US/dita/topics/nestedpaging.dita

    r105303 r107390  
    4141          Core i7 (Nehalem) processors.
    4242        </p>
    43         <p> If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large
    44             pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of
    45           up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm
    46             --large-pages</userinput> command. See <xref href="vboxmanage-modifyvm.dita">VBoxManage
    47             modifyvm</xref>. </p>
     43        <p> If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm --large-pages</userinput> command. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    4844        <p>
    4945          If you have an Intel CPU with EPT, please consult
    … …  
    5955          Translation Lookaside Buffers (TLBs).
    6056        </p>
    61         <p> To enable these features for a VM, you use the <userinput>VBoxManage modifyvm
    62             --vtx-vpid</userinput> and <userinput>VBoxManage modifyvm --large-pages</userinput>
    63           commands. See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. </p>
     57        <p> To enable these features for a VM, you use the <userinput>VBoxManage modifyvm --vtx-vpid</userinput> and <userinput>VBoxManage modifyvm --large-pages</userinput> commands. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    6458      </li>
    6559    </ul>

  • trunk/doc/manual/en_US/dita/topics/network_cloud.dita

    r105335 r107390  
    1818      </li>
    1919      <li>
    20         <p>On the command line, use <userinput>VBoxManage modifyvm vmname --nic <varname>x</varname> cloud</userinput>.
    21           See <xref href="vboxmanage-modifyvm.dita"/>. </p>
     20        <p>On the command line, use <userinput>VBoxManage modifyvm vmname --nic <varname>x</varname> cloud</userinput>. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    2221      </li>
    2322    </ul>

  • trunk/doc/manual/en_US/dita/topics/network_hostonly.dita

    r105335 r107390  
    3939      </li>
    4040      <li>
    41         <p>On the command line, use <userinput>VBoxManage modifyvm vmname --nic <varname>x</varname>
    42             hostonly</userinput>. See <xref href="vboxmanage-modifyvm.dita"/>. </p>
     41        <p>On the command line, use <userinput>VBoxManage modifyvm vmname --nic <varname>x</varname> hostonly</userinput>. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    4342      </li>
    4443    </ul>
    … …  
    5554      </li>
    5655      <li>
    57         <p>Alternatively, you can use the <userinput>VBoxManage dhcpserver</userinput> command. See <xref
    58             href="vboxmanage-dhcpserver.dita"/>. </p>
     56        <p>Alternatively, you can use the <userinput>VBoxManage dhcpserver</userinput> command. See <xref href="../cli_topics/vboxmanage-dhcpserver.dita"/>.</p>
    5957      </li>
    6058    </ul>

  • trunk/doc/manual/en_US/dita/topics/network_internal.dita

    r105293 r107390  
    4040      </li>
    4141    </ul>
    42     <p>Unless you configure the virtual network cards in the guest operating systems that are
    43       participating in the internal network to use static IP addresses, you may want to use the DHCP
    44       server that is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to manage IP addresses for the internal
    45       network. See <xref href="vboxmanage-dhcpserver.dita"/>. </p>
     42    <p>Unless you configure the virtual network cards in the guest operating systems that are participating in the internal network to use static IP addresses, you may want to use the DHCP server that is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to manage IP addresses for the internal network. See <xref href="../cli_topics/vboxmanage-dhcpserver.dita"/>.</p>
    4643    <p>As a security measure, by default, the Linux implementation of
    4744      internal networking only allows VMs running under the same user ID

  • trunk/doc/manual/en_US/dita/topics/network_performance.dita

    r105335 r107390  
    4444          adaptor. Use of this mode is only possible on the following network types: NAT Network, Bridged Adapter,
    4545          Internal Network, and Host-Only Adapter. </p>
    46                      <p>To setup a promiscuous mode policy, either select from the drop down list located in the <b
    47             outputclass="bold">Network Settings</b> dialog for the network adaptor or use the command line tool
    48             <userinput>VBoxManage</userinput>. See <xref href="vboxmanage-modifyvm.dita"/>. </p>
     46                     <p>To setup a promiscuous mode policy, either select from the drop down list located in the <b outputclass="bold">Network Settings</b> dialog for the network adaptor or use the command line tool <userinput>VBoxManage</userinput>. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    4947                     <p>Promiscuous mode policies are as follows: </p>
    5048                     <ul>

  • trunk/doc/manual/en_US/dita/topics/networkingdetails.dita

    r105335 r107390  
    1717      </li>
    1818    </ul>
    19     <p>Four of the network cards can be configured in the <b outputclass="bold">Network</b> section of the <b
    20         outputclass="bold">Settings</b> window in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. You can configure
    21       all eight network cards on the command line using <userinput>VBoxManage modifyvm</userinput>. See <xref
    22         href="vboxmanage-modifyvm.dita"/>. </p>
     19    <p>Four of the network cards can be configured in the <b outputclass="bold">Network</b> section of the <b outputclass="bold">Settings</b> window in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. You can configure all eight network cards on the command line using <userinput>VBoxManage modifyvm</userinput>. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    2320    <p>This chapter explains the various networking settings in more detail. </p>
    2421  </body>

  • trunk/doc/manual/en_US/dita/topics/ovf-about.dita

    r105289 r107390  
    1515        conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
    1616    <note>
    17       <p>The OVF standard is complex, and support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is an ongoing
    18         process. In particular, no guarantee is made that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports
    19         all appliances created by other virtualization software. For a list of known limitations, see <xref
    20           href="KnownIssues.dita">Known Limitations</xref>. </p>
     17      <p>The OVF standard is complex, and support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is an ongoing process. No guarantee is made that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports all appliances created by other virtualization software. In particular, the following limitations exist:</p>
     18      <p>
     19        <ul>
     20          <li>
     21            <p>OVF localization, with multiple languages in a single OVF file, is not yet supported.</p>
     22          </li>
     23          <li>
     24            <p>Some OVF sections like StartupSection, DeploymentOptionSection, and InstallSection are ignored.</p>
     25          </li>
     26          <li>
     27            <p>OVF environment documents, including their property sections are not yet supported.</p>
     28          </li>
     29          <li>
     30            <p>Remote files using HTTP or other mechanisms are not yet supported.</p>
     31          </li>
     32        </ul>
     33      </p>
    2134    </note>
    2235    <p>Appliances in OVF format can appear in the following variants: </p>

  • trunk/doc/manual/en_US/dita/topics/ovf-export-appliance.dita

    r105303 r107390  
    6161      </li>
    6262    </ol>
    63     <p>You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See <xref
    64         href="vboxmanage-export.dita"/>. </p>
     63    <p>You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See <xref href="../cli_topics/vboxmanage-export.dita"/>.</p>
    6564  </body>
    6665 

  • trunk/doc/manual/en_US/dita/topics/ovf-import-appliance.dita

    r105404 r107390  
    5555      </li>
    5656    </ol>
    57     <p>You can use the <userinput>VBoxManage import</userinput> command to import an appliance. See <xref
    58         href="vboxmanage-import.dita"/>. </p>
     57    <p>You can use the <userinput>VBoxManage import</userinput> command to import an appliance. See <xref href="../cli_topics/vboxmanage-import.dita"/>.</p>
    5958  </body>
    6059 

  • trunk/doc/manual/en_US/dita/topics/preface-accessibility.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preface-audience.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preface-conventions.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preface-diversity.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preface-doc-accessibility.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preface-reldocs.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preface.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/preferences.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/privacy.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/rawdisk-access-disk-partitions.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/rawdisk-access-entire-physical-disk.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/rawdisk.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/rdp-viewers.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/remotevm.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/restrict-network-attachments.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/seamlesswindows.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sec-rec-cve-2018-12126-et-al.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sec-rec-cve-2018-3646.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/secure-config-vms.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-3d-graphics.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-cd-dvd-passthrough.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-encryption.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-features.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-general.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-model.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-networking.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-of-remote-vms.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-recommendations.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-secure-install-overview.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-secure-install-postinstall.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-secure-install.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-shared-folders.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-usb-passthrough.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security-vrdp-auth.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/security_clipboard.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/serialports.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105841 r107390  
    1818      data is supported. How this virtual serial port is then connected to the host is configurable, and the details
    1919      depend on your host OS. </p>
    20     <p>You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set up virtual serial
    21       ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/> for information on the <codeph>--uart</codeph>,
    22         <codeph>--uart-mode</codeph> and <codeph>--uart-type</codeph> options. </p>
     20    <p>You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set up virtual serial ports. For the latter, see <xref href="../cli_topics/vboxmanage-modifyvm.dita"/> for information on the <codeph>--uart</codeph>, <codeph>--uart-mode</codeph> and <codeph>--uart-type</codeph> options.</p>
    2321    <p>You can configure up to four virtual serial ports per virtual machine. For each device, you must set the
    2422      following: </p>

  • trunk/doc/manual/en_US/dita/topics/settings-acceleration.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-audio.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-basic.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-capture.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-description.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-disk-encryption.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-display.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-general-advanced.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105841 r107390  
    3131            settings), the network, or none of these.
    3232          </p>
    33         <p>If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a network using the PXE
    34           mechanism. This needs to be configured in detail on the command line. See <xref
    35             href="vboxmanage-modifyvm.dita"/>. </p>
     33        <p>If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a network using the PXE mechanism. This needs to be configured in detail on the command line. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    3634      </li>
    3735      <li>
    … …  
    9492    <p>In addition, you can turn off the <b outputclass="bold">Advanced Configuration and Power Interface (ACPI)</b>
    9593      which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default. </p>
    96     <p>ACPI is the current industry standard to allow OSes to recognize hardware, configure motherboards and other
    97       devices and manage power. As most computers contain this feature and Windows and Linux support ACPI, it is also
    98       enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI can only be turned off using the
    99       command line. See <xref href="vboxmanage-modifyvm.dita"/>. </p>
     94    <p>ACPI is the current industry standard to allow OSes to recognize hardware, configure motherboards and other devices and manage power. As most computers contain this feature and Windows and Linux support ACPI, it is also enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI can only be turned off using the command line. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    10095    <note>
    10196      <p>All Windows OSes install different kernels, depending on whether ACPI is available. This means that ACPI

  • trunk/doc/manual/en_US/dita/topics/settings-network.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-processor.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-remote-display.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-screen.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105841 r107390  
    2828        <p>You can configure the relationship between guest and host monitors using the <b outputclass="bold">View</b>
    2929          menu by pressing Host key + Home when you are in full screen or seamless mode. </p>
    30         <p>See also <xref href="KnownIssues.dita">Known Limitations</xref>. </p>
     30        <p>See also <xref href="known-issues.dita"/>.</p>
    3131      </li>
    3232      <li>
    … …  
    7878      </li>
    7979      <li>
    80         <p><b outputclass="bold">Enable 3D Acceleration:</b> If
    81             a virtual machine has Guest Additions installed, you can
    82             select here whether the guest should support accelerated 3D
    83             graphics. See <xref href="guestadd-3d.dita#guestadd-3d"/>.
    84           </p>
     80        <p><b outputclass="bold">Enable 3D Acceleration:</b> If a virtual machine has Guest Additions installed, you can enable accelerated 3D graphics on the VM. See <xref href="guestadd-3d.dita#guestadd-3d"/>. </p>
     81        <p>With 3D acceleration enabled, the VM also uses video decoding acceleration if the host also supports video decoding acceleration. The host must be x86_64 running Windows or Linux, and the VM must be x86_64 running Windows 10 or Windows 11. The VM can use video decoding of all media formats that are supported by the host, and CPU load is reduced during playback of these media formats.</p>
    8582      </li>
    8683    </ul>

  • trunk/doc/manual/en_US/dita/topics/settings-storage.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-system.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/settings-usb.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105149 r107390  
    1818          host without a proper shutdown. This may cause data loss.</p>
    1919      </note>
    20       </p>
     20    </p>
    2121                  <note>
    22       <p>Oracle Solaris hosts have a few known limitations regarding USB support. See <xref
    23           href="KnownIssues.dita">Known Limitations</xref>. </p>
     22      <p>USB support on Oracle Solaris hosts requires Oracle Solaris 11 FCS or later. Webcams and other isochronous devices are known to have poor performance.</p>
    2423    </note>
    2524                  <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> also enables your guests

  • trunk/doc/manual/en_US/dita/topics/settings-window.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sf_mount_auto.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sf_mount_manual.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/shared-folders.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sharedfolders.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105388 r107390  
    3333          follows: </p>
    3434                     <pre xml:space="preserve">VBoxManage sharedfolder add "VM name" --name "sharename" --hostpath "C:\test"</pre>
    35                      <p> See <xref href="vboxmanage-sharedfolder.dita"/>. </p>
     35                     <p> See <xref href="../cli_topics/vboxmanage-sharedfolder.dita"/>.</p>
    3636                  </li>
    3737               </ul>

  • trunk/doc/manual/en_US/dita/topics/snapshots-contents.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/snapshots-take-restore-delete.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/snapshots.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/soft-keyb-custom.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/soft-keyb-using.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/soft-keyb.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/solaris-zones.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/solariscodedumper.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/specialcharacters.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sse412passthrough.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/startingvboxonlinux.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/storage-bandwidth-limit.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/storage-cds.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105335 r107390  
    5050                  </li>
    5151               </ul>
    52                <p>To enable host drive passthrough you can use the <codeph>--passthrough</codeph> option of the
    53         <userinput>VBoxManage storageattach</userinput> command. See <xref href="vboxmanage-storageattach.dita"/>. </p>
     52               <p>To enable host drive passthrough you can use the <codeph>--passthrough</codeph> option of the <userinput>VBoxManage storageattach</userinput> command. See <xref href="../cli_topics/vboxmanage-storageattach.dita"/>. </p>
    5453               <p>Even if passthrough is enabled, unsafe commands, such as updating the drive firmware, will be blocked.
    5554      Video CD formats are never supported, not even in passthrough mode, and cannot be played from a virtual machine. </p>

  • trunk/doc/manual/en_US/dita/topics/storage-iscsi.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105335 r107390  
    1515      (VDI file) and an iSCSI target. To achieve this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has an
    1616      integrated iSCSI initiator. </p>
    17                <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s iSCSI support has been developed according to
    18       the iSCSI standard and should work with all standard-conforming iSCSI targets. To use an iSCSI target with <ph
    19         conkeyref="vbox-conkeyref-phrases/product-name"/>, you must use the command line. See <xref
    20         href="vboxmanage-storageattach.dita"/>. </p>
     17               <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s iSCSI support has been developed according to the iSCSI standard and should work with all standard-conforming iSCSI targets. To use an iSCSI target with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you must use the command line. See <xref href="../cli_topics/vboxmanage-storageattach.dita"/>.</p>
    2118            </body>
    2219           

  • trunk/doc/manual/en_US/dita/topics/storage.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/sysprep.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/technical-components.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105134 r107390  
    8181          directly provide any video output and keyboard or mouse input,
    8282          but enables redirection through the VirtualBox Remote Desktop
    83           Extension. See <xref href="vboxheadless.dita"/>.
     83          Extension. See <xref href="headless-mode.dita"/>.
    8484        </p>
    8585      </li>

  • trunk/doc/manual/en_US/dita/topics/teleporting.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105335 r107390  
    3939        <pre xml:space="preserve">VBoxManage modifyvm <varname>targetvmname</varname> --teleporter on --teleporter-port <varname>port</varname>
    4040                     </pre>
    41         <p><varname>targetvmname</varname> is the name of the
    42           virtual machine on the target host and
    43           <varname>port</varname> is a TCP/IP port number to be
    44           used on both the source and the target hosts. For example, use
    45           6000. See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>.
    46         </p>
     41        <p><varname>targetvmname</varname> is the name of the virtual machine on the target host and <varname>port</varname> is a TCP/IP port number to be used on both the source and the target hosts. For example, use 6000. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>. </p>
    4742      </li>
    4843      <li>
    … …  
    5550        <pre xml:space="preserve">VBoxManage controlvm <varname>sourcevmname</varname> teleport --host <varname>targethost</varname> --port <varname>port</varname>
    5651                     </pre>
    57         <p>where <varname>sourcevmname</varname> is the name of the virtual machine on the source host, which is the
    58           machine that is currently running. <varname>targethost</varname> is the host or IP name of the target host on
    59           which the machine is waiting for the teleport request, and <varname>port</varname> must be the same number as
    60           specified in the command on the target host. See <xref href="vboxmanage-controlvm.dita">VBoxManage
    61             controlvm</xref>. </p>
     52        <p>where <varname>sourcevmname</varname> is the name of the virtual machine on the source host, which is the machine that is currently running. <varname>targethost</varname> is the host or IP name of the target host on which the machine is waiting for the teleport request, and <varname>port</varname> must be the same number as specified in the command on the target host. See <xref href="../cli_topics/vboxmanage-controlvm.dita"/>.</p>
    6253      </li>
    6354    </ol>
    … …  
    6556      the source and the target host. </p>
    6657    <note>
    67       <p>In rare cases, if the CPUs of the source and the target are very different, teleporting can fail with an error
    68         message, or the target may hang. This may happen especially if the VM is running application software that is
    69         highly optimized to run on a particular CPU without correctly checking that certain CPU features are actually
    70         present. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> filters what CPU capabilities are presented to
    71         the guest operating system. Advanced users can attempt to restrict these virtual CPU capabilities with the
    72           <userinput>VBoxManage modifyvm --cpuid-portability-level</userinput> command. See <xref
    73           href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. </p>
     58      <p>In rare cases, if the CPUs of the source and the target are very different, teleporting can fail with an error message, or the target may hang. This may happen especially if the VM is running application software that is highly optimized to run on a particular CPU without correctly checking that certain CPU features are actually present. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> filters what CPU capabilities are presented to the guest operating system. Advanced users can attempt to restrict these virtual CPU capabilities with the <userinput>VBoxManage modifyvm --cpuid-portability-level</userinput> command. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    7459    </note>
    7560  </body>

  • trunk/doc/manual/en_US/dita/topics/terminate-vm-action.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/terminate-vm-default-action.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_categorize-isolate.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_config-periodic-flush.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99016 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="ts_config-periodic-flush">
    4   <title>Guest Shows IDE/SATA Errors for File-Based Images on Slow Host File
    5         System</title>
     4  <title><?oxy_comment_start author="Mhari Duncan" timestamp="20241210T152506+0000" comment="kespenla: This is not a true &quot;known issue&quot;, it is documenting that sluggish I/O on the host can cause I/O timeouts in the VM which may have usability problems. This is quite old (but stll true) information. Likely not as frequently seen as when this was originally written 15+ years ago."?>Guest Shows IDE/SATA Errors for File-Based Images on Slow Host File System<?oxy_comment_end?></title>
    65 
    76  <body>

  • trunk/doc/manual/en_US/dita/topics/ts_debugger.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105176 r107390  
    55 
    66  <body>
    7     <p>
    8         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes a built-in VM debugger, which advanced
    9         users may find useful. This debugger enables you to examine and,
    10         to some extent, control the VM state.
    11       </p>
     7    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes a built-in VM debugger, which advanced users may find useful. This debugger enables you to examine and, to some extent, control the VM state. </p>
    128    <note type="caution">
    13       <p>
    14           Use the VM debugger at your own risk. There is no support for
    15           it, and the following documentation is only made available for
    16           advanced users with a very high level of familiarity with the
    17           x86/AMD64 machine instruction set, as well as detailed
    18           knowledge of the PC architecture. A degree of familiarity with
    19           the internals of the guest OS in question may also be very
    20           helpful.
    21         </p>
     9      <p>Use the VM debugger at your own risk. There is no support for it, and the following documentation is only made available for advanced users with a very high level of familiarity with the x86/AMD64 machine instruction set, as well as detailed knowledge of the PC architecture. A degree of familiarity with the internals of the guest OS in question may also be very helpful. </p>
    2210    </note>
    23     <p>
    24         The VM debugger is available in all regular production versions
    25         of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but it is disabled by default because the
    26         average user will have little use for it. There are two ways to
    27         access the debugger:
    28       </p>
     11    <p>The VM debugger is available in all regular production versions of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but it is disabled by default because the average user will have little use for it. There are two ways to access the debugger:</p>
    2912    <ul>
    3013      <li>
    31         <p>
    32             Using a debugger console window displayed alongside the VM
    33           </p>
     14        <p>Using a debugger console window displayed alongside the VM</p>
    3415      </li>
    3516      <li>
    36         <p>
    37             Using the <userinput>telnet</userinput> protocol on port 5000
    38           </p>
     17        <p>Using the <userinput>telnet</userinput> protocol on port 5000</p>
    3918      </li>
    4019    </ul>
    … …  
    4423    <ul>
    4524      <li>
    46         <p>
    47             Start the VM directly using <userinput>VirtualBoxVM
    48             --startvm</userinput>, with an additional
    49             <codeph>--dbg</codeph>, <codeph>--debug</codeph>, or
    50             <codeph>--debug-command-line</codeph> argument. See the
    51             <userinput>VirtualBoxVM --help</userinput> command usage help
    52             for details.
    53           </p>
     25        <p>Start the VM directly using <userinput>VirtualBoxVM --startvm</userinput>, with an additional <codeph>--dbg</codeph>, <codeph>--debug</codeph>, or <codeph>--debug-command-line</codeph> argument. See the <userinput>VirtualBoxVM --help</userinput> command usage help for details.</p>
    5426      </li>
    5527      <li>
    56         <p>
    57             Set the <codeph>VBOX_GUI_DBG_ENABLED</codeph> or
    58             <codeph>VBOX_GUI_DBG_AUTO_SHOW</codeph> environment
    59             variable to <codeph>true</codeph> before launching the
    60             <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process. Setting these variables, only their
    61             presence is checked, is effective even when the first
    62             <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process is the VM selector window. VMs
    63             subsequently launched from the selector will have the
    64             debugger enabled.
    65           </p>
     28        <p>Set the <codeph>VBOX_GUI_DBG_ENABLED</codeph> or <codeph>VBOX_GUI_DBG_AUTO_SHOW</codeph> environment variable to <codeph>true</codeph> before launching the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process. Setting these variables, only their presence is checked, is effective even when the first <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process is the VM selector window. VMs subsequently launched from the selector will have the debugger enabled.</p>
    6629      </li>
    6730      <li>
    68         <p>
    69             Set the <codeph>GUI/Dbg/Enabled</codeph> extra data item
    70             to <codeph>true</codeph> before launching the VM. This can
    71             be set globally or on a per VM basis.
    72           </p>
     31        <p>Set the <codeph>GUI/Dbg/Enabled</codeph> extra data item to <codeph>true</codeph> before launching the VM. This can be set globally or on a per VM basis.</p>
    7332      </li>
    7433    </ul>
    75     <p>
    76         A new <b outputclass="bold">Debug</b> menu entry is added
    77         to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application. This menu enables the user to
    78         open the debugger console.
    79       </p>
    80     <p>
    81         The VM debugger command syntax is loosely modeled on Microsoft
    82         and IBM debuggers used on DOS, OS/2, and Windows. Users familiar
    83         with symdeb, CodeView, or the OS/2 kernel debugger will find the
    84         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM debugger familiar.
    85       </p>
    86     <p>
    87         The most important command is <userinput>help</userinput>. This will
    88         print brief usage help for all debugger commands. The set of
    89         commands supported by the VM debugger changes frequently and the
    90         <userinput>help</userinput> command is always up-to-date.
    91       </p>
    92     <p>
    93         A brief summary of frequently used commands is as follows:
    94       </p>
     34    <p>A new <b outputclass="bold">Debug</b> menu entry is added to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application. This menu enables the user to open the debugger console.</p>
     35    <p>The VM debugger command syntax is loosely modeled on Microsoft and IBM debuggers used on DOS, OS/2, and Windows. Users familiar with symdeb, CodeView, or the OS/2 kernel debugger will find the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM debugger familiar.</p>
     36    <p>The most important command is <userinput>help</userinput>. This will print brief usage help for all debugger commands. The set of commands supported by the VM debugger changes frequently and the <userinput>help</userinput> command is always up-to-date.</p>
     37    <p>A brief summary of frequently used commands is as follows:</p>
    9538    <ul>
    9639      <li>
    … …  
    12063      </li>
    12164      <li>
    122         <p><userinput>da</userinput>, <userinput>db</userinput>,
    123             <userinput>dw</userinput>, <userinput>dd</userinput>,
    124             <userinput>dq</userinput>: Print memory contents as ASCII,
    125             bytes, words, dwords, and qwords
    126           </p>
     65        <p><userinput>da</userinput>, <userinput>db</userinput>, <userinput>dw</userinput>, <userinput>dd</userinput>, <userinput>dq</userinput>: Print memory contents as ASCII, bytes, words, dwords, and qwords</p>
    12766      </li>
    12867      <li>
    … …  
    13170      </li>
    13271      <li>
    133         <p><userinput>dg</userinput>: Print the guest's GDT
    134           </p>
     72        <p><userinput>dg</userinput>: Print the guest's GDT</p>
    13573      </li>
    13674      <li>
    137         <p><userinput>di</userinput>: Print the guest's IDT
    138           </p>
     75        <p><userinput>di</userinput>: Print the guest's IDT</p>
    13976      </li>
    14077      <li>
    141         <p><userinput>dl</userinput>: Print the guest's LDT
    142           </p>
     78        <p><userinput>dl</userinput>: Print the guest's LDT</p>
    14379      </li>
    14480      <li>
    145         <p><userinput>dt</userinput>: Print the guest's TSS
    146           </p>
     81        <p><userinput>dt</userinput>: Print the guest's TSS</p>
    14782      </li>
    14883      <li>
    149         <p><userinput>dp*</userinput>: Print the guest's page table
    150             structures
    151           </p>
     84        <p><userinput>dp*</userinput>: Print the guest's page table structures</p>
    15285      </li>
    15386      <li>
    154         <p><userinput>bp</userinput> and <userinput>br</userinput>: Set a
    155             normal and recompiler breakpoint
    156           </p>
     87        <p><userinput>bp</userinput> and <userinput>br</userinput>: Set a normal and recompiler breakpoint</p>
    15788      </li>
    15889      <li>
    159         <p><userinput>bl</userinput>: List breakpoints
    160           </p>
     90        <p><userinput>bl</userinput>: List breakpoints</p>
    16191      </li>
    16292      <li>
    163         <p><userinput>bc</userinput>: Clear a breakpoint
    164           </p>
     93        <p><userinput>bc</userinput>: Clear a breakpoint</p>
    16594      </li>
    16695      <li>
    … …  
    16998      </li>
    17099    </ul>
    171     <p>
    172         See the built-in <userinput>help</userinput> for other available
    173         commands.
    174       </p>
    175     <p>
    176         The VM debugger supports symbolic debugging, although symbols
    177         for guest code are often not available. For Oracle Solaris
    178         guests, the <userinput>detect</userinput> command automatically
    179         determines the guest OS version and locates kernel symbols in
    180         guest's memory. Symbolic debugging is then available. For Linux
    181         guests, the <userinput>detect</userinput> commands also determines
    182         the guest OS version, but there are no symbols in the guest's
    183         memory. Kernel symbols are available in the file
    184         <filepath>/proc/kallsyms</filepath> on Linux guests. This file
    185         must be copied to the host, for example using
    186         <userinput>scp</userinput>. The <userinput>loadmap</userinput> debugger
    187         command can be used to make the symbol information available to
    188         the VM debugger. Note that the <filepath>kallsyms</filepath>
    189         file contains the symbols for the currently loaded modules. If
    190         the guest's configuration changes, the symbols will change as
    191         well and must be updated.
    192       </p>
    193     <p>
    194         For all guests, a simple way to verify that the correct symbols
    195         are loaded is the <userinput>k</userinput> command. The guest is
    196         normally idling and it should be clear from the symbolic
    197         information that the guest operating system's idle loop is being
    198         executed.
    199       </p>
    200     <p>
    201         Another group of debugger commands is the set of
    202         <userinput>info</userinput> commands. Running <userinput>info
    203         help</userinput> provides complete usage information. The
    204         information commands provide ad-hoc data pertinent to various
    205         emulated devices and aspects of the VMM. There is no general
    206         guideline for using the <userinput>info</userinput> commands, the
    207         right command to use depends entirely on the problem being
    208         investigated. Some of the <userinput>info</userinput> commands are
    209         as follows:
    210       </p>
     100    <p>See the built-in <userinput>help</userinput> for other available commands.</p>
     101    <p>The VM debugger supports symbolic debugging, although symbols for guest code are often not available. For Oracle Solaris guests, the <userinput>detect</userinput> command automatically determines the guest OS version and locates kernel symbols in guest's memory. Symbolic debugging is then available. For Linux guests, the <userinput>detect</userinput> commands also determines the guest OS version, but there are no symbols in the guest's memory. Kernel symbols are available in the file <filepath>/proc/kallsyms</filepath> on Linux guests. This file must be copied to the host, for example using <userinput>scp</userinput>. The <userinput>loadmap</userinput> debugger command can be used to make the symbol information available to the VM debugger. Note that the <filepath>kallsyms</filepath> file contains the symbols for the currently loaded modules. If the guest's configuration changes, the symbols will change as well and must be updated.</p>
     102    <p>For all guests, a simple way to verify that the correct symbols are loaded is the <userinput>k</userinput> command. The guest is normally idling and it should be clear from the symbolic information that the guest operating system's idle loop is being executed.</p>
     103    <p>Another group of debugger commands is the set of <userinput>info</userinput> commands. Running <userinput>info help</userinput> provides complete usage information. The information commands provide ad-hoc data pertinent to various emulated devices and aspects of the VMM. There is no general guideline for using the <userinput>info</userinput> commands, the right command to use depends entirely on the problem being investigated. Some of the <userinput>info</userinput> commands are as follows:</p>
    211104    <ul>
    212105      <li>
    … …  
    259152      </li>
    260153    </ul>
    261     <p>
    262         The output of the <userinput>info</userinput> commands generally
    263         requires in-depth knowledge of the emulated device or
    264         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VMM internals. However, when used properly, the
    265         information provided can be invaluable.
    266       </p>
     154    <p>The output of the <userinput>info</userinput> commands generally requires in-depth knowledge of the emulated device or <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VMM internals. However, when used properly, the information provided can be invaluable.</p>
    267155  </body>
    268156 

  • trunk/doc/manual/en_US/dita/topics/ts_general.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99016 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="ts_general">
    4   <title>General Troubleshooting</title>
     4  <title>General Issues</title>
    55 
    66  <body/>

  • trunk/doc/manual/en_US/dita/topics/ts_guest-core-format.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99797 r107390  
    55 
    66  <body>
    7     <p> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the 64-bit ELF format for its VM core files created by
    8         <userinput>VBoxManage debugvm</userinput>, see <xref href="vboxmanage-debugvm.dita"
    9         >VBoxManage debugvm</xref>. The VM core file contain the memory and CPU dumps of the VM and
    10       can be useful for debugging your guest OS. The 64-bit ELF object format specification can be
    11       obtained at: </p>
     7    <p>
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the 64-bit ELF format for its VM core files created by <userinput>VBoxManage debugvm</userinput>, see <xref href="../cli_topics/vboxmanage-debugvm.dita"/>. The VM core file contain the memory and CPU dumps of the VM and can be useful for debugging your guest OS. The 64-bit ELF object format specification can be obtained at: </p>
    129    <p><ph>http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf</ph>.
    1310      </p>

  • trunk/doc/manual/en_US/dita/topics/ts_host-freq-boost.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_host-freq-scaling.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_host-powermgmt.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_ide-sata-flush.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_lin-hosts.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_lin-x11-guests.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-buggy.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-guest-high-cpu.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99016 r107390  
    55 
    66  <body>
    7     <p>
    8         Some Linux guests may cause a high CPU load even if the guest
    9         system appears to be idle. This can be caused by a high timer
    10         frequency of the guest kernel. Some Linux distributions, for
    11         example Fedora, ship a Linux kernel configured for a timer
    12         frequency of 1000Hz. We recommend to recompile the guest kernel
    13         and to select a timer frequency of 100Hz.
    14       </p>
    15     <p>
    16         Linux kernels shipped with Red Hat Enterprise Linux, as well as
    17         kernels of related Linux distributions, such as CentOS and
    18         Oracle Linux, support a kernel parameter
    19         <i>divider=N</i>. Hence, such kernels support a
    20         lower timer frequency without recompilation. We suggest you add
    21         the kernel parameter <i>divider=10</i> to select a
    22         guest kernel timer frequency of 100Hz.
    23       </p>
     7    <p>Some legacy Linux guests may cause a high CPU load even if the guest system appears to be idle. This can be caused by a high timer frequency of the guest kernel. Some older Linux distributions ship a Linux kernel configured for a timer frequency of 1000Hz. We recommend recompiling the guest kernel and selecting a timer frequency of 100Hz.</p>
     8    <p> Linux kernels shipped with Red Hat Enterprise Linux, as well as kernels of related Linux distributions, such as CentOS and Oracle Linux, support a kernel parameter <i>divider=N</i>. Hence, such kernels support a lower timer frequency without recompilation. We suggest you add the kernel parameter <i>divider=10</i> to select a guest kernel timer frequency of 100Hz.</p>
    249  </body>
    2510 

  • trunk/doc/manual/en_US/dita/topics/ts_linux-guest-x11-services.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105134 r107390  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="ts_linux-guest-x11-services">
    4   <title>Shared Clipboard, Auto-Resizing, and Seamless Desktop in X11 Guests</title>
     4  <title><?oxy_comment_start author="Mhari Duncan" timestamp="20241217T155049+0000" comment="Consider moving the &apos;processes&apos; info to here, and making this a section with &apos;what should be running, where, and how to check.&apos;"?>Shared Clipboard, Auto-Resizing, and Seamless Desktop in X11 Guests<?oxy_comment_end?></title>
    55 
    66  <body>
    7     <p>
    8         Guest desktop services in guests running the X11 window system
    9         such as Oracle Solaris and Linux, are provided by a guest
    10         service called <userinput>VBoxClient</userinput>, which runs under
    11         the ID of the user who started the desktop session and is
    12         automatically started using the following command lines when
    13         your X11 user session is started if you are using a common
    14         desktop environment such as Gnome or KDE.
    15       </p>
     7    <p>Guest desktop services in guests running the X11 window system such as Oracle Solaris and Linux, are provided by a guest service called <userinput>VBoxClient</userinput>, which runs under the ID of the user who started the desktop session and is automatically started using the following command lines when your X11 user session is started if you are using a common desktop environment such as Gnome or KDE.</p>
    168    <pre xml:space="preserve">$ VBoxClient --clipboard
    179$ VBoxClient --display
    1810$ VBoxClient --seamless</pre>
    19     <p>
    20         If a particular desktop service is not working correctly, it is
    21         worth checking whether the process which should provide it is
    22         running.
    23       </p>
    24     <p> The <userinput>VBoxClient</userinput> processes create files in the user's home directory
    25       with names of the form <filepath>.vboxclient-*.pid</filepath> when they are running in order
    26       to prevent a given service from being started twice. It can happen due to misconfiguration
    27       that these files are created owned by root and not deleted when the services are stopped,
    28       which will prevent them from being started in future sessions. If the services cannot be
    29       started, you may want to check whether these files still exist. </p>
     11    <p>If a particular desktop service is not working correctly, it is worth checking whether the process which should provide it is running.</p>
     12    <p>The <userinput>VBoxClient</userinput> processes create files in the user's home directory with names of the form <filepath>.vboxclient-*.pid</filepath> when they are running in order to prevent a given service from being started twice. It can happen due to misconfiguration that these files are created owned by root and not deleted when the services are stopped, which will prevent them from being started in future sessions. If the services cannot be started, you may want to check whether these files still exist.</p>
    3013  </body>
    3114 

  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-cd-dvd-not-found.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-grsec.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-ide-messages.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-malloc.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-vboxsvc.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_linux-kernelmodule-fails-to-load.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_sol-guests.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_sol-host-zfs.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_sol-hosts.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_solaris-10-guest-slow-boot-smp.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_usb-linux.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_vboxbugreport.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99797 r107390  
    66 
    77  <body>
    8     <p>
    9         The <userinput>VBoxBugReport</userinput> command is used to collect
    10         debug information automatically for an <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    11         installation. This command can be useful when you need to gather
    12         information to send to Oracle Support.
    13       </p>
    14     <p>
    15         The following examples show how to use
    16         <userinput>VBoxBugReport</userinput>.
    17       </p>
    18     <p>
    19         By default, the command collects <userinput>VBoxSVC</userinput>
    20         process logs, device settings, and global configuration data for
    21         an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host.
    22       </p>
     8    <p>The <userinput>VBoxBugReport</userinput> command is used to collect debug information automatically for an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation. This command can be useful when you need to gather information to send to Oracle Support.</p>
     9    <p>The following examples show how to use <userinput>VBoxBugReport</userinput>.</p>
     10    <p>By default, the command collects <userinput>VBoxSVC</userinput> process logs, device settings, and global configuration data for an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host.</p>
    2311    <pre xml:space="preserve">$ VBoxBugReport
    2412  ...
    … …  
    3422
    3523Report was written to '2019-03-26-13-32-02-bugreport.tgz'</pre>
    36     <p>
    37         The results are saved as a compressed tar file archive in the
    38         same directory where the command is run.
    39       </p>
    40     <p>
    41         To specify a different output file location:
    42       </p>
     24    <p>The results are saved as a compressed tar file archive in the same directory where the command is run.</p>
     25    <p>To specify a different output file location:</p>
    4326    <pre xml:space="preserve">$ VBoxBugReport --output ~/debug/bug004.tgz</pre>
    44     <p>
    45         To output all debug information to a single text file, rather
    46         than a <filepath>tgz</filepath> file:
    47       </p>
     27    <p>To output all debug information to a single text file, rather than a <filepath>tgz</filepath> file:</p>
    4828    <pre xml:space="preserve">$ VBoxBugReport --text</pre>
    49     <p>
    50         To collect information for a specific VM, called
    51         <codeph>Windows_10</codeph>:
    52       </p>
     29    <p>To collect information for a specific VM, called <codeph>Windows_10</codeph>:</p>
    5330    <pre xml:space="preserve">$ VBoxBugReport Windows_10</pre>
    54     <p>
    55         This command collects machine settings, guest properties, and
    56         log files for the specified VM. Global configuration information
    57         for the host is also included.
    58       </p>
    59     <p>
    60         To collect information for several VMs, called
    61         <codeph>Windows_7</codeph>, <codeph>Windows_8</codeph>, and
    62         <codeph>Windows_10</codeph>:
    63       </p>
     31    <p>This command collects machine settings, guest properties, and log files for the specified VM. Global configuration information for the host is also included.</p>
     32    <p>To collect information for several VMs, called <codeph>Windows_7</codeph>, <codeph>Windows_8</codeph>, and <codeph>Windows_10</codeph>:</p>
    6433    <pre xml:space="preserve">$ VBoxBugReport Windows_7 Windows_8 Windows_10</pre>
    65     <p>
    66         To collect information for all VMs:
    67       </p>
     34    <p>To collect information for all VMs:</p>
    6835    <pre xml:space="preserve">$ VBoxBugReport --all</pre>
    69     <p>
    70         To show a full list of the available command options, run
    71         <userinput>VBoxBugReport --help</userinput>.
    72       </p>
     36    <p>To show a full list of the available command options, run <userinput>VBoxBugReport --help</userinput>.</p>
    7337  </body>
    7438 

  • trunk/doc/manual/en_US/dita/topics/ts_win-cpu-usage-rept.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-active-dir-domain.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-bluescreen-record-info.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-bluescreen.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-high-cpu.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-shared-folders-access-delay.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-guests.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-host-bridged-network-adapters.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-host-cd-dvd-changes.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-host-com-server.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99797 r107390  
    66  <body>
    77    <p>
    8         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of the Microsoft Component Object Model
    9         (COM) for interprocess and intraprocess communication. This
    10         enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to share a common configuration among
    11         different virtual machine processes and provide several user
    12         interface options based on a common architecture. All global
    13         status information and configuration is maintained by the
    14         process <filepath>VBoxSVC.exe</filepath>, which is an
    15         out-of-process COM server. Whenever an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process is
    16         started, it requests access to the COM server and Windows
    17         automatically starts the process. Note that it should never be
    18         started by the end user.
    19       </p>
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of the Microsoft Component Object Model (COM) for interprocess and intraprocess communication. This enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to share a common configuration among different virtual machine processes and provide several user interface options based on a common architecture. All global status information and configuration is maintained by the process <filepath>VBoxSVC.exe</filepath>, which is an out-of-process COM server. Whenever an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process is started, it requests access to the COM server and Windows automatically starts the process. Note that it should never be started by the end user.</p>
    209    <p>
    2110        When the last process disconnects from the COM server, it will
    … …  
    2413        server and the files are locked whenever the server runs.
    2514      </p>
    26     <p>
    27         In some cases, such as when a virtual machine is terminated
    28         unexpectedly, the COM server will not notice that the client is
    29         disconnected and stay active for a longer period of 10 minutes
    30         or so, keeping the configuration files locked. In other rare
    31         cases the COM server might experience an internal error and
    32         subsequently other processes fail to initialize it. In these
    33         situations, it is recommended to use the Windows task manager to
    34         kill the process <filepath>VBoxSVC.exe</filepath>.
    35       </p>
     15    <p> In some cases, such as when a virtual machine is terminated unexpectedly, the COM server will not notice that the client is disconnected and stay active for a longer period of 10 minutes or so, keeping the configuration files locked. In other rare cases the COM server might experience an internal error and subsequently other processes fail to initialize it. In these situations, use the Windows task manager to kill the process <filepath>VBoxSVC.exe</filepath>.</p>
    3616  </body>
    3717 

  • trunk/doc/manual/en_US/dita/topics/ts_win-host-host-only-network-adapters.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-host-iscsi.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-host-rdp-client.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-hosts.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win-vista-guest-networking.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win2k-guest-install.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win31-ram-limitations.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win7-guest-usb3-support.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ts_win98-guest-usb-tablet-coordinates.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/ui-experience-level.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/unattended-guest-install-example.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/uninstall-solaris-host.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usb-implementation-notes.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usb-over-rdp.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usb-support.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usbip-security.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usbip-setup-server.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usbip.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/usbtrafficcapturing.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/user-interface.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vbox-auth.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105941 r107390  
    55 
    66  <body>
    7     <p>For each virtual machine that is remotely accessible using RDP, you can individually determine if and how client
    8       connections are authenticated. For this, use the <userinput>VBoxManage modifyvm</userinput> command with the
    9         <codeph>--vrde-auth-type</codeph> option. See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>.
    10       The following methods of authentication are available: </p>
     7    <p>For each virtual machine that is remotely accessible using RDP, you can individually determine if and how client connections are authenticated. For this, use the <userinput>VBoxManage modifyvm</userinput> command with the <codeph>--vrde-auth-type</codeph> option. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>. The following methods of authentication are available: </p>
    118    <ul>
    129      <li>

  • trunk/doc/manual/en_US/dita/topics/vboxandsolzvmm.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxbowsolaris11.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxbowvnictemplates.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-XML-files.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-global.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105303 r107390  
    8989        change the location of its snapshots folder in the VM settings.
    9090      </p>
    91     <p> You can change the default machine folder by selecting <b outputclass="bold">Preferences</b>
    92       from the <b outputclass="bold">File</b> menu in the <ph
    93         conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in the displayed
    94       window, click the <b outputclass="bold">General</b> tab. Alternatively, use the
    95         <userinput>VBoxManage setproperty machinefolder</userinput> command. See <xref
    96         href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>. </p>
     91    <p> You can change the default machine folder by selecting <b outputclass="bold">Preferences</b> from the <b outputclass="bold">File</b> menu in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in the displayed window, click the <b outputclass="bold">General</b> tab. Alternatively, use the <userinput>VBoxManage setproperty machinefolder</userinput> command. See <xref href="../cli_topics/vboxmanage-setproperty.dita"/>.</p>
    9792  </body>
    9893 

  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-summary-locations.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxexpertstoragemgmt.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboximg-mount-display.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboximg-mount-steps.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboximg-mount.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r99797 r107390  
    44<topic xml:lang="en-us" id="vboximg-mount">
    55            <title>vboximg-mount: A Utility for FUSE Mounting a Virtual Disk Image</title>
    6            
     6
    77            <body>
    88               <p>
    … …  
    6161      the <userinput>vboximg-mount</userinput> command usage. The complete
    6262      command reference is described in
    63       <xref href="man_vboximg-mount.dita"/>.
     63      <xref href="../cli_topics/man_vboximg-mount.dita"/>.
    6464    </p>
    6565               <p>
    … …  
    7373    </p>
    7474            </body>
    75            
    76            
     75
     76
    7777         </topic>

  • trunk/doc/manual/en_US/dita/topics/vboxmanage-intro.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r106204 r107390  
    44<topic xml:lang="en-us" id="vboxmanage-intro">
    55            <title>Introduction</title>
    6 
     6           
    77            <body>
    88               <p><userinput>VBoxManage</userinput> is the CLI to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. With it, you can control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from the command line of the host operating system. <userinput>VBoxManage</userinput> supports all the features that the graphical user interface gives you access to, plus the features of the virtualization engine that can't be accessed from the GUI. </p>
    … …  
    1919                  </li>
    2020               </ul>
    21                <p>For more information, refer to the VBoxManage command <xref href="../topics/vboxmanage-common-description.dita"/> and <xref href="../topics/vboxmanage-common-examples.dita"/>.</p>
     21               <p>For more information, refer to the VBoxManage command <xref href="../cli_topics/vboxmanage-common-description.dita"/> and <xref href="../cli_topics/vboxmanage-common-examples.dita"/>.</p>
    2222            </body>
    23 
     23           
    2424         </topic>

  • trunk/doc/manual/en_US/dita/topics/vboxmanage.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxsvc-session-0-known-issues.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxsvc-session-0.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-ballonctrl.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-hostisln.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-linux.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-moreinfo.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-solaris.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-daemon.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-linux.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-osx.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-solaris.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vdidetails.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105335 r107390  
    99      certain geometry. When a guest OS reads from or writes to a hard disk, <ph
    1010        conkeyref="vbox-conkeyref-phrases/product-name"/> redirects the request to the image file. </p>
    11                <p>Like a physical disk, a virtual disk has a size, or capacity, which must be specified when the image
    12       file is created. As opposed to a physical disk however, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    13       enables you to expand an image file after creation, even if it has data already. See <xref
    14         href="vboxmanage-modifymedium.dita"/>. </p>
     11               <p>Like a physical disk, a virtual disk has a size, or capacity, which must be specified when the image file is created. As opposed to a physical disk however, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to expand an image file after creation, even if it has data already. See <xref href="../cli_topics/vboxmanage-modifymedium.dita"/>.</p>
    1512               <p>
    1613      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the following types of disk image files:

  • trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/virtintro.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105941 r107390  
    1111               <ul>
    1212                  <li>
    13                      <p><b outputclass="bold">Host operating system (host OS).</b> This is the OS of the physical
    14           computer on which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> was installed. There are versions of
    15             <ph conkeyref="vbox-conkeyref-phrases/product-name"/> for Windows, macOS, Linux, and Oracle Solaris hosts.
    16           See <xref href="hostossupport.dita#hostossupport"/>. </p>
     13                     <p><b outputclass="bold">Host operating system (host OS).</b> This is the OS of the physical computer on which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> was installed. There are versions of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> for Windows, macOS, Linux, and Oracle Solaris hosts. See <xref href="installation-packages.dita"/>.</p>
    1714                     <p>Most of the time, this user guide discusses all <ph
    1815            conkeyref="vbox-conkeyref-phrases/product-name"/> versions together. There may be platform-specific

  • trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vm-activity-session-information.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vm-info.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vm-status-bar.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vmencryption-addpassword.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vmencryption-decryption.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vmencryption-encryption.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vmencryption-limitations.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vmencryption.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vrde-crypt.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vrde-customization.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vrde-multiconnection.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vrde-multimonitor.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vrde-videochannel.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/vrde.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision
    r105335 r107390  
    1515        href="intro-installing.dita">Installing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Extension
    1616        Packs</xref>. </p>
    17     <p>Oracle provides support for the VirtualBox Remote Display Protocol (VRDP) in such an <ph
    18         conkeyref="vbox-conkeyref-phrases/product-name"/> extension package. </p>
    19     <p>VRDP is a backward-compatible extension to Microsoft's Remote Desktop Protocol (RDP). As a result, you can use
    20       any standard RDP client to control the remote VM. </p>
     17    <p>Oracle provides support for the VirtualBox Remote Display Protocol (VRDP) in such an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension package.</p>
     18    <p>VRDP is a backward-compatible extension to Microsoft's Remote Desktop Protocol (RDP). As a result, you can use any standard RDP client to control the remote VM.</p>
    2119    <p>Even when the extension is installed, the VRDP server is disabled by default. It can easily be enabled on a
    2220      per-VM basis either from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> in the <b outputclass="bold"
    … …  
    2422        <userinput>VBoxManage</userinput> command, as follows: </p>
    2523    <pre xml:space="preserve">$ VBoxManage modifyvm <varname>VM-name</varname> --vrde on</pre>
    26     <p>By default, the VRDP server uses TCP port <codeph>3389</codeph>. You will need to change the default port if you
    27       run more than one VRDP server, since the port can only be used by one server at a time. You might also need to
    28       change it on Windows hosts since the default port might already be used by the RDP server that is built into
    29       Windows itself. Ports 5000 through 5050 are typically not used and might be a good choice. </p>
    30     <p>The port can be changed either in the <b outputclass="bold">Display</b> settings of the graphical user interface
    31       or with the <codeph>--vrde-port</codeph> option of the <userinput>VBoxManage modifyvm</userinput> command. You can
    32       specify a comma-separated list of ports or ranges of ports. Use a dash between two port numbers to specify a
    33       range. The VRDP server will bind to <i>one</i> of the available ports from the specified list. For example,
    34         <userinput>VBoxManage modifyvm <varname>VM-name</varname> --vrde-port 5000,5010-5012</userinput> configures the
    35       server to bind to one of the ports 5000, 5010, 5011, or 5012. See <xref href="vboxmanage-modifyvm.dita">VBoxManage
    36         modifyvm</xref>. </p>
     24    <p>The RDP server in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension pack supports only audio streams in format 22.05kHz stereo 16-bit. If the RDP client requests any other audio format there will be no audio.</p>
     25    <p>By default, the VRDP server uses TCP port <codeph>3389</codeph>. You will need to change the default port if you run more than one VRDP server, since the port can only be used by one server at a time. You might also need to change it on Windows hosts since the default port might already be used by the RDP server that is built into Windows itself. Ports 5000 through 5050 are typically not used and might be a good choice.</p>
     26    <p>The port can be changed either in the <b outputclass="bold">Display</b> settings of the graphical user interface or with the <codeph>--vrde-port</codeph> option of the <userinput>VBoxManage modifyvm</userinput> command. You can specify a comma-separated list of ports or ranges of ports. Use a dash between two port numbers to specify a range. The VRDP server will bind to <i>one</i> of the available ports from the specified list. For example, <userinput>VBoxManage modifyvm <varname>VM-name</varname> --vrde-port 5000,5010-5012</userinput> configures the server to bind to one of the ports 5000, 5010, 5011, or 5012. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    3727    <p>The actual port used by a running VM can be either queried with the <userinput>VBoxManage showvminfo</userinput>
    3828      command or seen in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> on the <b outputclass="bold">Runtime</b> tab
    3929      of the <b outputclass="bold">Session Information</b> dialog, which is accessible from the <b outputclass="bold"
    4030        >Machine</b> menu of the VM window. </p>
    41     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports IPv6. If the host OS supports IPv6 the VRDP server
    42       will automatically listen for IPv6 connections in addition to IPv4. </p>
     31    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports IPv6. If the host OS supports IPv6 the VRDP server will automatically listen for IPv6 connections in addition to IPv4.</p>
    4332  </body>
    4433</topic>

  • trunk/doc/manual/en_US/dita/topics/warpguest.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/webcam-linux-hosts.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/webcam-mac-hosts.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/webcam-passthrough.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/webcam-using-guest.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/webcam-win-hosts.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/dita/topics/windows-guest-file-extraction.dita

    • Property svn:keywords changed from Id Revision to Author Date Id Revision

  • trunk/doc/manual/en_US/man_VBoxHeadless.xml

    r106061 r107390  
    8080    <para>
    8181      For information about using this command, see
    82       <xref linkend="vboxheadless" />.
     82      <xref linkend="headless-mode" />.
    8383    </para>
    8484    <refsect2 id="man_vboxmanage-vboxheadless-command-options">

  • trunk/doc/manual/en_US/man_VBoxManage-controlvm.xml

    r106061 r107390  
    12451245      <para>
    12461246        See also the <option>--vrde-port</option> option description in
    1247         <xref linkend="vboxmanage-modifyvm-vrde" />.
     1247        <xref linkend="vboxmanage-modifyvm" />.
    12481248      </para>
    12491249    </refsect2>
    … …  
    12651265          </para><para>
    12661266            See also the <option>--vrde-port</option> option description
    1267             in <xref linkend="vboxmanage-modifyvm-vrde" />.
     1267            in <xref linkend="vboxmanage-modifyvm" />.
    12681268          </para></listitem>
    12691269        <listitem><para>
    … …  
    12741274          </para><para>
    12751275            See also the <option>--vrde-address</option> option
    1276             description in <xref linkend="vboxmanage-modifyvm-vrde" />.
     1276            description in <xref linkend="vboxmanage-modifyvm" />.
    12771277          </para></listitem>
    12781278        <listitem><para>

  • trunk/doc/manual/en_US/man_VBoxManage-guestcontrol.xml

    r106061 r107390  
    513513          graphical user interface applications launched using
    514514          <command>VBoxManage guestcontrol run</command>. See
    515           <xref linkend="KnownIssues" />.
     515          <xref linkend="known-issues" />.
    516516        </para>
    517517      </note>
    … …  
    683683          graphical user interface applications launched using
    684684          <command>VBoxManage guestcontrol start</command>. See
    685           <xref linkend="KnownIssues" />.
     685          <xref linkend="known-issues" />.
    686686        </para>
    687687      </note>

  • trunk/doc/manual/en_US/man_VBoxManage-startvm.xml

    r106061 r107390  
    187187    <title>See Also</title>
    188188    <para>
    189 <!--<xref linkend="vboxmanage-vboxheadless" />-->
    190       <xref linkend="vboxheadless" />,
     189      <xref linkend="headless-mode" />,
    191190      <xref linkend="vboxmanage-setproperty" />,
    192191      <xref linkend="vboxmanage-modifyvm" />.

  • trunk/doc/manual/ru_RU/man_VBoxManage-startvm.xml

    r106061 r107390  
    167167    <para>
    168168<!--<xref linkend="vboxmanage-vboxheadless" />-->
    169       <xref linkend="vboxheadless" />,
     169      <!-- <xref linkend="vboxheadless" />, -->
    170170      <xref linkend="vboxmanage-setproperty" />,
    171171      <xref linkend="vboxmanage-modifyvm" />.
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette