VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (301 - 303 of 16363)

Ticket Resolution Summary Owner Reporter
#3302 obsolete d-link Bluetooth USB Adapter - DBT-120 Spock
Description

I want to connect my DBT-120 to the VM. But it does not work. It has also no name --> unbekanntes Gerät 0A12:0001 [0443]

Product Link:

http://www.d-link.de/?go=jN7uAYLx/oIJaWVdDbgYU93ygJVYLelXSNvhLPG3yV3oWI58kP98f8p8Nqtn6TU6VHqqnHtB85pJVJ23gKftOQ5A8ruEaoqgXYP+pmsMmdsPTbhHNpbF3RLA5TSEJcbefr8r/Ep+/J4S7CoTftygjm/1giFdsmyuGh4=

#3309 obsolete HostMemoryLow Alexandre Arruda
Description

I have a Centos 5 Host and I install a Debian Lenny Guest. It's a 4 GB RAM/Dual Xeon Server. I create the VM with only 200 MB and when I do simple tasks (like an apt-get), I got this error.

Bellow, the tail of VBox.log and the free command. I don't understand why I have a lot of buffers and cached memory (2.5 MB) and the system can't allocate this. Have I do tune any sysctl parameters to coorect this ???

00:00:24.834 PCNet#0: Init: ss32=1 GCRDRA=0x0c11b000[32] GCTDRA=0x0c11a000[16]
00:00:27.355 NAT: DHCP offered IP address 10.0.2.15
00:00:27.691 NAT: IPv6 not supported
00:02:55.969 pgmr3PhysGrowRange: out of memory. pause until the user resumes execution.
00:02:55.969 Changing the VM state from 'RUNNING' to 'SUSPENDED'.
00:02:57.050 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"

server1@server1 [~/.VirtualBox/Machines/debian]# free
             total       used       free     shared    buffers     cached
Mem:       4152072    4001504     150568          0     410616    2522284
-/+ buffers/cache:    1068604    3083468
Swap:      2096472      20672    2075800

#3313 obsolete Booting from Fedora Install CD, then choosing 'Local Hard Disk' results in Fatal Error kookyman
Description

I am using Vista as my host currently, however I remember this bug happening on XP hosts as well. Guests were both Linux and Windows.

I reproduced this using installation CD images for Fedora 7, Fedora 9, Fedora 10. This is most likely to happen if you install Fedora, and leave the DVD image mounted.

Procedure: Install guest OS of your choice in your virtual machine, (I used Fedora 10). Boot Virtual Machine with Fedora Install CD still mounted, as CD is higher in boot order, the DVD will begin the boot. One of the options is to "Boot from local hard disk." Choose that.

Expected Result: Begin booting installed OS on the hard drive.

Observed Result: (Direct output) "Booting from local disk... FATAL: INIT18: BOOT FAILURE"

Note: I know this may not necessarily be a bug in VBoxes handling, it may be that Fedora is using a obscure way to boot the local drive, but a FATAL error shouldn't be thrown either way. Additionally, it was mentioned in the vbox chat room I believe that someone experienced this error with another disk.

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