VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (397 - 399 of 16363)

Ticket Resolution Summary Owner Reporter
#260 fixed VBox does not detect when network moves to different NIC -> fixed in SVN/1.5.4 asrinivasan
Description

On my laptop, my host OS is FC6, my guest OS is XP. I start vbox at home when I'm already connected to my home LAN via Wifi (eth1). I suspend my laptop, bring it to work, plug into the wired LAN via eth0. XP is not able to see the network. I would expect that no matter which configured NIC I'm using, whether its up or down when vbox is started, the host routes will be used by vbox.

-andre.

#261 fixed VirtualBox starts on an incorrect X-Server -> fixed in SVN/1.5.0 Technologov
Description

Platform: openSUSE Linux 10.2, VBox 1.3.8

When I have two X-servers running, VirtualBox Manager starts where I ask it to start, but the VMs are always started on the first X server (that is: display :0), even if they are launched from second X-server by VirtualBox Manager.

to reproduce:

  1. KDE Start Menu->Start New Session (or startx -- :1) to start a 2nd X-Server
  1. Try running some VBox VMs on the 2nd X-Server.
#262 fixed Kernel X Modules - external source tarball laxathom
Description

Hi all,

Does it plan to provide an external xgraphic and xmouse kernel module driver source tarball like vboxdrv.ko (vbox-kernel-module-driver.src.tar.bz2) ?

this will avoid to rebuild all the main source tarball to just update the kernel module for the updated kernel release.

For now the way to avoid a full rebuild it's to: pushd %{_builddir}/%{package_name}-%{version}/src/VBox/Additions then do kmk on related Makefile contained folder to build them alone.

I can provide a script kernel X module install for Fedora Core system is someone need it.

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