Hi,
I used to prepare VM on a host (let's call Host1) and then copy the VDI to another host (called Host2). Usually it works perfectly, even if the two hosts have totally different hardware or even OS (like Linux / Windows). Today Host2 refuses to boot the VDI. I have tried to change various settings (Nested Paging, NX, IO APIC, IDE/Sata) but there is no improvement. When the VM is booted, it just go to a cycle of boot/power off/reboot.
Specs:
VirtualBox 3.1.8 x64
Host1: Win7 x64, Intel P8700, ATI Radeon HD 3650
Host2: Win7 x64, Intel i5 M520, nVidia Quadro FX 880
Guest: Windows Server 2008 R2
Attached is the Virtualbox log. Hope someone can figure out a clue to help me to move forward. I am wondering if hooking the VM back to Host1 and removing the Guest addition would improve the situation.
Thanks in advance for any help.
VBX 3.1.8: VM created on Host1, cannot boot on Host2
-
AntiMatter
- Volunteer
- Posts: 176
- Joined: 2. Nov 2008, 06:48
- Primary OS: Ubuntu 12.04
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: All Windows (x32 & x64), Linux
- Location: Canada
VBX 3.1.8: VM created on Host1, cannot boot on Host2
- Attachments
-
Host2_Virtualbox.log- (66.62 KiB) Downloaded 4 times
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: VBX 3.1.8: VM created on Host1, cannot boot on Host2
What happens when you try to boot in safe mode?
What about 3D/2D? difference in drivers might cause this. Disable in the settings and see how it goes.
What about 3D/2D? difference in drivers might cause this. Disable in the settings and see how it goes.
-
AntiMatter
- Volunteer
- Posts: 176
- Joined: 2. Nov 2008, 06:48
- Primary OS: Ubuntu 12.04
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: All Windows (x32 & x64), Linux
- Location: Canada
Re: VBX 3.1.8: VM created on Host1, cannot boot on Host2
2D/3D acceleration were unchecked in Virtualbox settings. On the host, there is no 3D or special video feature of the video card which is turned on. If there is anything to check there, can you please suggest me how to check and disable it?Perryg wrote:What happens when you try to boot in safe mode?
What about 3D/2D? difference in drivers might cause this. Disable in the settings and see how it goes.
Booting in safe mode: is it the white and black screen Windows 2008 R2 displays when the OS was not shutdown properly? There are two choices:
1. Start Windows in Recovery mode
2. Start Windows normally
Recovery mode did start. Mouse integration not working. I could select Memory Test, Open Dos Prompt or Restart. Memory Test was complete successfully. But a Restart always failed. After some failures to restart (which means the black/white screen of Windows boot which ask which boot to select) then I don't even have time to select anything. This black screen just come up and power recycled almost right away.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: VBX 3.1.8: VM created on Host1, cannot boot on Host2
What happens if you switch the HDD to IDE instead of SATA?
I have had issues with different SATA drivers between processors and motherboards.
Or you could switch the original to SCSI and see if that will work on the 2nd host.
I have had issues with different SATA drivers between processors and motherboards.
Or you could switch the original to SCSI and see if that will work on the 2nd host.
-
AntiMatter
- Volunteer
- Posts: 176
- Joined: 2. Nov 2008, 06:48
- Primary OS: Ubuntu 12.04
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: All Windows (x32 & x64), Linux
- Location: Canada
Re: VBX 3.1.8: VM created on Host1, cannot boot on Host2
Hi,
Issue fixed. On Host2, uninstall Virtualbox 3.18 + Install 3.2.10. Looks like new VB version copes better with the hardware of the new machine. When using 3.1.8, I have tried to play around with all possibles VB settings, always failed to start. Don't know if VB 3.2.10 is really better, but that the only choice for this new laptop.
Issue fixed. On Host2, uninstall Virtualbox 3.18 + Install 3.2.10. Looks like new VB version copes better with the hardware of the new machine. When using 3.1.8, I have tried to play around with all possibles VB settings, always failed to start. Don't know if VB 3.2.10 is really better, but that the only choice for this new laptop.