Move vdi from Win->MAC; starts up but crashes under way

This is for discussing general topics about how to use VirtualBox.
Post Reply
Rokker33
Posts: 2
Joined: 4. Apr 2016, 18:49
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: Win8, Chrome, Ubuntu

Move vdi from Win->MAC; starts up but crashes under way

Post by Rokker33 »

Hi,

I had a Win7 machine where I hosted a Win8 virtual box. Now I wish to take the win8 dvi and use it on my macbook. The win7 hard disk crashed. Is that possible? I copied the vdi to the macbook and created a new virtual machine in VirtualBox. It starts loading up Win8 (startup logo is shown) but then it crashed. Don't know how to read the log file.

Anyone a hint how can I get this Win8 vdi up and running?

Thanks, Markus
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Move vdi from Win->MAC; starts up but crashes under way

Post by socratis »

First of all, the VDI is the Virtual Disk Image, i.e. your virtual hard drive. That does not include the rest of the "recipe" of the VM, like amounts of RAM, networking, etc. You should have migrated the whole VM, according to the article Moving a VM. But, if you made a VM with the exact same settings, it may work.

There are two things that will help us to potentially identify the problem. First of all, the settings of each of the VMs. From both your computers issue the following command in the Terminal/Command Prompt (for Windows hosts you have to be in the VirtualBox directory, typically "C:\Program Files\Oracle\VirtualBox\"):
   VBoxManage showvminfo "Your_VM_name"
Attach the output from both systems in your response.

Next, the VBox.log.
  1. Start the VM. Not from a saved or suspended state. Clean start.
  2. Take the steps required to generate/observe the error.
  3. Record the error message. EXACTLY. Post a screenshot if you have to.
  4. Shut down the VM (if it hasn't aborted by itself). Not suspend, not pause. Shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
  5. Right-click on the VM in the VirtualBox Manager.
  6. Select "Show Log..."
  7. Save it, ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Rokker33
Posts: 2
Joined: 4. Apr 2016, 18:49
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: Win8, Chrome, Ubuntu

Re: Move vdi from Win->MAC; starts up but crashes under way

Post by Rokker33 »

Thanks a lot for the answer. Unfortunately my provider put the notification mail into spam and I just saw it today.

Please find attached the requested information. Unfortunately my windows machine does not boot up any more after hard disk crash. So I could not sent a showvminfo text.

I could sent the windows machine box file and the last logs from the time vmbox Win8 was started last time on my windows machine. Please let me know if that helps.

Thanks so much for helping.

Best regards,
Markus
Attachments
error message vm startup screenshot
error message vm startup screenshot
vm-win8-error-message-boot-small.jpg (123.62 KiB) Viewed 906 times
show_vm_info_mac.txt
show vm info on mac
(3.05 KiB) Downloaded 7 times
VBox.log.zip
log file mac compressed
(42.95 KiB) Downloaded 8 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Move vdi from Win->MAC; starts up but crashes under way

Post by mpack »

VBox.log wrote: 00:00:02.075108 Host RAM: 8192MB total, 1431MB available
...
00:00:02.245126 RamSize <integer> = 0x00000000c3400000 (3 275 751 424, 3 GB)
00:00:02.246011 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
Never going to work. Host RAM way overcommitted.
VBox.log wrote: 00:00:02.108917 Guest OS type: 'Windows8_64'
Are you sure the guest was Win8, and not Win8.1? It make a big difference: running Windows 8.1 in a Win8 VM will not work.
Post Reply