VirtualBox

Ticket #367 (closed defect: fixed)

Opened 7 years ago

Last modified 4 years ago

Invalid write causes crash on my XP guest (Stop monitoring IDT handler)

Reported by: Piwai Owned by:
Priority: major Component: other
Version: VirtualBox 1.3.8 Keywords: invalid write crash
Cc: Guest type: other
Host type: other

Description

I installed VirtualBox on my Ubuntu 7.04 Feisty ( with a Debian package :  http://www.virtualbox.org/download/1.3.8/VirtualBox_1.3.8_Ubuntu_feisty_i386.deb).

I created a 5Gb virtual partition, and I installed Windows XP Pro SP2.

I only installed a few software on the XP OS ( + the guest additions)

The VirtualBox crashes at random, whenever I'm doing something on it or not. The state of the VB changes, from Running, to Aborted.

I've looked at the log files, it seems that there is a problem of invalid write, always the same :

00:01:30.109 PATM: Stop monitoring IDT handler pages at 806f2d50 - invalid write 806f3ac8-806f3acc 00:01:30.109 PATM: Disable block at 806f304d - invalid write 806f3ac8-806f3acc

I'll attach 2 or 3 crash log files with the ticket, so that you may compare.

Do not hesitate to ask me for further information, I'll check this ticket from time to time (I'd like this problem to be solved :p).

PS : I'm not used to writing bug tickets, I hope I used the good syntax (moreover I'm french and my english is not so good).

Attachments

VBox.log Download (26.3 KB) - added by Piwai 7 years ago.
log
VBox.log.1 Download (26.4 KB) - added by Piwai 7 years ago.
VBox.log.2 Download (26.1 KB) - added by Piwai 7 years ago.
Random Crash VBox.log Download (33.4 KB) - added by kenken 7 years ago.
Same problem, Ubuntu Feisty but 1.4.0
VBox.log.2.1 Download (71.6 KB) - added by Xpheroid 7 years ago.
VBox.2.log Download (23.7 KB) - added by MaxMill 7 years ago.
crash Stop monitoring IDT handler

Change History

Changed 7 years ago by Piwai

log

Changed 7 years ago by Piwai

Changed 7 years ago by Piwai

comment:1 Changed 7 years ago by OxoTnicK

I have the same problem exactly.

comment:2 Changed 7 years ago by Piwai

Well, I hope it will be resolved soon...

Anyway, I can't use the virtualBox any more : the ubuntu automatic update to the last version of the linux kernel made Vbox crash when starting the virtualbox. Can't remember to message right now, I tried to reinstall, but it didn't work... I'm waiting for a vbox upgrade...

comment:3 Changed 7 years ago by joseph85750

I'm having the same problem, but I don't think the errors in the log are related to the crash. The last errors I see in the log are:

01:04:01.995 PATM: Stop monitoring IDT handler pages at 81e11044 - invalid write 81e116a0-81e116a4

But I know the XP instance was running/healthy for 5 more hours. The timestamp of the vdi file is 06:02. Also, my XP instance was doing some work creating files on a remote server just prior to 6:02, so that agrees with what I observed.

I'm running: VirtualBox-1.4.0_21864_openSUSE102-1.i586.rpm (OpenSuse 10.2).

I was thinking about trying it under CentOS 5, but it appears to be distribution independent. I notice others having the problem under Ubuntu.

Changed 7 years ago by kenken

Same problem, Ubuntu Feisty but 1.4.0

Changed 7 years ago by Xpheroid

comment:4 Changed 7 years ago by Xpheroid

Same happening here. Kubuntu Feisty host, XPSP2 guest. Using 1.4.0.

comment:5 Changed 7 years ago by joseph85750

I patched my WinXP virtual instances to the latest/greatest everything from Microsoft, rebooted the WinXP VMs 2 or 3 times, patched again, rebooted, etc., and have not had VirtualBox crash since. Try patching your VMs and see how that works.

comment:6 Changed 7 years ago by joseph85750

Today a couple of my VMs crashed. But, they have been running rock solid for almost a week! Not too bad I guess.

This leads me to my next question-- Is there a way to "power on" a single VM via command line? In other words, if instance 1 is still running, but instance 2 is "aborted", is there something I can enter on command line (or via cron) that would start that instance 2 back up? I was thinking about writing a 'checker' script that would detect if a VM had died, and if so, start it up again. I was hoping for something like: $ VirtualBox --start 2 Or something. But 'man VirtualBox' or 'VirgualBox --help' yield nothing.

Thanks!

comment:7 Changed 7 years ago by joseph85750

I just found my answer by looking at some of the binaries, and running one with no options:

$ VBoxManage

Specifically:

$ VBoxManage startvm <name of vm>

Works great!

Changed 7 years ago by MaxMill

crash Stop monitoring IDT handler

comment:8 Changed 7 years ago by MaxMill

Anything new here? I have the same problem as the topic opener.

Vbox 1.4 on Debian Testing with Winxp SP2 guest.

Thanks in advance, Maximilian Mill

comment:9 Changed 7 years ago by joseph85750

I've heard nothing. So, I wrote a VirtualBoxLazarus.pl (perl script) which runs every minute and detects whether or not the VBs are running. If any are not running, it starts them, logs the restart, and emails me that it restarted the VB(s).

comment:10 Changed 7 years ago by sandervl73

Wait a bit and try again with the upcoming 1.5.0 (later this week). Please report back if you still see such problems.

comment:11 Changed 7 years ago by Piwai

Ok, I'll look for it next week. Should we try on a new VM, or will it work on an existing VM ?

If I just have to update virtualbox, then I will give you quick feedback.

comment:12 Changed 7 years ago by sandervl73

It will work with your existing VM.

comment:13 Changed 7 years ago by booyah

This is still occurring for me using 1.5.0

comment:14 Changed 7 years ago by Kripton

I've got the same problem here. Running 1.5.0 OSE on Gentoo Linux 2.6 host (will try binary build instead of OSE later), windows 2000 guest-OS.

comment:15 Changed 7 years ago by Kripton

Some news about this: I tried using the non-OSE and it crashes there, too. But as far as I can see, it only crashes while having the mouse grabbed by the VM. I'm running VB pretty stable as long as I don't have the mouse grabbed. Can be pretty handicapping when browsing super-multimedia-webpages which can only be used with a mouse.

comment:16 Changed 7 years ago by Kripton

Ok, further investigation showed that is has nothing to do with having the mouse attached or not. It crashes sometimes with heavy disk-IO-load and my host-CPU-cores beeing idle. Running BOINC, clocking down the cores, disabling all but one core or keeping them occupied otherwise helps here. And: Linux guests are affected by this bug, too.

comment:17 Changed 6 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

Try again with 1.5.2. We've fixed several bugs there that cause seemingly unexplainable crashes. Reopen if it still happens.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use