VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita@ 107390

Last change on this file since 107390 was 107390, checked in by vboxsync, 3 months ago

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

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 8.7 KB
Line 
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="virtual-media-manager">
5 <title>The Virtual Media Manager</title>
6
7 <body>
8 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> keeps track of all the hard disk, CD/DVD-ROM,
9 and floppy disk images which are in use by virtual machines. These are often referred to as <i>known media</i> and
10 come from two sources: </p>
11 <ul>
12 <li>
13 <p>All media currently attached to virtual machines. </p>
14 </li>
15 <li>
16 <p>Registered media, for compatibility with legacy <ph
17 conkeyref="vbox-conkeyref-phrases/product-name"/> versions. </p>
18 </li>
19 </ul>
20 <p>The known media can be viewed and changed using the <b outputclass="bold">Virtual Media Manager</b>
21 tool, which you access by clicking <b outputclass="bold">Media</b> on the global <b outputclass="bold">Tools</b>
22 menu in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
23 <p>The known media are conveniently grouped in separate tabs for the supported formats. These formats
24 are: </p>
25 <ul>
26 <li>
27 <p>Hard disk images, either in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s own Virtual
28 Disk Image (VDI) format, or in the third-party formats listed in <xref href="vdidetails.dita#vdidetails"
29 />. </p>
30 </li>
31 <li>
32 <p>CD/DVD images in standard ISO format. </p>
33 </li>
34 <li>
35 <p>Floppy images in standard RAW format. </p>
36 </li>
37 </ul>
38 <p>For each image, the Virtual Media Manager shows you the full path of the image file and other
39 information, such as the virtual machine the image is currently attached to. </p>
40 <p>The Virtual Media Manager enables you to do the following: </p>
41 <ul>
42 <li>
43 <p><b outputclass="bold">Add</b> an image to the known media. </p>
44 </li>
45 <li>
46 <p><b outputclass="bold">Create</b> a new disk image. </p>
47 <ul>
48 <li>
49 <p>For hard disks, the <b outputclass="bold">Create Virtual Hard Disk</b> wizard is shown.
50 See <xref href="create-virtual-hard-disk-image.dita#create-virtual-hard-disk-image"/>. </p>
51 </li>
52 <li>
53 <p>For optical disks, the <b outputclass="bold">VISO Creator</b> tool is shown. See <xref
54 href="create-optical-disk-image.dita#create-optical-disk-image"/>. </p>
55 </li>
56 <li>
57 <p>For floppy disks, the <b outputclass="bold">Floppy Disk Creator</b> tool is shown. See
58 <xref href="create-floppy-disk-image.dita#create-floppy-disk-image"/>. </p>
59 </li>
60 </ul>
61 </li>
62 <li>
63 <p><b outputclass="bold">Copy</b> an image to create another one. </p>
64 <p>For virtual hard disks, you can specify one of the following target types: VDI, VHD, or VMDK. </p>
65 </li>
66 <li>
67 <p><b outputclass="bold">Move</b> an image to another location. </p>
68 <p>A file dialog prompts you for the new image file location. </p>
69 <p>When you use the Virtual Media Manager to move a disk image, <ph
70 conkeyref="vbox-conkeyref-phrases/product-name"/> updates all related configuration files automatically. </p>
71 <note>
72 <p>Always use the Virtual Media Manager or the <userinput>VBoxManage modifymedium</userinput>
73 command to move a disk image. </p>
74 <p>If you use a file management feature of the host OS to move a disk image to a new location,
75 run the <userinput>VBoxManage modifymedium --setlocation</userinput> command to configure the new path of
76 the disk image on the host file system. This command updates the <ph
77 conkeyref="vbox-conkeyref-phrases/product-name"/> configuration automatically. </p>
78 </note>
79 </li>
80 <li>
81 <p><b outputclass="bold">Remove</b> an image from the known media. You can optionally delete the
82 image file when removing the image. </p>
83 </li>
84 <li>
85 <p><b outputclass="bold">Release</b> an image to detach it from a VM. This action only applies if
86 the image is currently attached to a VM as a virtual hard disk. </p>
87 </li>
88 <li>
89 <p><b outputclass="bold">Clear</b> all inaccessible disk images from the list. The disk images are
90 released from the VMs they are attached to and removed from the known media. </p>
91 <note>
92 <p>This option is for optical disks and floppy disks only. </p>
93 </note>
94 </li>
95 <li>
96 <p><b outputclass="bold">Search</b> for an image by name or UUID. </p>
97 </li>
98 <li>
99 <p>View and edit the <b outputclass="bold">Properties</b> of a disk image. </p>
100 <p>Available properties include the following: </p>
101 <ul>
102 <li>
103 <p><b outputclass="bold">Type:</b> Specifies the snapshot behavior of the disk. See <xref
104 href="hdimagewrites.dita#hdimagewrites"/>. </p>
105 </li>
106 <li>
107 <p><b outputclass="bold">Location:</b> Specifies the location of the disk image file on the
108 host system. You can use a file dialog to browse for the disk image location. </p>
109 </li>
110 <li>
111 <p><b outputclass="bold">Description:</b> Specifies a short description of the disk image. </p>
112 </li>
113 <li>
114 <p><b outputclass="bold">Size:</b> Specifies the size of the disk image. You can use the
115 slider to increase or decrease the disk image size. </p>
116 </li>
117 <li>
118 <p><b outputclass="bold">Information:</b> Specifies detailed information about the disk
119 image. </p>
120 </li>
121 </ul>
122 </li>
123 <li>
124 <p><b outputclass="bold">Refresh</b> the property values of the selected disk image. </p>
125 </li>
126 </ul>
127 <p>To perform these actions, highlight the medium in the Virtual Media Manager and then do one of the
128 following: </p>
129 <ul>
130 <li>
131 <p>Click an icon in the Virtual Media Manager toolbar. </p>
132 </li>
133 <li>
134 <p>Right-click the medium and select an option. </p>
135 </li>
136 </ul>
137 <p>Use the <b outputclass="bold">Storage</b> page in a VM's <b outputclass="bold">Settings</b> window to
138 create a new disk image. By default, disk images are stored in the VM's folder. </p>
139 <p>You can copy hard disk image files to other host systems and then import them in to VMs from the host
140 system. However, some Windows guest OSes may require that you configure the new VM in a similar way to the old
141 one. </p>
142 <note>
143 <p>Do not simply make copies of virtual disk images. If you import such a second copy into a VM, <ph
144 conkeyref="vbox-conkeyref-phrases/product-name"/> issues an error because <ph
145 conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a universally unique identifier (UUID) to each disk
146 image to ensure that it is only used one time. See <xref href="cloningvdis.dita#cloningvdis"/>. Also, if you
147 want to copy a VM to another system, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> import and
148 export features. See <xref href="ovf.dita#ovf"/>. </p>
149 </note>
150 </body>
151
152
153
154 </topic>
Note: See TracBrowser for help on using the repository browser.

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