Page 1 of 4

VB always aborting.

Posted: 19. May 2007, 16:02
by Grumpy
My virtual box is always aborting after a short but random period of use. It seems to abort only when I run applications actively as I've tried to leave windows overnight and all was ok.

My settings are:

General
Name
Windows XP Professional
OS Type
Windows XP
Base Memory
250 MB
Video Memory
8 MB
Boot Order
Floppy, CD/DVD-ROM, Hard Disk
ACPI
Enabled
IO APIC
Enabled

Can anyone with experience give me some help? thanks.

Posted: 19. May 2007, 16:30
by moonlight
Please check VBoxSVC.log - in may contain useful information.

It's also may be good idea to use
http://virtualbox.org/wiki/Bugtracker

Posted: 19. May 2007, 18:41
by Grumpy
Thanks for directing me where to look. I see that the crashes are cause by this:

Qt WARNING: X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Qt WARNING: Failed to open device

Does anyone know what could be the problem? Also do I need to supply the backtrace and the memory map as well so to find out about the problem?

Posted: 21. May 2007, 20:08
by Cogar
Your memory may be too low. You might want to increase it 50% to 384MB and see how that works.

Posted: 23. May 2007, 15:25
by michael
That
Qt WARNING: X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Qt WARNING: Failed to open device
stuff is not related to VirtualBox. As far as I can see it is something to do with the way Qt is set up on Ubuntu (it triggers for all KDE applications) and is harmless.

Posted: 23. May 2007, 15:29
by michael
You might also want to take a look in the log file for the virtual machine (/home/<user>/.VirtualBox/Machines/<machine>/Logs contains the logs, numbered from the most recent to the oldest). And as moonlight suggested, try opening a bug report for it and posting the log there.

Posted: 11. Sep 2007, 18:37
by vista killer
i have the same problem with virtual box 1.5.0 in my system.I have kubuntu 7.04 with 3.5.7 kde.My hardware is cpu 6600,2g ram.I always give up to 512 mb ram to my virtual desktop.The problem is the random crashes of virtual desktop(abort).

Posted: 11. Sep 2007, 18:42
by michael
VirtualBox 1.5.2 is due out in a few days, and contains fixes for a number of abort problems. If you still have the problem with VirtualBox 1.5.2, you might want to go through the tickets on http://virtualbox.org/wiki/Bugtracker to look for an appropriate one and add a comment.

Posted: 12. Sep 2007, 12:22
by vista killer
I don't know if i have the last version of virtual box.I have the virtual box repos in my system and before one week virtual box updated.Normally i have the latest vb version but the abort problem still exist.

Posted: 12. Sep 2007, 22:06
by chriz
That aborting annoys me too.

It happens on VirtualBox 1.4, 1.5 and now 1.5.51-OSE on Fedora 7 host with Windows 2000 guest.

I created ticket #628 (http://www.virtualbox.org/ticket/628) with backtraces etc.

Posted: 13. Sep 2007, 18:00
by bsmith1051
Exact same prob here, VB 1.5.0 on Ubuntu 7.04, AMD X2 5600 w 2G. Please post here when 1.5.2 is released so that I get the Reply Notification!

VB always aborting

Posted: 14. Sep 2007, 17:22
by jbeiter
Just to chime in, ever since I upgraded to 1.5, I keep getting random aborts. Happens during various activities and applications, but usually with MS Outlook.

host: Ubuntu 7.04

Guest:
OS Type
Windows XP
Base Memory
1008 MB
Video Memory
38 MB
Boot Order
Floppy, CD/DVD-ROM, Hard Disk
ACPI
Enabled
IO APIC
Disabled

Hard Disks
Primary Master
laptop-image.vdi [Normal, 9.77 GB]

CD/DVD-ROM
Host Drive
/dev/scd0

Floppy
Not mounted

Audio
Adapter
OSS Audio Driver

Network
Adapter 1
NAT

Serial Ports
Disabled



USB
Device Filters
0 (0 active)


Shared Folders
Shared Folders
2


Remote Display
Disabled

Posted: 14. Sep 2007, 21:11
by chriz
Now I upgraded to 1.5.51_OSE r4786 (from wednesdays r4735) and it's still aborting.

Easily reproducable e.g. with holding down a character key in my favorite text editor for some seconds.

Logfile and backtrace see http://www.virtualbox.org/ticket/628)

Posted: 19. Sep 2007, 21:55
by jbeiter
Is this even acknowledged by innotek?

This aborting sucks. I keep loosing work.

Can I just load a prior version of virtual box without screwing up my VM?

I'm going to have to look into xen or go back to VMware if this is life in virtual box, which is unfortunate. The performance is good otherwise.

Posted: 20. Sep 2007, 12:15
by vista killer
just wait for the update