VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1975 - 1977 of 16363)

Ticket Resolution Summary Owner Reporter
#2020 invalid Patch to VBox.sh for Linux 2.4.x host kernels abe_skolnik
Description

here is a patch that removes annoying erroneous warnings when vboxdrv.o [note: _not_ .ko, as in Linux 2.6] is already loaded:

* VBox.sh Wed Aug 27 23:14:51 2008 --- VBox.sh_orig Wed Aug 27 22:46:43 2008 * * 32,40

if [ "$1" = "shutdown" ]; then

SHUTDOWN="true"

! # The following patch to prevent spurious unnecessary warnings when running on a 2.4.x host kernel written by Abe Skolnik 2008-8-27 ! # elif [ ! -e /lib/modules/uname -r/misc/vboxdrv.ko ]; then ! elif [ ! -e /lib/modules/uname -r/misc/vboxdrv.ko ] && [ ! -e /lib/modules/uname -r/misc/vboxdrv.o ]; then

cat << EOF

WARNING: There is no module available for the current kernel (uname -r).

Please recompile the kernel module and install it by:

--- 32,38 ----

if [ "$1" = "shutdown" ]; then

SHUTDOWN="true"

! elif [ ! -e /lib/modules/uname -r/misc/vboxdrv.ko ]; then

cat << EOF

WARNING: There is no module available for the current kernel (uname -r).

Please recompile the kernel module and install it by:

#2021 worksforme VDI corruption (or file size limitation?) Jan Schmidt
Description

I have an Ubuntu Hardy VM image that I've been using for a few months, running in an OS/X host. After a reboot of the laptop yesterday, the VM started refusing to boot - getting about halfway through the boot process, and then reporting a cascade of ATA errors, that I'd call 'faulty hard drive' errors, except that they're coming from a VDI file and the host disk is fine. The error output brings the host to its knees with IO, and I typically have to kill the VM, since I can't get it to respond sufficiently to power off.

Attaching a VBox log from when it happens. In the log, it's reporting VERR_EOF when trying to access certain sectors of the VDI. In case it's relevant, the VDI image is at 15.5GB of a 20GB allocation.

I've just tried compacting the VDI, which worked through the image without any warnings or errors, and that seems to have allowed it to boot. Some of the files in the filesystem seem to be corrupted though (filled with 0 bytes). I'm not sure how to diagnose it further.

#2022 obsolete Problem with recognition of the battery on a Sony Vaio notebook. Aziz K.
Description

Hello!

I have this issue with my notebook battery. I get an error message from a Sony Vaio utility (see screenshot in the attachment). The message box can't be clicked away and it wants to put the computer to sleep. I can only avoid this by killing the task ISBMgr.exe using the Task Manager.

Here is the English version of the text:

The installed battery may not be properly connected to the computer or may not be compatible with the computer.


Click "OK" to enter Hibernate mode, and remove and reinsert the battery.

See the VAIO(R) User Guide for more information about using the battery.

The utility that causes the error message can probably be deactivated from running at the start, though I haven't tried this, but I'd rather not to because I'm booting Win XP from a physical partition.

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