VM will not start after SSD upgrade

[harveydog]

Hi

I am having a problem with a Win 7 VM in VirtualBox on Mac OSX host.

I upgraded my HDD to an SSD, and now the VM will not start.
See attachment.
Can anyone help.
I don't have the install disks anymore as it is quite old and I have moved a few times.

Thanks in advance.

[socratis]

Moving to "Windows Guests" from "OSX Hosts" since the problem is clearly with your guest.

I upgraded my HDD to an SSD, and now the VM will not start.

Upgrading your host's hard drive should not have any implications on the VM, unless 1) you were using raw disk access, or 2) your restore method from the old to the new hard drive had logical faults. How did you restore from the old to the new? Did you use another 3rd hard drive?

Did you search for "windows 7 c000000f"?

[harveydog]

I copied the old disk to the new disk using dd.
If I attach the old hard drive via usb and compare the 2 files using cmp, they are the same.

I can also start the vm fine from the old drive connected via usb.


I did search for windows 7 c000000f, however suggested solutions require installation media, which i no longer have.

[mpack]

I copied the old disk to the new disk using dd.

Yup, that's pretty much guaranteed to kill a modern Windows VM.

FAQ: How to move a VM.

[harveydog]

Solved problem by running up the old vm from the original drive attached via usb, and then exporting to the new SSD from VirtualBox gui..

Still a mystery why dd did not work, even though cmp showed the files to be the same.

[mpack]

You messed up the VM recipe, not the disk. That's why I pointed you to the "Moving a VM" FAQ.

Export/Import is still doing it wrong.

[harveydog]

what is the right way pleasse

[mpack]

I gave you the link to the FAQ in my previous post +1.

[harveydog]

Yes - that is the way i did it to begin with.

I took a tarball of the win7 vb folder and copied it over with dd. (I had to use tar and dd because os/x had problems copying my vdi file - too large).
Then unpacked it and added using the gui menu
I compared the copied files using cmp and they are all identical.
That seems to be pretty much what it says in the faq apart from the tar and dd:

"The basic procedure for moving VMs created by VirtualBox v4.0.0 or later is to copy the VM folder (with contents) to your preferred location, then use the GUI's Machine|Add menu item to register the .vbox file (found in the VM folder) from its new location."

However, after adding the machine from the new location I get the error pictured.

But it works when i add the machine from the original disk connected by usb.

[mpack]

I don't use either tar or dd. I do know what they are (or thought I did), but I'm not sure of their relevance for copying files and folders.

The error message in the first post seems to be quite clear: some boot device is inaccessible. With a normal VM and following the procedure in the FAQ then any devices accessible before the event must be accessible after. Either the FAQ was not followed, or something must be missing from the description of this problem.

[harveydog]

>>I don't use either tar or dd. I do know what they are (or thought I did), but I'm not sure of their relevance for copying files and folders.

This is why i put it in the Mac OSX host thread, but it got moved.
The reason i had to use tar and dd was because mac os x copy using the gui could not handle the file size.

It had no effect on the resulting files.
Indeed when I do a binary comparison of all the files in the VM folder they are all identical.

However for some reason the VM will not start from the copied files on the new disk, but only from an exported ovf from the old disk.

I have followed the faq to the letter - copying the old VM folder to the new location, just that i had to use dd and tar to achieve the copy due to OS limitations.

[erdeslawe]

MacOS doesn't have any such size limitations on its ability to copy files from one drive to another, but the receiving drive may well have limitations if it is not correctly formatted to receive such large files, e.g. if the format of the Drive is FAT32 there is a 4Gb file size limit.