VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (307 - 309 of 16363)

Ticket Resolution Summary Owner Reporter
#7778 obsolete 3.2.10 crashes on exit (bus error in QtGuiVBox) RJVB
Description

Recent VirtualBox 3.2.10 installation on a MacbookPro 7,1 running OS X 10.6.5; 6Gb RAM.

Virtual Box crashes persistently on exit, due to a bus error in QtGuiVBox. This happens after running a VM, but also when exitting Virtual Box immediately after launching.

I've attached a few crash reports (which don't seem to get submitted unlike all other crash reports?!)

#7638 fixed 3.2.10 r66523 Freezes Xserver and takes segfault John P. Hartmann
Description

The setup runs vbox on a headless 64-bit Fedora 13 (linux). The X server is a 32-bit Fedora 13 on an atom processor. Virtual OS win2k.

After a while the X server freezes up and must be manually reset (rebooted). Last this happened, windows was idle and the screensaver active.

The syslog where Vbox is running shows two messages related to vbox:

VirtualBox[17597]: segfault at 8 ip 00007f228c8aae48 sp 00007f227ab96980 error 6 in VirtualBox.so[7f228c680000+43e000]

At this point it is possible to log in the user that started Vbox, but it never gets the shell prompt. I can log in as root and see all the processes.

about 3 minutes later after the X server is rebooted:

VirtualBox[17533] general protection ip:3f7c275795 sp:7fff9284a530 error:0 in libc-2.12.1.so[3f7c200000+175000]

At this point all VBox processes have disappeared without trace.

I am appending the log file, but it contains no information.

I could not find any core dumps. Where would it be in my file system?

j.

#7827 fixed 3.2.12 BUG during modprobe on x86_64 if CONFIG_DEBUG_SET_MODULE_RONX set in kernel Valdis Kletnieks
Description

A heads-up for possible kernel incompatibility coming down the pipe...

Recent linux-next (targeting the 2.6.38 release) development kernels include an extension to allow modules to also be set to RO/NX status. It looks like the problem is that g_abExecMemory is defined with permission bits 'awx'. I haven't studied it enough to tell if redefining it with other permissions will suffice, or if you'll need to open-code the unset_section_ro_nx() function from the patch, or if it should be a permanent restriction that SET_MODULE_RONX=n has to be in the kernel config, or some other solution.

The problematic patch is here: http://git.kernel.org/tip/84e1c6bb38eb318e456558b610396d9f1afaabf0

I've attached the ugly details of the crash

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy