Custom Query (16363 matches)
Results (1492 - 1494 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13152 | obsolete | Host Windows Backgrounded on Multi-Monitor Setup | ||
| Description |
Problem: Host windows are automatically covered by maximised VBox windows. Details: I am using a setup with three screens on a Linux host and I have a Windows 7 guest running with three screens so that each physical screen contains one maximised VBox window. When I now cover one of the VBox windows on one screen with a window running on the host (maximised or not makes no difference), do something in or just click into a VBox window on another screen and then move the mouse back over the host window on the original screen, that screen is automatically put in the background and covered by the VBox window on that monitor. Software versions
Arch Linux Kernel 3.15.2 The problem isn't restricted to these specific versions and has occurred with previous versions and combinations thereof. It is also not specific to VBox 4.3.12, but occurs with every version starting with 4.2.20. 4.2.18 does not show this behaviour on the same machine with the same exact software versions as listed above. |
|||
| #3476 | fixed | Host networking Issues and potential fix | ||
| Description |
Not sure if this is the right place to post this but this is a potential fix for some of the hostif networking problems under windows on an os x host. When I install a windows XP guest on an OS X (10.5) host and select host interface networking with a virtual Intel 1000T server nic, the connection is flaky and tempermental. Certain sites connect and others don't. Local networking is hit and miss. If i go to the intel website and download the official drivers for the pro1000t complete with intels proset util etc, and install these in the guest vm, they replace the existing drivers installed by virtualbox and/or the xp install cd. After installing these drivers everything works perfectly. Driver link: http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=4275 Is it possible that there is a problem with the drivers installed by virtualbox and/or the xp installation media causing problems? Or does installing the official intel driver reset some other things? Anyway, thought you might be interested in this lead, as it's solved all my problems instantly... Cheers |
|||
| #6176 | fixed | Unable to change IP range of NAT network => Fixed in SVN | ||
| Description |
Hi 10.0.2.x currrently overlaps my work subnet. I would like to set the IP subnet to 172.23.24/24 but the step listed in the User Manual seem to have no effect. This is the command I am issuing to change the the subnet:
If I look in OpenSuse01.xml the first NIC shows: <Adapter slot="0" enabled="true" MACAddress="0800272F1D1A" cable="true" speed="0" type="Am79C973"> <NAT network="172.23.24/24"/> I also have UseHostResolver set: <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/UseHostResolver" value="1"/> If I powerdown the VM network="172.23.24/24" goes away. Posted in Windows Host Forum also: http://forums.virtualbox.org/viewtopic.php?f=6&t=27801 |
|||

