| 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="vboxconfigdata-XML-files">
|
|---|
| 4 | <title>Oracle VM VirtualBox XML Files</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | Oracle VM VirtualBox uses XML for both the machine settings files and
|
|---|
| 9 | the global configuration file,
|
|---|
| 10 | <filepath>VirtualBox.xml</filepath>.
|
|---|
| 11 | </p>
|
|---|
| 12 | <p>
|
|---|
| 13 | All Oracle VM VirtualBox XML files are versioned. When a new settings
|
|---|
| 14 | file is created, for example because a new virtual machine is
|
|---|
| 15 | created, Oracle VM VirtualBox automatically uses the settings format
|
|---|
| 16 | of the current Oracle VM VirtualBox version. These files may not be
|
|---|
| 17 | readable if you downgrade to an earlier version of
|
|---|
| 18 | Oracle VM VirtualBox. However, when Oracle VM VirtualBox encounters a
|
|---|
| 19 | settings file from an earlier version, such as after upgrading
|
|---|
| 20 | Oracle VM VirtualBox, it attempts to preserve the settings format as
|
|---|
| 21 | much as possible. It will only silently upgrade the settings
|
|---|
| 22 | format if the current settings cannot be expressed in the old
|
|---|
| 23 | format, for example because you enabled a feature that was not
|
|---|
| 24 | present in an earlier version of Oracle VM VirtualBox.
|
|---|
| 25 | </p>
|
|---|
| 26 | <p>
|
|---|
| 27 | In such cases, Oracle VM VirtualBox backs up the old settings file in
|
|---|
| 28 | the virtual machine's configuration directory. If you need to go
|
|---|
| 29 | back to the earlier version of Oracle VM VirtualBox, then you will
|
|---|
| 30 | need to manually copy these backup files back.
|
|---|
| 31 | </p>
|
|---|
| 32 | <p>
|
|---|
| 33 | We intentionally do not document the specifications of the
|
|---|
| 34 | Oracle VM VirtualBox XML files, as we must reserve the right to modify
|
|---|
| 35 | them in the future. We therefore strongly suggest that you do
|
|---|
| 36 | not edit these files manually. Oracle VM VirtualBox provides complete
|
|---|
| 37 | access to its configuration data through its the
|
|---|
| 38 | <userinput>VBoxManage</userinput> command line tool, see
|
|---|
| 39 | <xref href="vboxmanage.dita">VBoxManage</xref> and its API, see
|
|---|
| 40 | <xref href="VirtualBoxAPI.dita"/>.
|
|---|
| 41 | </p>
|
|---|
| 42 | </body>
|
|---|
| 43 |
|
|---|
| 44 | </topic>
|
|---|
