I just upgraded the VirtualBox from 3.0.4 to 3.0.6 running on Win 2008 Ent SP2 x86.
After upgrading when i am trying to strat the Guest OS (Win 2008 R2 x64 Bit) it stays at black screen just after showing the windows loading bar. When i try to hit reset it gives me a message box with title "Guru Meditation" saying that there is an error.
I am attaching the Vbox.log and Vbox.png file to this post for further troubleshooting.
Update: I uninstalled 3.0.6 and downgraded to 3.0.4 and i could start my guest os without any problem.
Upgrade 3.0.4 -> 3.0.6 Crashes Guest OS
-
sameerdhoot
- Posts: 2
- Joined: 12. Sep 2009, 18:27
- Primary OS: MS Windows 2008
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: MS Win
- Location: Farmington Hills, MI
- Contact:
Upgrade 3.0.4 -> 3.0.6 Crashes Guest OS
- Attachments
-
- VBox.png (993 Bytes) Viewed 1559 times
-
VBox.log- (111.6 KiB) Downloaded 8 times
Sameer Dhoot
http://sharemypoint.in
http://sharemypoint.in
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Upgrade 3.0.4 -> 3.0.6 Crashes Guest OS
From the log
Host RAM: 4093MB RAM, available: 2803MB
assigned = 1,572,864,000
They have limited the guest to 1/2 of the available memory and no more than 1.5 gig
Try setting the RAM to the host at 1024 Meg and see if it works.
Host RAM: 4093MB RAM, available: 2803MB
assigned = 1,572,864,000
They have limited the guest to 1/2 of the available memory and no more than 1.5 gig
Try setting the RAM to the host at 1024 Meg and see if it works.
-
sameerdhoot
- Posts: 2
- Joined: 12. Sep 2009, 18:27
- Primary OS: MS Windows 2008
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: MS Win
- Location: Farmington Hills, MI
- Contact:
Re: Upgrade 3.0.4 -> 3.0.6 Crashes Guest OS
Perryg,
Is this limitaion of 1.5gb new with version 3.0.6? This is absurd.. why would they want to limit the VM to 1.5 gig.
When i could not start the VM i deleted the VM and created a new one pointing to same old hard drive and the UI did not allow me to set more than 1500mb of ram. So i think the ram was already set this limit. But inspite of this the VM crashed though i did not try it with 1024. Now that i have downgraded could not check it. The old version allows to allocate more than 1.5gig i used the Guest OS with 1536mb of ram.
Aparently from log it did still not change the ram to 1500mb and kept it 1536mb. Is the config xml cached anywhere? I deleted and create the vm at same location so should have picked up new setting of 1500gig.
Is this limitaion of 1.5gb new with version 3.0.6? This is absurd.. why would they want to limit the VM to 1.5 gig.
When i could not start the VM i deleted the VM and created a new one pointing to same old hard drive and the UI did not allow me to set more than 1500mb of ram. So i think the ram was already set this limit. But inspite of this the VM crashed though i did not try it with 1024. Now that i have downgraded could not check it. The old version allows to allocate more than 1.5gig i used the Guest OS with 1536mb of ram.
Aparently from log it did still not change the ram to 1500mb and kept it 1536mb. Is the config xml cached anywhere? I deleted and create the vm at same location so should have picked up new setting of 1500gig.
Perryg wrote:From the log
Host RAM: 4093MB RAM, available: 2803MB
assigned = 1,572,864,000
They have limited the guest to 1/2 of the available memory and no more than 1.5 gig
Try setting the RAM to the host at 1024 Meg and see if it works.
Sameer Dhoot
http://sharemypoint.in
http://sharemypoint.in
-
imperator_cz
- Posts: 1
- Joined: 14. Sep 2009, 11:21
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: Windows Server 2008 R2
Re: Upgrade 3.0.4 -> 3.0.6 Crashes Guest OS
Hello.
I have exactly the same problem
Host OS: Windows XP SP2 x86
Guest OS: Windows Server 2008 R2 x64 -- RAM assigned 512MB
When starting guest it hangs up in blank (black) loading screen. HDD indicator indicate no activity.
I also tried start Windows 7 guest and Windows Server 2003 R2 and they work fine. Everything worked perfectly on previous version.
EDIT: Log file attachement
I have exactly the same problem
Host OS: Windows XP SP2 x86
Guest OS: Windows Server 2008 R2 x64 -- RAM assigned 512MB
When starting guest it hangs up in blank (black) loading screen. HDD indicator indicate no activity.
I also tried start Windows 7 guest and Windows Server 2003 R2 and they work fine. Everything worked perfectly on previous version.
EDIT: Log file attachement
- Attachments
-
w2k8r2.log- (40.86 KiB) Downloaded 8 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: Upgrade 3.0.4 -> 3.0.6 Crashes Guest OS
This may be a little too low for the 64 bit OS. Try to assign 768 meg and see if this helps. Really a 64 Bit OS as a guest in a system with only 2 gig total RAM is really asking a lot. But since you say this worked in 3.0.4 I would suggest that you revert back and live with it until you have more memory.Windows Server 2008 R2 x64 -- RAM assigned 512MB