|
|
|
|
|
|
|
|
|
|
|
|
kellypkelly
Confident Newbie
 
Karma: 18
Posts: 93

|
 |
« Reply #32 on: May 15, 2017, 04:35:17 PM » |
|
Please backup anything important and only work with copies, please be careful even a minor error in a virtual drive can make it impossible to access and useless, also because of the sheer data size any error may be impossible to correct or even find.
Your virtual drive in vBox may be in their own VDI format or VMDK format, if it is in the VDI format you need to use Media Manager and copy it to VMDK format.
Check whether the vBox controller is SATA or SCSI your new VMware machine must use the same format.
Create a new VMware machine and choose to install an OS later, do not open or play the new machine. Close VMware and open the folder location of the new machine. Copy or move the VMDK file of your vBox machine to this folder.
Now use one of the two methods below.
1. IF the controller for the drive in the new machine is the same format as the original vBox, open the vmx file and change the name of the drive in there to that of the VMDK you copied to the new machine's folder. EG the line will be similar to this. sata0:0.filename= "your virtual drive file". Then delete the virtual drive VMDK file which was created when you made the new VNware machine from the folder.
2. If the controller for the drive in the new machine is somehow different from the format of your original vBox drive, open VMware, select your new machine on the left, click edit virtual machine settings, click add, select hard disk, and click next, important choose the disk type you require, and click next, select use an existing virtual disk, and click next, browse to your new VMDK file, and click finish. If it asks to convert the disk format choose not to. Select the original unwanted drive on the left and click remove. Close VMware.
Open VMware and the machine should play, there may be some minor issues to correct, usually for me it has been simple perhaps manually install some drivers eg sound card etc. These issues exist as this is not a clone of your original machine or computer, it is similar to transferring a hard drive from one computer to another, and can have similar issues as that.
You cannot run virtual machines with the same UUID, Using this method will assign your VM with a new UUID, should you vary from above method and get a message complaining about conflicting UUIDs you can manually edit the UUID in the vmx file.
This is far from the usual recommended method, I can't say it will work with all systems or versions, but it has worked for me many times when exporting to OVA/OVF has failed due to incorrect or unmatched disk capacity etc, if you have the paid version of VMware or a copy of ovftool it is much easier to export and use that tool.
|
|
|
Logged
|
|
|
|
|
|
|
|
|
|
|