WinXP guest goes GURU while using serial port.

[hiwk]

WinXP guest, openSuSE 11.2 host. Failure is not deterministic, but always when I use a program (MTK3) to program a MAXQ1850 over serial port. Short passage of the log:

00:07:18.403 
00:07:18.403 !!Assertion Failed!!
00:07:18.403 Expression: RT_SUCCESS_NP(rc)
00:07:18.403 Location  : /home/vbox/vbox-4.0.0/src/VBox/VMM/VMMGC/TRPMGCHandlers.cpp(225) int trpmGCExitTrap(VM*, VMCPU*, int, CPUMCTXCORE*)
00:07:18.438 PDMGetInterrupt failed with -304
00:07:19.440 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:07:19.440 !!
00:07:19.440 !!                 Guru Meditation 1103 (VINF_EM_DBG_HYPER_ASSERTION)
00:07:19.440 !!
00:07:19.440 !!Assertion Failed!!
00:07:19.440 Expression: RT_SUCCESS_NP(rc)
00:07:19.440 Location  : /home/vbox/vbox-4.0.0/src/VBox/VMM/VMMGC/TRPMGCHandlers.cpp(225) int trpmGCExitTrap(VM*, VMCPU*, int, CPUMCTXCORE*)
00:07:19.440 PDMGetInterrupt failed with -304

[hiwk]

Log file.

[hiwk]

Screenshot.

[hiwk]

Another log file.

[hiwk]

Another screenshot.

[aeichner]

The log shows that your host has VT-x disabled in the BIOS. You could try to enable it and see if that helps.

[hiwk]

Tried to find that setting in BIOS (786H1), couldn't find any.

I have upgraded to VirtualBox 4.0.2, same problem.

[Teuniz]

I have the same problem here, using the latest version of Virtualbox. Host is OpenSuse 11.3, guest is windows XP. I get communication errors when I try to use my Microchip PicstartPlus programmer via the serial port. With the latest Virtualbox 3.X.X it worked fine.

[Teuniz]

For your information: VT-x is enabled.

[Frank Mehnert]

There is a slight chance that this bug was fixed in VBox 4.0.4 -- could you test please?

[hiwk]

Log file under 4.0.4

[hiwk]

Same problem under 4.0.4, new log attached.

[Emerson Prado]

I used some versions from 3.something up to 4.0.8 without having this problem. Yesterday I upgraded to 4.0.12*, and used it without problems either. Today, this same error ocurred in my first usage. The VM crashed with the already described error as soon as I tried to open an app which uses the serial ports. I used this app all times I opened this VM - just to dismiss it as a point. I couldn't reproduce it so far (maybe only restarting or shutting down/up host, what I can't do now). Host OS: Linux Mint Debian Edition (sync'ed to Debian Stable repos) kernel 2.6.32-5-686 Guest OS: Windows 2000 SP4 Ports ttyS1 and S2 mapped to COM1 and COM2. Physically, they're a PCI to serial adapter NetMos Technology PCI 9835 Multi-I/O Controller (rev 01). I have the logs if someone wants. I thought about upgrading to 4.1.2, but I'll try a bit more to reproduce the problem and finding the conditions that lead it to happen.

*What encouraged me for the upgrade was an error in the serial ports. I ended up learning that the PCI to serial adapter just came loose in the slot. I guess it's a coincidence, but found better to mention it than not.

[Emerson Prado]

Log of guru meditation without serial app

[Emerson Prado]

Today it happened again in a new VM. Guest OS is WinXP SP3. Failure happened after I installed MSSQL 2000 Release A and restarted. Crashed when XP was starting to boot. Same error message in the log. I didn't even install my software which uses the serial ports. This may mean the serial app is not the issue or my problem is unrelated to the bug. Anyway, I'm sending a log too. BTW, I restarted the VM and it's working without problems.

[Emerson Prado]

After a good while without seeing the problem, today it started again. I'm using now VirtualBox 4.1.18. It happened after some serial port communications. As I mentioned before, I use serial ports all the time in this VM - I test equipments under service - and guru meditation happens during test software utilization. The error is just like the reported one. I created a core dump and will send it along with the log, just in case.

[Emerson Prado]

Log of crash with 4.1.18

[Emerson Prado]

Oops, core dump, even compressed, is several times bigger than the allowed attachment limit. If anyone is interested, I'll divide it in pieces and send here.

[Frank Mehnert]

That log was taken with VBox 4.1.8 not 4.1.18 but actually I don't think that there was a related fix in between...