Downgrading to 5.0.16 fixes this network problem. The next problem that 5.1.8 introduced was video related. I use VirtualBox on a Dell Precision M6500 laptop, and while at work it is connected to an external monitor. I don't remember where or how I configured it, but when the external monitor is connected and I select Full Screen in VirtualBox, my Win7 VM snaps to the external monitor. That worked great in 5.0.16. I could even use xrandr to disable the external monitor, and the VM would switch between the external monitor and the laptop screen. Well, 5.1.8 not only broke that process, but every time the external monitor is enabled or disabled with xrandr, the VM would crash. Tomorrow I'll see whether or not downgrading to 5.0.16 also fixes that problem.
Tom On 11/14/2016 09:20 PM, Tom McArthur wrote: > I'm running 64bit VBOX 5.1.8 with a Win7 guest on a Mageia 5 host. > > After upgrading to 5.1.8, the virtual network will not time out in the > Win7 guest. In other words, any app that tries to access any > unavailable network resource freezes indefinitely. The only solution > is to disable the virtual network adapter, which immediately allows > the app to wake up and complain about the network being unavailable. > > Specific examples: an emulator for a mainframe, Notepad++ with a file > open that lives on the network at work, xplorer2 with a network folder > open. All of these are completely frozen while the network is > unavailable. > -- _____ |_ _|__ _ __ ___ | |/ _ \| '_ ` _ \ | | (_) | | | | | | |_|\___/|_| |_| |_| ------------------------------------------------------------------------------ _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
