VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (499 - 501 of 16363)

Ticket Resolution Summary Owner Reporter
#11815 fixed Starting the VirtualBox Guest Additions [FAILED] in Fedora 18 Biswajit
Description

Hi, I've installed Fedora 18 32bit guest into a Oracle VM Virtualbox running on a windows 7 host. Previously I've installed Fedora 16 as the host machine and everything was working fine. Now after installing Fedora 18 i tried to install virtual-guest addition but there is some issue. I guess its BUG.

I had followers all the procedures correctly to install the VirtualBoxGuestAdditions

I am attaching the logs.

root@localhost VirtualBoxGuestAdditions]# sh ./VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 4.2.10 Guest Additions for Linux.......... VirtualBox Guest Additions installer Removing installed version 4.2.10 of VirtualBox Guest Additions... Removing existing VirtualBox DKMS kernel modules [ OK ] Removing existing VirtualBox non-DKMS kernel modules [ OK ] Building the VirtualBox Guest Additions kernel modules [ OK ] Doing non-kernel setup of the Guest Additions [ OK ] Starting the VirtualBox Guest Additions [FAILED] (modprobe vboxguest failed) Installing the Window System drivers Installing X.Org Server 1.13 modules [ OK ] Setting up the Window System to use the Guest Additions [ OK ] You may need to restart the hal service and the Window System (or just restart the guest system) to enable the Guest Additions.

Installing graphics libraries and desktop services componen[ OK ]

----------------------------------

[root@localhost VirtualBoxGuestAdditions]# cat /var/log/VBoxGuestAdditions.log

Starting vboxadd (via systemctl): Job for vboxadd.service failed. See 'systemctl status vboxadd.service' and 'journalctl -xn' for details. [FAILED] Starting vboxadd-service (via systemctl): Job for vboxadd-service.service failed. See 'systemctl status vboxadd-service.service' and 'journalctl -xn' for details. [FAILED] Starting vboxadd-x11 (via systemctl): [ OK ] [root@localhost VirtualBoxGuestAdditions]#

-----------------------------------------

[root@localhost VirtualBoxGuestAdditions]#systemctl status vboxadd.service

vboxadd.service - LSB: VirtualBox Linux Additions kernel modules

Loaded: loaded (/etc/rc.d/init.d/vboxadd) Active: failed (Result: exit-code) since Mon 2013-05-20 03:37:22 EDT; 4min

54s ago May 20 03:37:22 localhost.localdomain vboxadd[9543]: Starting the VirtualBox Guest Additions [FAILED] May 20 03:37:22 localhost.localdomain vboxadd[9543]: (modprobe vboxguest failed) May 20 03:37:22 localhost.localdomain systemd[1]: vboxadd.service: control process exited, code=exited status=1 May 20 03:37:22 localhost.localdomain systemd[1]: Failed to start LSB: VirtualBox Linux Additions kernel modules. May 20 03:37:22 localhost.localdomain systemd[1]: Unit vboxadd.service entered failed state. [root@localhost VirtualBoxGuestAdditions]#

-------------------------------------------------------

[root@localhost VirtualBoxGuestAdditions]# cat /var/log/vboxadd-install.log Uninstalling modules from DKMS Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxguest/4.2.10/source ->

/usr/src/vboxguest-4.2.10

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module: cleaning build area.... make KERNELRELEASE=3.9.2-200.fc18.i686.PAE -C /lib/modules/3.9.2-200.fc18.i686.PAE/build M=/var/lib/dkms/vboxguest/4.2.10/build............... cleaning build area....

DKMS: build completed.

vboxguest: Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/3.9.2-200.fc18.i686.PAE/extra/

vboxsf.ko: Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/3.9.2-200.fc18.i686.PAE/extra/

vboxvideo.ko: Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/3.9.2-200.fc18.i686.PAE/extra/

depmod....

DKMS: install completed. Creating user for the Guest Additions. Creating udev rule for the Guest Additions kernel module. [root@localhost VirtualBoxGuestAdditions]#

Best Regards,

Biswajit Sadhu

#10780 fixed HostMemoryLow - Ubuntu 12.04 Host Ops Ended BitMangler
Description

The single guest OS, Ubuntu 12.04 with Unity 3D enabled, I add allocated the maximum amount of memory that VBox allowed for a 32 bit Linux (which was indicated as ~3.5 GB in UI). I could consistently reproduce the HostMemoryLow error by using tar to extract a ~1.5 GB file which contained another large file inside. Once this bug occurs, there is no apparent way to safely shutdown the VM, as another dialog appears immediately afterwards, and the net affect is a cold power-off of the Guest. I did try reducing the amount of memory allocated to the Ubuntu/Linux guest to 3GB (vs. the max ~3.5), and the error remains consistent (still reproduced, shortly after tar command starts extracting a tar file in the Guest Linux). I did also note a very similar problem occurring, on the VirtualBox forums, for a Windows VirtualBox host. The user posted their VBox.log there as well. Might be interesting to compare his, with the one I'm posting in this report. As you'll note from my VBox.log, I have 24GB DDR3, and there was no other heavy loads on that host memory. VirtualBox is/was the only mass DDR consumer when this bug is reproduced.

https://forums.virtualbox.org/viewtopic.php?f=6&t=50090

The following message appears in a VBox Dialog, as well as the VBox.log:

Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM }}}
#15366 worksforme Yosemite 10.10.5 - Kernel Instability and Crash BitMangler
Description

It's possible that your developers are already aware of this crash. Unfortunately, I'm in midst of critical timeline of another SW dev project, but thought I would report this problem anyway.

I installed VirtualBox 5.0.16 on the OsX-Yosemite 10.10.5 system, (which, BTW, did also have Fusion 7.1.2 installed on it). It was after the VirtualBox installation that the kernel instabilities were introduced. The complete system lockups, where 2 of the 3 monitors would immediately go black, leaving desktop still showing on a 3rd monitor, on a 2nd GTX-980, were traced to VirtualBox as the culprit, by using your Un-Installer to remove VirtualBox and it's KEXT(s) from the system. There have been no more kernel instabilities since the complete VirtualBox removal.

It is important to note, that VirtualBox is causing OsX kernel instabilities, even when no virtual machines are running on the system. (No VMware VMs, nor VBox VMs). Thus you have a very insiduous problem going on within your KEXTs for OsX. That's because after 10 crashes, and inspecting the OsX System Logs, there are common messages produced in that log, which would give clue to the fact that VirtualBox had any problem, OR that any other OsX driver or subsystem had any problem. That's why I used the word "insidious". However, the impact can be devastating for those whom try to utilize VirtualBox for some type of production level system.

Hardware: CPU Hexacore 3970X (Extreme) Sabertooth X79 Mobo 64 GB DDR 2 NVidia GTX-780 Misc SSDs OsX 10.10.5 (Yosemite)

This instability ALSO exhibits itself on a MacMini (Apple) Mid 2013 with 4 core...also with VMware Fusion 7.1.2. Same symptoms, but needs more stressing of CPUs to exhibit the kernel crash. Multiple streams of audio processing were also involved in 2 crashes.

My intution: This instability seems to be related to some type of low level video processing, like potentially GPU raster operations or video buffer movements, possibly your code which is virtualizing the display (if that's possible without VMs running). The bug can occur with VMs running, but most of the crashes I experienced, were with NO VMs running.

Our resolution: For now...we have removed VirtualBox from every development system we have.

Sorry, that I do not currently have the bandwidth to aid/assist more in your tracking this down. I almost didn't report at all. I just don't have time for it...but I know the nature of this bug is very nasty.

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