VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1720 - 1722 of 16363)

Ticket Resolution Summary Owner Reporter
#10022 fixed [FIXED IN SVN] EMM386 does not automatically detect the available UMB regions t6ti00
Description

If MS-DOS virtual machine is created and EMM386.EXE is used, VirtualBox cannot automatically detect available UMB regions, so they are needed to setup manually to the CONFIG.SYS-file, like:

DEVICE=C:\WINDOWS\EMM386.EXE RAM ON NOEMS FRAME=NONE I=E000-EFFF I=B000-B7FF

On the contrary, Microsoft Virtual PC 2007 can do this. Command

DEVICE=C:\WINDOWS\EMM386.EXE NOEMS

is enough and UMB regions will be detected.

This is not a big problem for advanced users who are able to do a manual edit and people who are running only small programs on MS-DOS virtual machines may not need it at all. It can be confusing for the others. I do not consider this is a bug, so let's say that this is a feature request.

Thanks.

#11713 obsolete Realtek, VLAN, Bridge, interfaces disabled t3mp
Description

I'm have "Realtek PCIe GBE Family Controller" LAN card, on Host machine win7 x64 Driver ver: 6.250.908.2011
I'm create VLAN by "Realtek Ethernet Diagnostic Utility" ver: 2.0.1.9 in host machine. VLAN's create by new virtual interfaces in system aka "Virtual NIC". Before the update i used VirtualBox-4.2.8-83876, and all work's fine. To use the VLAN in linux i'm created a bridge between the interfaces in Linux and "native(not Virtual)" interface to the host machine. In Linux created VLAN.
But after the upgrade, if the settings of the native interface on the host machine to enable the use of the bridge, all VLAN interfaces are disabled, and nothing work((, without the possibility turn on, if we remove the bridge interfaces are automatically enabled, and work normal.
As a temporary solution, I create a bridge between the vlan interface on the host and the guest machine, but it is inconvenient and surprising number of interfaces in the machine gostovoy limited.
Update to version 4.2.12 NO solves the problem.

#13649 obsolete Vbox 4.3.20 Windows x64 and Symantec End Point Protection 12.1.4112.4156 BSOD t3mp
Description

BSOD at start any VM.

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