Custom Query (16363 matches)
Results (2041 - 2043 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16197 | invalid | Network issues in VBox 5.1.8 | ||
| Description |
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 uncheck/deactivate the network device via Devices > Network > Adapter 1, which immediately allows the app to wake up and complain about the network being unavailable. Downgrading to 5.0.16 fixes this network problem.
I also tested this on the latest build (5.1.9 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. $ ifconfig -a
eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 5c:f9:dd:5c:25:98 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 703 bytes 67338 (65.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 703 bytes 67338 (65.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.56.1 netmask 255.255.255.0 broadcast 192.168.56.255
inet6 fe80::800:27ff:fe00:0 prefixlen 64 scopeid 0x20<link>
ether 0a:00:27:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14 bytes 1187 (1.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp12s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.64 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::221:6aff:fec5:749a prefixlen 64 scopeid 0x20<link>
inet6 2602:30a:2c54:2e20:221:6aff:fec5:749a prefixlen 64 scopeid 0x0<global>
ether 00:21:6a:c5:74:9a txqueuelen 1000 (Ethernet)
RX packets 15944 bytes 10006776 (9.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14417 bytes 3582297 (3.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 wlp12s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp12s0 192.168.56.0 0.0.0.0 255.255.255.0 U 0 0 0 vboxnet0 |
|||
| #16196 | obsolete | Cannot start VMs in Windows 10 x64 | ||
| Description |
After initial install of virtual box I was able to create and run a red hat VM. After a restart of the PC, I was not able to start the red hat VM, nor any others (I tried creating Ubuntu and Win7 VMs as a test). When attempting to start one, the following error occurs: "supR3HardenedDllNotificationCallback: NtCreateFile failed on 'C:\windows\System32\umppc4702.dll' / '\??\C:windows/System32\umppc4702.dll': 0xc0000034 (rc=-225) Please try reinstalling Virtual Box. where: supR3HardenedWinCheckChild what: 5 VERR-INTERNAL_ERROR (-225) - Internal error - this should never happen." Reinstalling virtual box/restarting the PC had no impact. Running as administrator had no impact. Both 5.1.8 and the 5.1.9 test build exhibit the same issue. Host is Windows 10 Enterprise 64 bit. |
|||
| #16195 | fixed | VBox crashes caused by video | ||
| Description |
I use VirtualBox on a Dell Precision M6500 laptop. Host is Mageia 5, guest is Win7. While at work my laptop 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. I just tested this with the latest build (5.1.9-111957), which has the same problem. My log is attached. Please let me know if I need to recreate the log with debugging options enabled. |
|||

