Install failure for Ubuntu 8.04 on Vista 32-bit host -> fixed in SVN/2.1.4

I'm not sure how to provide more information since this causes my machine to freeze. Can someone provide some feedback on how I might get more information before the machine dies?

Attaching VBox.log of a started VM (don't wait for the problem to occur; close immediately) would help.

Have you enabled VT-x/AMD-V for the VM? If so, try to disable it.

I will retry setting up that guest and re-install to provide a vbox.log. For now, I did track down the following information in the windows event log. I don't know how much help it will be:

Faulting application VirtualBox.exe, version 0.0.0.0, time stamp 0x48ca75c1, faulting module VBoxQtGui4.dll, version 4.3.3.0, time stamp 0x4858ed16, exception code 0xc0000005, fault offset 0x001200ab, process id 0x1184, application start time 0x01c9193dd75e8cf4.

First Try - Crashed

Fault bucket 926644387, type 1 Event Name: APPCRASH Response: None Cab Id: 0

Problem signature: P1: VirtualBox.exe P2: 0.0.0.0 P3: 48ca75c1 P4: VBoxQtGui4.dll P5: 4.3.3.0 P6: 4858ed16 P7: c0000005 P8: 001200ab P9: P10:

Attached files: C:\Users\van\AppData?\Local\Temp\WER47F9.tmp.version.txt These files may be available here: C:\Users\van\AppData?\Local\Microsoft\Windows\WER\ReportArchive?\Report126d83ff

Second Try - Crashed

Faulting application VirtualBox.exe, version 0.0.0.0, time stamp 0x48ca75c1, faulting module VBoxQtGui4.dll, version 4.3.3.0, time stamp 0x4858ed16, exception code 0xc0000005, fault offset 0x001200ab, process id 0x1184, application start time 0x01c9193dd75e8cf4.

Fault bucket 926644387, type 1 Event Name: APPCRASH Response: None Cab Id: 0

Problem signature: P1: VirtualBox.exe P2: 0.0.0.0 P3: 48ca75c1 P4: VBoxQtGui4.dll P5: 4.3.3.0 P6: 4858ed16 P7: c0000005 P8: 001200ab P9: P10:

Attached files: C:\Users\van\AppData?\Local\Temp\WERBA89.tmp.version.txt

These files may be available here: C:\Users\van\AppData?\Local\Microsoft\Windows\WER\ReportArchive?\Report171fd2ba

Thanks for these information but: Please attach the VBox.log file as you were asked.

The same as me! =( I think that some instruction of linux kernel is incompatible to my cpu Core2Duo T5550 and go in crash. I've tried a lot of distribution.

Instead Windows run perfectly in VirtualBox.

I'll try to boot Ubuntu Intrepid that has the new kernel 2.6.27.

Log File of loading existing CentOS VM in Windows Vista.

This is happening to me, too. Virtualbox 2.0.2, Vista 32 bit Home Premium host. I have tried installing various flavors of linux but they all crash in this way. I have tried installing: fedora 9, Ubuntu 8.04, Ubuntu 8.10, CentOS 5.2 guests, but they all crash. I have a strong hunch it is related to ATI graphics driver (Card is crappy Radeon HD 2400 PCIE which came with the cheap desktop machine).

I even tried creating CentOS 5.2 VM under my Ubuntu 8.10 partition (dual boot), which runs fine under Ubuntu 8.10, but when I try to load that existing and working VM on Windows Vista host, it also crashes.

Seems to crash about the time it tries to load extended video features (i.e. not console boot process).

I just reproduced this error again, and have attached 3 files.

VB_Vista_error.txt is the text/details of "Windows has recovered from an unexpected shutdown" error message that appears on first reboot after failure. I also included the files mentioned in the output. I don't think you need my .dmp file but let me know if it will help.

When I tell windows to search for a solution, it blames it on ATI graphics driver and suggests installing a newer version (but I just upgraded/reinstalled the driver yesterday, and I am sure it is newest version).

The error popup on first reboot after failure

1 of the files mentioned in vista post-crash report

sysdata.xml - mentioned in crash report

Also FYI it appears my CPU does not support VT-x/AMD-V.

I can confirm that this is also happening to me on an LG laptop with T5450 and ATI Xpress 1250. I get to the starting point of Ubuntu instal where I can select to instal, check memory, or check install media. Interesingly, I also get the BSOD as soon as I select check media.

I noticed that in my system event log I get the system warnings event 4101:

"Display driver atikmdag stopped responding and has successfylly recovered"

I get a bout 6 of these in the log in the span of a minute followed by the BSOD.

Hi,

Are you using a laptop with both wireless and wired network connections? I get the same errors though only when using the wired connection.

Replying to mabrahamsson:

Hi, Are you using a laptop with both wireless and wired network connections? I get the same errors though only when using the wired connection.

for me it happens on my desktop, it does have a wireless card, and an on-board ethernet card, but I only use the wireless.

Everything I can find attributes this to the ATI driver, though.

--Matt

Yes, I do have a laptop with both wired and wireless. I'll try it without the wired connection. Question, has anyone tried with the new release of Ubuntu 8.10? I heard somewhere that the ATI problems have been addressed with this release.

Replying to cicatrix1:

Replying to mabrahamsson:

Hi, Are you using a laptop with both wireless and wired network connections? I get the same errors though only when using the wired connection.

for me it happens on my desktop, it does have a wireless card, and an on-board ethernet card, but I only use the wireless. Everything I can find attributes this to the ATI driver, though. --Matt

mabrahamsson: that's an interesting observation you made there. The wired network device is part of some integrated ATI chipset? There aren't newer Windows drivers available?

By the way, when you do use the wired connection, are you using NAT or host interface networking in VirtualBox?

Getting same issue.

Same problem here both installing Ubuntu or trying to start a preinstalled VM. I am attaching the log I got.

The problem also happens using VitualBox? 2.0.4, 2.0.6 or 2.1.0

I might have an idea what's causing this. It's a bit of a guess as we've never been able to reproduce this here.

This theory assumes that only Linux VMs will trigger this host crash/hang. At least Windows VMs should not.

If anybody wants to try a test build, please let me know (here).

This fix will be in the next maintenance release (due out soon).