virtualBox crashes after installing GuestAditions (win7)

This is for discussing general topics about how to use VirtualBox.
Post Reply
justinrpg
Posts: 142
Joined: 18. Mar 2011, 00:33
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP Ubuntu Fedora LinuxMint Mageia

virtualBox crashes after installing GuestAditions (win7)

Post by justinrpg »

every time I log onto the guest in VirtualBox after installing the Guest additions that support Aero, it causes VirtualBox to crash
Attachments
VBox.log
(51.86 KiB) Downloaded 6 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: virtualBox crashes after installing GuestAditions (win7)

Post by Perryg »

Code: Select all

VirtualBox 4.1.12 r77218 win.x86
You need to newer version of VirtualBox. 77245

Also there are problems with your graphics adapter

Code: Select all

00:01:30.251 OpenGL Info: Render SPU: GL_VENDOR:   Intel
00:01:30.251 OpenGL Info: Render SPU: GL_RENDERER: Intel 965/963 Graphics Media Accelerator
00:01:30.251 OpenGL Info: Render SPU: GL_VERSION:  2.0.0 - Build 8.14.10.1930
You must be running the latest host drivers and even then that Intel graphics model has been known to cause issues with accelerated (virtual) graphics.
justinrpg
Posts: 142
Joined: 18. Mar 2011, 00:33
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP Ubuntu Fedora LinuxMint Mageia

Re: virtualBox crashes after installing GuestAditions (win7)

Post by justinrpg »

but 4.1.12 is the latest! I got the update last week! what do you mean mine is outdated??
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: virtualBox crashes after installing GuestAditions (win7)

Post by Perryg »

Did you go to the download and check? Of course not, or you would see exactly what I said.

And I quote.
"There was a last-minute regression in the original 4.1.12 builds from April 2nd, (build 4.1.12-77218) which was silently fixed by replacing all builds (new build 4.1.12-77245)."
Post Reply