virtualbox.org

On a Win7 host I can't get guest additions to work in a Debian wheezy guest using kernel 3.2.0.3. I've tried the 4.1.18 additions from virtualbox.org, and the 4.1.18 additions from the debian package repository. The problem is that a few seconds after I log in virtualbox crashes with:

Oracle VM VirtualBox Manager has stopped working...

Mixing the guest additions is never a good idea. I would purge them in the guest and make sure it is working, then install the guest additions from VirtualBox.org. If this still fails you will need to post the guest log file (as an attachment).

Perryg wrote:purge [all additions] in the guest and make sure it is working

I did that. debian's version is gone via "apt-get --purge ..." and VirtualBox.org's version is gone via "sh VBoxLinuxAdditions.sh uninstall".

Perryg wrote:make sure it is working

I rebooted and had no problem using the guest without the additions support.

Perryg wrote:install the guest additions from VirtualBox.org

This seemed to work, but I get the following warning:

"The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason."

After that the compilation succeeds. I'm thinking this warning is because I'm running a stock kernel, and not one compiled on this machine. I don't know. I have installed debian's linux-header package that matches my kernel version, and I've actually installed the entire kernel source. Anyway, there are no errors during compilation or module installation. Then, after a reboot I have the same problem. The system comes up fine, I can see that the additions have been installed because automatic screen resizing is working, but a few seconds after I log in vbox crashes.

post the guest log file (as an attachment)

Attached.

Thanks.

If you receive the error you mentioned then the headers do not match the kernel. Try the following: Then install the guest additions again.
Make note of any errors.

Perryg wrote:

Code: Select all

apt-get install kernel-headers-$(uname -r)

That fails with "unable to locate package kernel-headers-3.2.0-3-amd64". However, replacing "kernel" with "linux" gives:

"linux-headers-3.2.0-3-amd64 is already the newest version".

So, I think I have the correct package installed.

Yes sorry the night is long, and I made a typo.
However if you receive the error even though the headers are installed there must be a problem. I never see this unless there is an issue with the running kernel and the headers being out of sync. Have you installed dkms and also updated the guest?

Perryg wrote: Have you installed dkms

I hadn't. (It automatically installed as part of the debian guest additions, but I removed it after I removed the debian additions.) After installing dkms there were no more warnings while installing the VirtualBox.org additions. However, after reboot the crashing problem persists. I've attached a new log file.

Perryg wrote:updated the guest?

Yes. "apt-get update; apt-get upgrade" shows nothing is needed.

FYI, debian squeeze works with no problems.

There is no indication of the crash in the log file, which puts it guest side. Look at the syslogs of the guest and see if it indicates the cause. Also can you define crash a bit better? How or what does it actually so. Another thing, does it continue to work if you disable 3D in the guests settings?

Perryg wrote:disable 3D in the guests settings?

"Display | Enable 3D Acceleration" had been enabled. After disabling that and starting the guest the problem has disappeared. Thanks.

Perryg wrote:the syslogs of the guest

I'm not seeing a cause there, but I'm not experienced in reading those. I've attached an excerpt that starts with the most-recent boot of the guest with 3D enabled. The crash seems to occur at line 527 where we see a half-formed line of the log file, where the beginning of the line is part of the timestamp from the time of the crash, and the end of the line is the first new log entry after booting with 3D disabled. The log file ends when it is rotated shortly after the successful boot.

Perryg wrote:define crash a bit better

With 3D enabled the gdm login screen comes up fine. I can resize the guest window and it seems fine. A few seconds after I log in then the Windows diagnostic pop-up appears telling me:

Oracle VM VirtualBox Manager has stopped working...

Then it offers me the option to tell Microsoft about the problem, and so on. I've never followed that dialog, but I've always canceled it. In the Windows event viewer, under "Windows Logs | Application" I see an entry that seems to correspond to the crash. I've attached that.

Thanks for taking the time with this. At this point I'm content without 3D, but I'm willing to continue troubleshooting.

Alright. I see you have an Intel graphics adapter which is known to have issues with the virtual guest and 3D acceleration. Best thing that you can do is make sure that you have the latest drivers on the host side. Wheezy is pushing the driver harder than squeeze did so that is probably why it does not show the same issue.

Perryg wrote:make sure that you have the latest drivers on the host side

It seems I have the latest display drivers. The Intel driver update utility scanned my system and then told me to get drivers from Toshiba. The Toshiba driver location tool showed that the latest version for my model laptop is the same version as what Windows Device Manager showed was already installed. For fun I installed the drivers from Toshiba, anyway. There were no problems with that installation, but the wheezy crash problem persists.

My system is an "Intel Core Processor with Intel HD Graphics," and the driver version I have installed is 8.15.10.2086. The latest from Intel seems to be 8.15.10.2622. I could try the latest Intel driver just to see what happens, even though Intel recommends I stick with the version from Toshiba.

xthx1138 wrote:system is an "Intel Core Processor with Intel HD Graphics," and the driver version I have installed is 8.15.10.2086. The latest from Intel seems to be 8.15.10.2622

I also have a latter-model laptop with the same type Intel hardware, but newer display drivers. On this host everything is fine. Wheezy works with 3D. The Intel driver version on this newer laptop is 8.15.10.2430.