Virtual Machine does not open VMDK-file from VMWare

[nachtkrabb]

On a MacBook Pro with Monterey 12.4, a virtual machine (*.vmdk) was created by an installation of VMWare Fusion Player. The guest system is Windows 7. The MacBook Pro has an Intel i7-processor.

The vmdk was copied to a Linux-notebook with Tuxedo 1.1.5 (an Ubuntu-derivate) with VirtualBox 6.1.36. This computer has an AMD Ryzen 7-processor. A session was created for the vmdk along ​https://medium.com/riow/how-to-open-a-vmdk-file-in-virtualbox-e1f711deacc4. VirtualBox started the vmdk, tried to start the guest system but failed: It tried to repair Windows unsuccessfully. Using "VBoxManage clonehd --format VDI mySource.vmdk myTarget.vdi", the vmdk was converted into a vdi-file. Same problem: Start-up of Windows failed, repair failed.

VirtualBox was installed on the MacBook and a session was created for the vmdk as above. Same problem: Start-up of Windows failed, repair failed.

After reading that on Linux the VirtualBox-Extensions were missing, installed the current version 6.1.36. Now, VirtualBox does not even start the vmdk or vdi, but writes an error message (my translation):

Für die virtuelle Maschine XXX konnte keine neue Sitzung eröffnet werden. (No new session could be created for the virtual machine XXX.) The VM session was aborted.

Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: SessionMachine Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

According to the manual, a vmdk should be opened an run easily?

[nachtkrabb]

On trying to start the guest system, this bluescreen is shown for a second.

[nachtkrabb]

After the bluescreen, the system tries to repair Windows which fails.

[fth0]

The 0x0000007B (INACCESSIBLE_BOOT_DEVICE) in the BSOD (Blue Screen Of Death) usually means that you changed the Disk Controller, which is remembered by the Windows OS in the VM. In the VirtualBox VM, you should configure the same type of disk controller as in the original VM.

[nachtkrabb]

Thank you for the idea. But: ...Disk Controller? I am so sorry, I do not know too much about that. I have found that there are quite some tickets with this error code, so I opened the ticket. How can I find out which is the old disk controller, and where can I change it in VirtualBox? I have made a screenshot where I think I can enter the Disk Controller. Again: Thank you.

[nachtkrabb]

Is this where to change the Disk Controller?

[nachtkrabb]

...Your description is that good that I catch the idea. Great. Although I still have to learn what to do.

[nachtkrabb]

Is that "chipsatz" also a possible source of error?

[fth0]

To find out which disk controller was used in the VMware Fusion VM, the obvious way would be to look into the VM configuration inside VMware Fusion. Another alternative would be to look into the .vmx file that contains the VM configuration.

Alternatively, you can simply use trial and error: Google tells that VMware VMs often use an SCSI controller, but nowadays also use an NVMe controller. In VirtualBox, use the configuration dialog you've successfully found, add an SCSI controller, remove the VDI file from the SATA controller and add it to the SCSI controller.

Regarding the chipset, I don't know. Generally speaking, moving a virtual disk image from one VM to another is equivalent to moving a physical hard disk from one PC to another. Depending on the guest OS and its autodetecting capabilities, it may adapt to the new hardware or not. In case of VMs, you're in the lucky position to be able to modify the (virtual) hardware quite a bit. ;)

[nachtkrabb]

Thank you ever so much. This is very helpful. I have read the .vmx (which I hadn't known before) and the preferences of my old machine. According to these, I have made changes:

• System > Main board > Boot order new: board / optical / floppy.
• System > Main memory 9500MB (again)
• System > chipset PIIX3 (unchanged)
• System > processors: 4 (old default: 1)
• Mass storage > Controller / old: given default was SATA / AHCI / 2.
• Mass storage > Controller / new selection: "Buslogic (SCSI)" (Also tried "LsiLogic default SCSI").
• Shared folder: home completely rw added (only main level).

With both controllers, Buslogic as well as LsiLogic, there was no bluescreen! Hurray! But Windows didn't start up either. It again tried to repair and failed. But it was another repair -- you could already see the background of the login screen. So the process could go much further. This was the same with the vmdk as well as with the vdi; picture to follow.

With procesor ICH9, there was a bluescreen, so I will stay with the default PIIX3.

I will now copy the vmdk again from backup to my computer as there might have something happened to my local copy through all these repairs with the wrong preferences. Then I will try again to start the vmdk with the preferences given above.

[nachtkrabb]

New "no automtic repair" window give hope.

[nachtkrabb]

Oh gosh. After getting a fresh version of the vmdk I realised: At the very first start of the thingummy there is a bluescreen with 0x0000007B as error code, I will attach a screenshot. At successing starts, this bluescreen is not displayed. Please, would you have a look again? Thank you.

[nachtkrabb]

Bluescreen after getting a fresh copy of the vmdk.

[fth0]

I have nothing really new to add. This BSOD has been well known (on physical PCs and virtual machines) for many years. The current Microsoft help can be found on ​Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device.

[nachtkrabb]

Thank you. N.