1 | <?xml version='1.0' encoding='UTF-8'?>
|
---|
2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
---|
3 | <topic xml:lang="en-us" id="rawdisk">
|
---|
4 | <title>Using a Raw Host Hard Disk From a Guest</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p>
|
---|
8 | As an alternative to using virtual disk images as described in
|
---|
9 | <xref href="storage.dita">Virtual Storage</xref>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can also present
|
---|
10 | either entire physical hard disks or selected partitions as
|
---|
11 | virtual disks to virtual machines.
|
---|
12 | </p>
|
---|
13 | <p>
|
---|
14 | With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, this type of access is called <i>raw
|
---|
15 | hard disk access</i>. It enables a guest operating system
|
---|
16 | to access its virtual hard disk without going through the host
|
---|
17 | OS file system. The actual performance difference for image
|
---|
18 | files compared to raw disk varies greatly depending on the
|
---|
19 | overhead of the host file system, whether dynamically growing
|
---|
20 | images are used, and on host OS caching strategies. The caching
|
---|
21 | indirectly also affects other aspects such as failure behavior.
|
---|
22 | For example, whether the virtual disk contains all data written
|
---|
23 | before a host OS crash. Consult your host OS documentation for
|
---|
24 | details on this.
|
---|
25 | </p>
|
---|
26 | <note type="attention">
|
---|
27 | <p>
|
---|
28 | Raw hard disk access is for expert users only. Incorrect use
|
---|
29 | or use of an outdated configuration can lead to
|
---|
30 | <b outputclass="bold">total loss of data</b> on the
|
---|
31 | physical disk. Most importantly, <i>do not</i>
|
---|
32 | attempt to boot the partition with the currently running host
|
---|
33 | operating system in a guest. This will lead to severe data
|
---|
34 | corruption.
|
---|
35 | </p>
|
---|
36 | </note>
|
---|
37 | <p>
|
---|
38 | Raw hard disk access, both for entire disks and individual
|
---|
39 | partitions, is implemented as part of the VMDK image format
|
---|
40 | support. As a result, you will need to create a special VMDK
|
---|
41 | image file which defines where the data will be stored. After
|
---|
42 | creating such a special VMDK image, you can use it like a
|
---|
43 | regular virtual disk image. For example, you can use the Virtual
|
---|
44 | Media Manager, see <xref href="virtual-media-manager.dita">The Virtual Media Manager</xref>, or
|
---|
45 | <userinput>VBoxManage</userinput> to assign the image to a virtual
|
---|
46 | machine.
|
---|
47 | </p>
|
---|
48 | </body>
|
---|
49 | </topic>
|
---|