virtualbox.org

Hello!

I have a big problem.... I tried to use the vmware-File within my (new) virtualbox. Created a new "machine" and used the harddrive-image of my vmware-machine. Then I started the virtualbox-machine and nothing happened (no system found).
But after this procedure the hd-image does not even run under vmware! There I now get the same error (no system on disk)!

What can I do to "repair" this file so that I can even use it within vmware!?

Or can I repair it in an other way so that it will really run under virtualbox (what was my primary intention)!

I hope anyone can help me?!

Best regards!

Best guess is that the VMware VM used snapshots, but you attached the base VMDK only to your VirtualBox VM. VMWare may have checks to detect a modified base image, which kicks in even if the mod was trivial (*). Easiest repair is to restore the modified file from a backup. I don't know of any other way.

(*) I don't see why what you describe should have resulted in a modified VMDK. If you managed to get it to boot, or otherwise attached to a running VM, that would be a different matter. Are you leaving out a part of your story?

mpack wrote: Are you leaving out a part of your story?

Hello mpack,

no I am not leaving out anything! I did it the same way with two different vmware-images - and both are not running anymore with vmware!

Backup... Well.... Do you really think that I would ask for help when there would be a backup?!

As I said: I created a new virtualbox and selected the vmware-vmdk file as image file (harddisk) - then I just tried to start this created virtualbox-mashine : "No system found on disk" - and after that I tried to reuse vmware: "No system found on disk"

Without leaving out anything!

So you mean: Without a backup there is no way to restore it?

I just solve the problem 2 hours ago, vmware vmdk to Vbox

set the vmdk-boot up disk under the IDE-controler tab not SATA-controler

No need to create-backup or restore.

* I follow too many advised backup-restore, it break the boot up before the complete the process because windows want a ide-driver. My suspect that the windows 2008 r2 X64, I created by vmware, I used IDE-drive.

* however, on the windows 2008 x86 when I backup-restore it run fine with SATA-controler tab, but not the windows 2008 r2 x64 version.

not such thing: "VMWare vmdk damaged by Virtualbox". I retest in the vmware it work fine (without installed the extension pack or switch to SATA-controller).

a suggestion in this forum, I should convert that in to SATA-controller.

cheer!

I run Virtual machines: concurrently vmware and vbox
my: Host windows 2k8 r2 x64
guests: windows 2k8 x86, 2k8 x64. linux versions:centos, ubuntu, ...
hw: amd phenom II x6 1075T 3.0GHz

benhuynh70x7 wrote:set the vmdk-boot up disk under the IDE-controler tab not SATA-controler

Hi and thanks for your feedback!
Do you mean to switch this within the vbox-bios? Or within the harddrive-tab?

I tried a lot yesterday (nothing within the bios) - and will go on testing today... (I want to try restoring the disk using the installation-CDs)

in the vbox,
- Settings (ctr-s)
- Storage
- IDE-Controller
- add a new attachment (+), add a hard disk
* point to the vmdk boot up disk, and automatically set it as IDE Primary Master and the cd/dvd driver should be Secondary Master.

* other none-boot up vmdk can be in SATA-Controller Storage Tree