Custom Query (16363 matches)
Results (1843 - 1845 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16631 | duplicate | Guest doesn't recognize if LAN network cable is pulled out | ||
| Description |
Host: Windows 10 x64 1 LAN adapter Intel I219-LM (cable disconnected) 1 Wireless adapter Intel AC 8260 (connected to Wi-Fi) Guest: Windows 10 x64 (new installed) 1 Bridged network to LAN adapter (cable connected in guest settings) 1 NAT network (cable connected in guest settings) Steps to reproduce the error: Host is started, start the guest Guest shows to network adapter, both connected One network (the bridged) shows "Unidentified network", one network (the NAT) is connected, the guest is online through this network. But the LAN cable is pulled out from the beginning but the guest doesn't recognize this. |
|||
| #16630 | duplicate | Guest doesn't recognize if LAN network cable is pulled out -> duplicate of #16631. | ||
| Description |
Host: Windows 10 x64 1 LAN adapter Intel I219-LM (cable disconnected) 1 Wireless adapter Intel AC 8260 (connected to Wi-Fi) Guest: Windows 10 x64 (new installed) 1 Bridged network to LAN adapter (cable connected in guest settings) 1 NAT network (cable connected in guest settings) Steps to reproduce the error: Host is started, start the guest Guest shows to network adapter, both connected One network (the bridged) shows "Unidentified network", one network (the NAT) is connected, the guest is online through this network. But the LAN cable is pulled out from the beginning but the guest doesn't recognize this. Full log is attached. |
|||
| #16629 | worksforme | Virtual Box 5.1.18 corrupted vdi drives on Windows 10 | ||
| Description |
I recently upgraded to VirtualBox 5.1.18r114002 and started a few Virtual Box Images which just worked fine under Virtual Box 5.0.32. However, after a restart the guest's Linux file system got corrupted. Too many multiply claimed blocks (fsock error and device no longer found). I also notices slower performance. HDD on the host is SATA. The guest uses a sata (AHCI) controller as well. After digging around, I saw that there was a similar problem in 2012, so I decided to use the IDE Controller on the guest instead of the SATA controller. Corruption of file system no longer occurs. Problem fixed with a work- around but still thought this bug should be reported as I lost a few hours getting this to work. |
|||

