VirtualBox

Ticket #575 (closed defect: fixed)

Opened 10 years ago

Last modified 7 years ago

Guests randomly abort.

Reported by: phzi Owned by:
Priority: critical Component: other
Version: VirtualBox 1.4.0 Keywords: Abort, Windows, XP, Sabayon, Linux, Aborted
Cc: Guest type: other
Host type: other

Description

I have run both a WindowsXP Pro SP2 Guest, and a Ubuntu Linux Guest, on my Sabayon Linux 3.4e install. While running, Virtualized Sessions randomly close, and enter the 'Aborted' state.

Attachments

VBox.log.1.ubuntu Download (30.8 KB) - added by phzi 10 years ago.
Ubuntu Guest Log
VBox.log.1 Download (25.3 KB) - added by phzi 10 years ago.
Windows XP Pro Guest Log

Change History

Changed 10 years ago by phzi

Ubuntu Guest Log

Changed 10 years ago by phzi

Windows XP Pro Guest Log

comment:1 Changed 10 years ago by phzi

I started another session, and left it idling until it crashed, the end of the log is:

00:29:52.799 VBVA: Enabled.
01:07:23.028 PATM: Stop monitoring IDT handler pages at 821da9ac - invalid write 821dae30-821dae34 
01:10:29.127 PATM: Stop monitoring IDT handler pages at 806f2d50 - invalid write 806f3ac8-806f3acc 
01:10:29.127 PATM: Disable block at 806f304d - invalid write 806f3ac8-806f3acc 

comment:2 Changed 10 years ago by sandervl73

That part is unrelated to the abort. It's a VBox crash of some kind as the log isn't complete. Please wait for the next release to try again. (due out very soon)

comment:3 Changed 9 years ago by frank

Please could you try VirtualBox 1.5.0? If the problem still persists, please could you try to disable the clipboard?

comment:4 Changed 9 years ago by booyah

I have this problem on 1.5.0 with clipboard disabled. Moving from fact to speculation now, it might be crashing on some disk activity. The guest always seems to crash after I do something intensive (like launch and antivirus install). Last thing in my logs:

vbox.log 00:00:32.491 Guest Additions capability report: (0x1) VMMDEV_GUEST_SUPPORTS_SEAMLESS: yes VMMDEV_GUEST_SUPPORTS_GUEST_HOST_WINDOW_MAPPING: no 00:00:36.782 PATM: Stop monitoring IDT handler pages at 80efacc4 - invalid write 80efa6d8-80efa6dc (this is not a fatal error) 00:00:56.712 PATM: Stop monitoring IDT handler pages at 80ec7044 - invalid write 80ec7d48-80ec7d4c (this is not a fatal error)

vbox.log.1 00:00:35.721 Guest Additions capability report: (0x1) VMMDEV_GUEST_SUPPORTS_SEAMLESS: yes VMMDEV_GUEST_SUPPORTS_GUEST_HOST_WINDOW_MAPPING: no 00:00:43.873 PATM: Stop monitoring IDT handler pages at 80efacc4 - invalid write 80efa5f0-80efa5f4 (this is not a fatal error) 00:01:16.743 PATM: Stop monitoring IDT handler pages at 80ec7044 - invalid write 80ec7d48-80ec7d4c (this is not a fatal error)

vbox.2.log 00:06:23.986 PATM: Stop monitoring IDT handler pages at 80ec7044 - invalid write 80ec7ab0-80ec7ab4 (this is not a fatal error) 00:26:36.203 PATM: Stop monitoring IDT handler pages at 80e6070c - invalid write 80e60f38-80e60f3c (this is not a fatal error) 00:26:55.889 PATM: Stop monitoring IDT handler pages at 806f2d50 - invalid write 806f3ac8-806f3acc (this is not a fatal error) 00:26:55.889 PATM: Disable block at 806f304d - invalid write 806f3ac8-806f3acc

vbox.3.log 00:05:30.486 PATM: Stop monitoring IDT handler pages at 806f2d50 - invalid write 806f3ac8-806f3acc (this is not a fatal error) 00:05:30.486 PATM: Disable block at 806f304d - invalid write 806f3ac8-806f3acc

comment:5 Changed 9 years ago by frank

Please retry with 1.5.2. We fixed a related bug.

comment:6 Changed 9 years ago by sandervl73

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

Reopen if it still happens in 1.5.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use