VirtualBox

Opened 7 years ago

Closed 7 years ago

#16197 closed defect (invalid)

Network issues in VBox 5.1.8

Reported by: iwicfm666 Owned by:
Component: network/NAT Version: VirtualBox 5.1.8
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by Valery Ushakov)

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 r111957) which has the same problem.

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

Attachments (1)

Win7-Network-Problems.log (78.0 KB ) - added by iwicfm666 7 years ago.

Download all attachments as: .zip

Change History (7)

by iwicfm666, 7 years ago

Attachment: Win7-Network-Problems.log added

comment:1 by Valery Ushakov, 7 years ago

Component: networknetwork/NAT
Description: modified (diff)

comment:2 by Valery Ushakov, 7 years ago

The network configuration I asked for was the configuration of the guest, not that of the host.

All of these are completely frozen while the network is unavailable.

Do you mean when the network on the host is unavailable?

comment:3 by iwicfm666, 7 years ago

C:\>ifconfig -a

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Dawn010933L
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : attlocal.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : attlocal.net
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 08-00-27-5C-97-EE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4fb:53f7:1e9f:1f5c%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, November 20, 2016 6:50:49 PM
   Lease Expires . . . . . . . . . . : Tuesday, November 22, 2016 8:09:44 PM
   Default Gateway . . . . . . . . . : 10.0.2.2
   DHCP Server . . . . . . . . . . . : 10.0.2.2
   DHCPv6 IAID . . . . . . . . . . . : 386400295
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-A7-CD-29-08-00-27-6F-68-D4
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.dawnfoods.com:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
C:\>netstat -rn

===========================================================================
Interface List
 15...08 00 27 5c 97 ee ......Intel(R) PRO/1000 MT Network Connection
  1...........................Software Loopback Interface 1
 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.0.2.2        10.0.2.15     10
         10.0.2.0    255.255.255.0         On-link         10.0.2.15    266
        10.0.2.15  255.255.255.255         On-link         10.0.2.15    266
       10.0.2.255  255.255.255.255         On-link         10.0.2.15    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         10.0.2.15    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link         10.0.2.15    266
===========================================================================
Persistent Routes:
  None
  
IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 15    266 fe80::/64                On-link
 15    266 fe80::4fb:53f7:1e9f:1f5c/128
                                    On-link
  1    306 ff00::/8                 On-link
 15    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
Last edited 7 years ago by Valery Ushakov (previous) (diff)

comment:4 by Valery Ushakov, 7 years ago

Your log file lists a second, host-only adapter in the guest, but I don't see anything about it in the guest IP configuration you provided.

comment:5 by iwicfm666, 7 years ago

I did not notice that the host-only adapter was disabled in the guest. Enabling it fixed this issue in 5.1.9 r111957.

I'm guessing that the adapter was disabled during the removal of 5.1.8 or the installation of 5.1.9. I know I did not disable it manually.

Since the network resources being connected to are not on the host, it seems odd to me that enabling the host-only adapter would fix the problem, but it did.

Thanks for your assistance. As far as I am concerned, this ticket can be closed.

comment:6 by Valery Ushakov, 7 years ago

Resolution: invalid
Status: newclosed

Thanks for the quick update.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use