How to easily port VirtualBox machines?
I have used VMware for a long time.
VMware saves all the information for one machine in one directory.
This means it is easy to zip and copy.
Now I switched to VirtualBox.
VirtualBox seems to save the machine's information in more than one directory, e.g., a machine I called "Windows 7 Basic" is apparently saved here:
C:Usersedward.VirtualBoxHardDrivesWindows 7 Basic.vdi
C:Usersedward.VirtualBoxMachinesWindows 7 Basic…
(various directories and files)
What do I need to do to transport my "Windows 7 Basic" machine?
The fact that the data is saved under a "." directory and in various places suggests that there is some kind of export/import feature.
I found the "export appliance" feature so I assume this is it.
But I started it for an empty machine and it says "time remaining 1 hour 31 minutes".
Am I doing this right? Does it really take 1.5 hours to "export" a machine and perhaps 1.5 hours to import it again, so 3 hours to move a virtual machine?
virtualbox virtual-machine
add a comment |
I have used VMware for a long time.
VMware saves all the information for one machine in one directory.
This means it is easy to zip and copy.
Now I switched to VirtualBox.
VirtualBox seems to save the machine's information in more than one directory, e.g., a machine I called "Windows 7 Basic" is apparently saved here:
C:Usersedward.VirtualBoxHardDrivesWindows 7 Basic.vdi
C:Usersedward.VirtualBoxMachinesWindows 7 Basic…
(various directories and files)
What do I need to do to transport my "Windows 7 Basic" machine?
The fact that the data is saved under a "." directory and in various places suggests that there is some kind of export/import feature.
I found the "export appliance" feature so I assume this is it.
But I started it for an empty machine and it says "time remaining 1 hour 31 minutes".
Am I doing this right? Does it really take 1.5 hours to "export" a machine and perhaps 1.5 hours to import it again, so 3 hours to move a virtual machine?
virtualbox virtual-machine
add a comment |
I have used VMware for a long time.
VMware saves all the information for one machine in one directory.
This means it is easy to zip and copy.
Now I switched to VirtualBox.
VirtualBox seems to save the machine's information in more than one directory, e.g., a machine I called "Windows 7 Basic" is apparently saved here:
C:Usersedward.VirtualBoxHardDrivesWindows 7 Basic.vdi
C:Usersedward.VirtualBoxMachinesWindows 7 Basic…
(various directories and files)
What do I need to do to transport my "Windows 7 Basic" machine?
The fact that the data is saved under a "." directory and in various places suggests that there is some kind of export/import feature.
I found the "export appliance" feature so I assume this is it.
But I started it for an empty machine and it says "time remaining 1 hour 31 minutes".
Am I doing this right? Does it really take 1.5 hours to "export" a machine and perhaps 1.5 hours to import it again, so 3 hours to move a virtual machine?
virtualbox virtual-machine
I have used VMware for a long time.
VMware saves all the information for one machine in one directory.
This means it is easy to zip and copy.
Now I switched to VirtualBox.
VirtualBox seems to save the machine's information in more than one directory, e.g., a machine I called "Windows 7 Basic" is apparently saved here:
C:Usersedward.VirtualBoxHardDrivesWindows 7 Basic.vdi
C:Usersedward.VirtualBoxMachinesWindows 7 Basic…
(various directories and files)
What do I need to do to transport my "Windows 7 Basic" machine?
The fact that the data is saved under a "." directory and in various places suggests that there is some kind of export/import feature.
I found the "export appliance" feature so I assume this is it.
But I started it for an empty machine and it says "time remaining 1 hour 31 minutes".
Am I doing this right? Does it really take 1.5 hours to "export" a machine and perhaps 1.5 hours to import it again, so 3 hours to move a virtual machine?
virtualbox virtual-machine
virtualbox virtual-machine
edited Apr 28 '15 at 19:55
G-Man
5,597112357
5,597112357
asked Aug 2 '09 at 20:55
Edward TanguayEdward Tanguay
5,9633091123
5,9633091123
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You can just copy the files inside the directories you mentioned, that is, the virtual harddisk (.vdi) and the xml-based description of the virtual machine. I did this twice, even cross plattform (a XP geust from an OS X host to a Windows XP host, and an Ubuntu guest from a Windows Vista Host to an OS X host) and it worked fine.
There may be two issues:
- Both VDIs will have the same UUIDs, which is certainly not how it is intended
- You may have to make minor changes to the XML-based machine defintion. I remember that it once contained an absolute path to the vdi, which was not valid after the host-to-host transfer. However, I think newer versions of virtual box do not use absolute paths.
2
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the.vbox
file's location.
– Kaz
Mar 13 '15 at 18:35
add a comment |
The export feature saves the image in OVF format. From the manual:
OVF is a cross-platform standard supported by many virtualization products which allows for creating ready-made virtual machines that can then be imported into a virtualizer such as VirtualBox
I believe you want the VBoxManage clonehd
command.
This command duplicates a registered virtual hard disk image to a new image file with
a new unique identifier (UUID). The new image can be transferred to another host
system or imported into VirtualBox again using the Virtual Disk Manager...
VBoxManage clonehd <uuid>|<filename> <outputfile>
[--format VDI|VMDK|VHD|RAW|<other>]
[--variant Standard,Fixed,Split2G,Stream,ESX]
[--type normal|writethrough|immutable]
[--remember]
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f17340%2fhow-to-easily-port-virtualbox-machines%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can just copy the files inside the directories you mentioned, that is, the virtual harddisk (.vdi) and the xml-based description of the virtual machine. I did this twice, even cross plattform (a XP geust from an OS X host to a Windows XP host, and an Ubuntu guest from a Windows Vista Host to an OS X host) and it worked fine.
There may be two issues:
- Both VDIs will have the same UUIDs, which is certainly not how it is intended
- You may have to make minor changes to the XML-based machine defintion. I remember that it once contained an absolute path to the vdi, which was not valid after the host-to-host transfer. However, I think newer versions of virtual box do not use absolute paths.
2
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the.vbox
file's location.
– Kaz
Mar 13 '15 at 18:35
add a comment |
You can just copy the files inside the directories you mentioned, that is, the virtual harddisk (.vdi) and the xml-based description of the virtual machine. I did this twice, even cross plattform (a XP geust from an OS X host to a Windows XP host, and an Ubuntu guest from a Windows Vista Host to an OS X host) and it worked fine.
There may be two issues:
- Both VDIs will have the same UUIDs, which is certainly not how it is intended
- You may have to make minor changes to the XML-based machine defintion. I remember that it once contained an absolute path to the vdi, which was not valid after the host-to-host transfer. However, I think newer versions of virtual box do not use absolute paths.
2
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the.vbox
file's location.
– Kaz
Mar 13 '15 at 18:35
add a comment |
You can just copy the files inside the directories you mentioned, that is, the virtual harddisk (.vdi) and the xml-based description of the virtual machine. I did this twice, even cross plattform (a XP geust from an OS X host to a Windows XP host, and an Ubuntu guest from a Windows Vista Host to an OS X host) and it worked fine.
There may be two issues:
- Both VDIs will have the same UUIDs, which is certainly not how it is intended
- You may have to make minor changes to the XML-based machine defintion. I remember that it once contained an absolute path to the vdi, which was not valid after the host-to-host transfer. However, I think newer versions of virtual box do not use absolute paths.
You can just copy the files inside the directories you mentioned, that is, the virtual harddisk (.vdi) and the xml-based description of the virtual machine. I did this twice, even cross plattform (a XP geust from an OS X host to a Windows XP host, and an Ubuntu guest from a Windows Vista Host to an OS X host) and it worked fine.
There may be two issues:
- Both VDIs will have the same UUIDs, which is certainly not how it is intended
- You may have to make minor changes to the XML-based machine defintion. I remember that it once contained an absolute path to the vdi, which was not valid after the host-to-host transfer. However, I think newer versions of virtual box do not use absolute paths.
edited Aug 3 '09 at 11:17
answered Aug 3 '09 at 11:01
Lena SchimmelLena Schimmel
4553711
4553711
2
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the.vbox
file's location.
– Kaz
Mar 13 '15 at 18:35
add a comment |
2
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the.vbox
file's location.
– Kaz
Mar 13 '15 at 18:35
2
2
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
I do this almost everyday between Linux, Windows and MacOSX with very little problems. In fact once you have moved it the first time you can actually just copy the VDI file over
– BinaryMisfit
Aug 3 '09 at 11:07
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the .vbox
file's location.– Kaz
Mar 13 '15 at 18:35
.vbox
files use relative paths which work if everything is in the same directory; absolute paths will still be used in the "scattered" cases, like when there are disks which are not in a subdirectory of the .vbox
file's location.– Kaz
Mar 13 '15 at 18:35
add a comment |
The export feature saves the image in OVF format. From the manual:
OVF is a cross-platform standard supported by many virtualization products which allows for creating ready-made virtual machines that can then be imported into a virtualizer such as VirtualBox
I believe you want the VBoxManage clonehd
command.
This command duplicates a registered virtual hard disk image to a new image file with
a new unique identifier (UUID). The new image can be transferred to another host
system or imported into VirtualBox again using the Virtual Disk Manager...
VBoxManage clonehd <uuid>|<filename> <outputfile>
[--format VDI|VMDK|VHD|RAW|<other>]
[--variant Standard,Fixed,Split2G,Stream,ESX]
[--type normal|writethrough|immutable]
[--remember]
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
add a comment |
The export feature saves the image in OVF format. From the manual:
OVF is a cross-platform standard supported by many virtualization products which allows for creating ready-made virtual machines that can then be imported into a virtualizer such as VirtualBox
I believe you want the VBoxManage clonehd
command.
This command duplicates a registered virtual hard disk image to a new image file with
a new unique identifier (UUID). The new image can be transferred to another host
system or imported into VirtualBox again using the Virtual Disk Manager...
VBoxManage clonehd <uuid>|<filename> <outputfile>
[--format VDI|VMDK|VHD|RAW|<other>]
[--variant Standard,Fixed,Split2G,Stream,ESX]
[--type normal|writethrough|immutable]
[--remember]
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
add a comment |
The export feature saves the image in OVF format. From the manual:
OVF is a cross-platform standard supported by many virtualization products which allows for creating ready-made virtual machines that can then be imported into a virtualizer such as VirtualBox
I believe you want the VBoxManage clonehd
command.
This command duplicates a registered virtual hard disk image to a new image file with
a new unique identifier (UUID). The new image can be transferred to another host
system or imported into VirtualBox again using the Virtual Disk Manager...
VBoxManage clonehd <uuid>|<filename> <outputfile>
[--format VDI|VMDK|VHD|RAW|<other>]
[--variant Standard,Fixed,Split2G,Stream,ESX]
[--type normal|writethrough|immutable]
[--remember]
The export feature saves the image in OVF format. From the manual:
OVF is a cross-platform standard supported by many virtualization products which allows for creating ready-made virtual machines that can then be imported into a virtualizer such as VirtualBox
I believe you want the VBoxManage clonehd
command.
This command duplicates a registered virtual hard disk image to a new image file with
a new unique identifier (UUID). The new image can be transferred to another host
system or imported into VirtualBox again using the Virtual Disk Manager...
VBoxManage clonehd <uuid>|<filename> <outputfile>
[--format VDI|VMDK|VHD|RAW|<other>]
[--variant Standard,Fixed,Split2G,Stream,ESX]
[--type normal|writethrough|immutable]
[--remember]
answered Aug 2 '09 at 23:23
McDowellMcDowell
26138
26138
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
add a comment |
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
I used VBoxManage CloneVDI (instead of cloneHD) and it worked nicely.
– Ash
May 31 '10 at 5:37
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f17340%2fhow-to-easily-port-virtualbox-machines%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown