VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/sharedfolders.dita@ 105134

最後變更 在這個檔案從105134是 105134,由 vboxsync 提交於 9 月 前

Docs: bugref:10705. This is a merge commit to introduce doc team's changes in the user manual dita files. The following files
are excluded from this process:

  • Files whose names satrt with "viso", "vboxmanage", "man_", "vboximg", "vboxheadless", or "user_isomakercmd-man".

And general notes about this merge are as follows:

  • For now I leave glossentry-*dita file as they are since we use different enclosing dita elements
  • in hdimagewrites.dita we have <note type="attention"> while doc team's copy has <note type="caution">. Not sure if this is significant.

For now I copy doc team's version over.

  • I have not modified our UserManual.ditamap file. This will be done in a follow up commit.

The list of commits we have merged are as follows:

r3392: 7.1 new features; add comments to some DITA topics
r3730: VBP-283: Update supported platforms; 7.0 and 7.1
r3980: 7.1: reset menu option; add note
r3992: ARM hosts; add draft topic on limitations; add container topic for ARM-based subtopics
r3993: ARM create new VM wizard: add some dummy topics
r4014: ER 34784410 DOCUMENT THE VIRTUAL MACHINE TASKBAR ICONS: port topic and icon graphics from 7.0 tree
r4026: VBP-378: status bar icons; remove any mention of task bar; ported from 7.0
r4034: Cloning a cloud VM; add draft topic
r4035: Cloning a cloud VM;typo
r4036: Cloning a cloud VM;add xref from intro topic
r4050: Reset operation; add instructions
r4051: Amend comment
r4052: Ditaval markup for images
r4056: Add ditaval markup for images
r4057: Add ditaval markup for images
r4058: Add ditaval markup for images
r4073: UI experience level: add dummy topic
r4075: Subtype: option for VM settings General tab and Create VM wizard
r4094: Cloud VM reset; add to relnotes
r4095: Reset VM; use main Machine menu, rather than right-click menu
r4099: ARM hosts; draft revisions to cover different wizard screens
r4134: Cloud VMs: file manager menu option; add comment
r4214: Settings page, Motherboard tab: Chipset option for Arm VMs; add note
r4306: Terminology checker: clear up Errors; Installation chapter
r4307: Terminology checker: clear up Errors; Config settings/GA chapters
r4308: Terminology checker: clear up Errors; Storage, networking, remote VM chapters
r4311: Terminology checker: clear up Errors: various
r4324: Prefences and settings; potential areas for change in 7.1
r4356: r160214: Monitoring cloud VM performance; add new topic
r4358: r160214: Monitoring cloud VM performance; add new topic
r4364: r160214: Monitoring cloud VM performance; redraft topic
r4374: Experience levels; update user manual topic
r4377: Experience levels; Preferences window: add note re. availability of all possible settings
r4378: Experience levels; Preferences window: add note re. availability of all possible settingsLp
r4379: Typos and add remark re. Global menu changes
r4387: Preferences, Display: some settings introduced post-7.0: font scaling and extended features
r4388: Performance monitoring: add cloud VM instances to intro para
r4389: Experience levels: selecting a level, add graphic of icon
r4391: Resource monitoring; add CLI example to show CPU usage for a cloud instance
r4395: Experience levels; apply to menu items only
r4398: Experience levels; add notes
r4401: Experience levels; remove pics of global tools menu/machine tools menu; number of menu items can vary
r4402: Experience levels; remove image files for global tools menu/machine tools menu
r4525: Experience levels: minor redraft
r4528: Typo
r4538: Experience levels: selected level applies throughout VirtualBox Manager GUI
r4543: GUI topics; add notes for required changes
r4544: VISO Creator changes
r4563: r160714: unattended guest install example; now has user-password option
r4569: Terminology: front end, not front-end
r4570: Arm wizard screens; remove, as Create VM Wizard will be very similar regardless of architecture
r4571: Arm wizard screens; remove, as Create VM Wizard will be very similar regardless of architecture
r4623: Cloud VM monitoring: Compute Instance Monitoring plugin must be enabled; add note
r4625: CPU activity icon; update, now has solid bar
r4626: GUI changes; various, from Serkan; includes new pic for soft keyboard
r4629: separate mode: add some draft topics, will need to get technical review at a later stage
r4634: GUI; various notes and updates
r4655: Typo
r4703: Arm host platform limitations; redraft and add topic to host OS section
r4724: VISO creator; add notes re. ISO import
r4725: Separate mode: edits
r4863: r161176; Python 2.x no longer supported for API
r4899: Arm host support: limitations
r4910: Create VM wizard: settings may vary x86 vs. Arm hosts
r4911: Guest OS support; add note re. supported aarch64 OSes
r4973: r161445: Remove mention of parallel port support
r5004: Cloud VM monitoring: detailed data graphs and Activity Overview
r5038: Cloud VM monitoring: export to file
r5214: r161947: Solaris non-Global zone configuration
r5215: r161947: Solaris non-Global zone configuration; typo
r5230: Glossary: fix title for I/O APIC topic
r5341: Experience levels; can be selected from welcome screen in VirtualBox Manager; need replacement pic
r5345: Experience levels; add note on Welcome screen option
r5346: Arm host limitations; unavailable System settings
r5434: r162377: shared folders; symlinks behaviour
r5565: Cloud VM list in VirtualBox Manager; show mixed VM types; screenshot from Klaus
r5627: Obfuscate UUID data in screen shot
r5628: Delete legacy cloudvm pic; use mixed VMs example
r5654: Clean up comments in source files; redraft VM activity section
r5672: 7.1 changes; add comments
r5683: 7.1 changes; add comments for Arm topics
r5687: 7.1 changes; GUI; add comments
r5703: Oracle notices; include up to date versions in preface-* topics for User Guide
r5707: r162904: Windows install directory requirements; redraft
r5781: updated GNU version from 2 to 3 as per r163272
r5812: started removal of screenshots and updating tasks VBP-807
r5818: Further updates to creating a VM VBP-807
r5822: Restructured topics and made task based VBP-807
r5824: Removed files during restructure VBP-807
r5834: Fixed formatting of note and caution VBP-807
r5836: Updated supported host OS list VBP-825
r5837: updated USB topics for VBP-823
r5842: changes as per legal request re supported guests VBP-843
r5853: Updated versions following review. VBP-825


  • 屬性 svn:eol-style 設為 native
  • 屬性 svn:keywords 設為 Id Revision
