VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1294 - 1296 of 16363)

Ticket Resolution Summary Owner Reporter
#1321 fixed shared drive protocol error when using "ar" command in linux guest Dirk Farin
Description

Using the "ar" command fails with a protocol error when using it on a shared drive:


farin@debian:/mnt/windata$ ar r lib.a control.o ar: unable to rename 'q.a' reason: Protocol error


Host is Windows XP, Guest is Linux Debian 2.6.22-3-686, shared drive is NTFS. VirtualBox version: 1.5.6 (but the same problem also occurred before)

#1322 obsolete Seamless: on secondary TwinView monitor not working -> Fixed in SVN John Bowen
Description

Under Ubuntu Gutsy using the NVIDIA 1.0-9639 driver (NVidia Quadro FX550 w/128MB), seamless mode is not working.

If I start the VM and move the VM window to the secondary monitor then enter seamless mode, the VM window disappears and no client windows are displayed. Pressing <Ctrl><Home> will allow me to disable seamless mode and restore the VM window to its original state.

If I move the VM back to the primary display and enter seamless mode, then everything works fine.

#1323 fixed VirtualBox OSX 1.5.51-r27946-beta3 does not allow large memories for its virtual machines Arthur van Leeuwen
Description

When I install VirtualBox OSX 1.5.51-r27946-beta3 on my MacBook (x86) running Mac OS X Leopard 10.5.2, I cannot start virtual machines with more than 1023 MB of memory. Trying to do so results in

Unknown error creating VM. VBox status code: -8 (VERR_NO_MEMORY).

Result Code: 0x80004005 Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

Changing the settings of a virtual machine to then use 1023 MB or less will allow me to start the virtual machine.

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