檔案大小: 5.9 KB
 
1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE topic
3 PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
4<topic xml:lang="en-us" id="sharedfolders">
5 <title>Shared Folders</title>
6
7 <body>
8 <p>
9 With the <i>shared folders</i> feature of
10 <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can access files of your host system from
11 within the guest system. This is similar to how you would use
12 network shares in Windows networks, except that shared folders do
13 not require networking, only the Guest Additions. Shared folders
14 are supported with Windows 2000 or later, Linux, and Oracle
15 Solaris guests. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for
16 Mac OS X and OS/2 guests.
17 </p>
18 <p>
19 Shared folders physically reside on the <i>host</i>
20 and are then shared with the guest, which uses a special file
21 system driver in the Guest Additions to talk to the host. For
22 Windows guests, shared folders are implemented as a pseudo-network
23 redirector. For Linux and Oracle Solaris guests, the Guest
24 Additions provide a virtual file system.
25 </p>
26 <p>
27 To share a host folder with a virtual machine in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
28 you must specify the path of the folder and choose a
29 <i>share name</i> that the guest can use to access
30 the shared folder. This happens on the host. In the guest you can
31 then use the share name to connect to it and access files.
32 </p>
33 <p>
34 There are several ways in which shared folders can be set up for a
35 virtual machine:
36 </p>
37 <ul>
38 <li>
39 <p> In the window of a running VM, you select <b outputclass="bold">Shared
40 Folders</b> from the <b outputclass="bold">Devices</b> menu, or click the folder icon on
41 the status bar in the bottom right corner. </p>
42 </li>
43 <li>
44 <p>
45 If a VM is not currently running, you can configure shared
46 folders in the virtual machine's
47 <b outputclass="bold">Settings</b> window.
48 </p>
49 </li>
50 <li>
51 <p>
52 From the command line, you can create shared folders using
53 <userinput>VBoxManage</userinput>, as follows:
54 </p>
55 <pre xml:space="preserve">VBoxManage sharedfolder add "VM name" --name "sharename" --hostpath "C:\test"</pre>
56 <p> See <xref href="vboxmanage-sharedfolder.dita"/>. </p>
57 </li>
58 </ul>
59 <p>
60 There are two types of shares:
61 </p>
62 <ul>
63 <li>
64 <p>
65 Permanent shares, that are saved with the VM settings.
66 </p>
67 </li>
68 <li>
69 <p>
70 Transient shares, that are added at runtime and disappear when
71 the VM is powered off. These can be created using a check box
72 in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or by using the <codeph>--transient</codeph>
73 option of the <userinput>VBoxManage sharedfolder add</userinput>
74 command.
75 </p>
76 </li>
77 </ul>
78 <p>
79 Shared folders can either be read-write or read-only. This means
80 that the guest is either allowed to both read and write, or just
81 read files on the host. By default, shared folders are read-write.
82 Read-only folders can be created using a check box in the
83 <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or with the <codeph>--readonly option</codeph> of the
84 <userinput>VBoxManage sharedfolder add</userinput> command.
85 </p>
86 <p>
87 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> shared folders also support symbolic links, also
88 called <i>symlinks</i>, under the following
89 conditions:
90 </p>
91 <ul>
92 <li>
93 <p>
94 The host operating system must support symlinks. For example,
95 a macOS, Linux, or Oracle Solaris host is required.
96 </p>
97 </li>
98 <li>
99 <p>
100 The guest VM must have a version of the Guest Additions
101 installed which supports symlinks. Currently only the Linux and
102 Oracle Solaris Guest Additions support symlinks.
103 </p>
104 </li>
105 <li>
106 <p>
107 For security reasons the guest OS is not allowed to create
108 symlinks by default. If you trust the guest OS to not abuse
109 this functionality, you can enable the creation of symlinks for
110 a shared folder as follows:
111 </p>
112 <pre xml:space="preserve">VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/SharedFoldersEnableSymlinksCreate/<varname>sharename</varname> 1</pre>
113 </li>
114 </ul>
115 <p>
116 If a symbolic link is created inside a shared folder on the host
117 and the installed Guest Additions do not support symbolic links
118 then the guest will see the target of the symlink as a file
119 inside the shared folder. For example, if a symlink is created
120 to a file on a Linux host:
121 </p>
122 <p>
123 <pre xml:space="preserve">$ cd /SharedFolder &amp;&amp; ln -s filename symlink-to-filename</pre>
124 </p>
125 <p>
126 When the shared folder is viewed on a Windows guest there
127 will be two identical files listed, <userinput>filename</userinput>
128 and <userinput>symlink-to-filename</userinput>.
129 </p>
130 </body>
131
132
133 </topic>
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

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