VirtualBox

Opened 11 years ago

Closed 8 years ago

#11755 closed defect (obsolete)

Networking breaks until guest reboot when sleeping host

Reported by: toobulkeh Owned by:
Component: network Version: VirtualBox 4.2.10
Keywords: Cc:
Guest type: Linux Host type: Mac OS X

Description

Using vagrant (https://github.com/mitchellh/vagrant/issues/1660).

Using Mountain Lion (osx 10.8) host and ubuntu VM guest, after the host's lid is shut and reopened (tested and verified with different IP / network) the guest can no longer connect to the internet without being restarted.

I will gather some logs I've searched and only found this 2 year old ticket that might be related: https://www.virtualbox.org/ticket/8577

but that was chalked up to a different guest OS.

Change History (7)

comment:1 by VirtualSean, 11 years ago

The same issue exists on Mountain lion as host and Win8 as guest

comment:2 by foobaz, 11 years ago

Same here, running VirtualBox 4.2.18 on osx 10.8.5, Ubuntu 12.04 guest.

I'd be glad to provide further info, since this is a daily occurrence for me and quite annoying.

Seems to occur on both using NAT and Bridged networking. Restarting the guest fixes the issue.

Running sudo ifdown eth0 hangs, and once that happens other commands like sudo shutdown -Ph now also hang. I have to power off the VM to restart it.

Not sure what helps in debugging this, but here is some information from the guest (using NAT):

[~] ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 08:00:27:2a:50:29 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
    inet6 fe80::a00:27ff:fe2a:5029/64 scope link 
       valid_lft forever preferred_lft forever

[~] ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 08:00:27:2a:50:29  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe2a:5029/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:232131 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180126 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:159445531 (159.4 MB)  TX bytes:32629286 (32.6 MB)


[~] route -nee
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface    MSS   Window irtt
0.0.0.0         10.0.2.2        0.0.0.0         UG    100    0        0 eth0     0     0      0
10.0.2.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0     0     0      0

On host:

[~] VBoxManage list bridgedifs     

Name:            en3: Display Ethernet
GUID:            00336e65-0000-4000-8000-a8206635deef
DHCP:            Disabled
IPAddress:       192.168.1.156
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: a8:20:66:35:de:ef
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-en3

Name:            en0: Wi-Fi (AirPort)
GUID:            00306e65-0000-4000-8000-14109fe57f5d
DHCP:            Disabled
IPAddress:       192.168.1.119
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 14:10:9f:e5:7f:5d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-en0

Name:            p2p0
GUID:            30703270-0000-4000-8000-06109fe57f5d
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 06:10:9f:e5:7f:5d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-p2p0

[~] VBoxManage showvminfo 4d5f2fbf-6ff9-4ec0-96b0-bc401dbd28a1 --details
Name:            current
Groups:          /
Guest OS:        Ubuntu (64 bit)
UUID:            4d5f2fbf-6ff9-4ec0-96b0-bc401dbd28a1
Config file:     /Users/m/VirtualBox VMs/current/current.vbox
Snapshot folder: /Users/m/VirtualBox VMs/current/Snapshots
Log folder:      /Users/m/VirtualBox VMs/current/Logs
Hardware UUID:   4d5f2fbf-6ff9-4ec0-96b0-bc401dbd28a1
Memory size:     5564MB
Page Fusion:     off
VRAM size:       64MB
CPU exec cap:    95%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  8
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): HardDisk
Boot Device (2): DVD
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             on
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
State:           running (since 2013-09-27T17:49:31.076000000)
Monitor count:   2
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0):            IDE Controller
Storage Controller Type (0):            PIIX3
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA Controller
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE Controller (0, 0): /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso (UUID: a83e60fc-cc89-42d2-ae56-bf09f127b3ae)
SATA Controller (0, 0): /Users/m/VirtualBox VMs/current/box-disk1.vmdk (UUID: bc0c8865-3e01-4d83-b9d1-10f3f8a1ed53)
NIC 1:           MAC: 0800272A5029, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0):   name = Rule 1, protocol = tcp, host ip = , host port = 2222, guest ip = , guest port = 22
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           disabled
Clipboard Mode:  Bidirectional
Drag'n'drop Mode:  disabled
Video mode:      1200x1920x32
VRDE:            disabled
USB:             disabled
EHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Guest:

Configured memory balloon size:      0 MB
OS type:                             Linux26_64
Additions run level:                 2
Additions version:                   4.2.18 r88780


Guest Facilities:

Facility "VirtualBox Base Driver": active/running (last update: 2013/09/25 23:36:52 UTC)
Facility "VirtualBox System Service": active/running (last update: 2013/09/25 23:37:36 UTC)
Facility "Seamless Mode": active/running (last update: 2013/09/27 18:47:43 UTC)
Facility "Graphics Mode": active/running (last update: 2013/09/27 18:47:43 UTC)
Last edited 11 years ago by foobaz (previous) (diff)

comment:3 by orangeBlueMesa, 10 years ago

Another way of bringing up the network interface again is to issue the /etc/init.d/networking restart command.

When you are experiencing your problems, can you ping an IP address? I.e. is this a DNS issue?

Have you tried configuring your guest with a DNSPROXY?

comment:4 by toobulkeh, 10 years ago

Sorry for the lack of communication, I don't get alerts on ticket comments and had forgotten where this was.

I am always ABLE to ping outwards to IP addresses, so this DOES appear to be a DNS issue.

I have a coworker who uses his VM on a Windows host and has the same problems (same guest).

Last edited 10 years ago by toobulkeh (previous) (diff)

comment:5 by toobulkeh, 10 years ago

A networking restart on the guest fixes the DNS issues. On my version of ubuntu in the guest I have to run sudo service networking restart

Any ideas on how to get past this in the future?

comment:6 by toobulkeh, 10 years ago

This is fixed with the recent 4.3.8 release, due to a similar bug here: https://www.virtualbox.org/ticket/12441

After provisioning the VM, you can type this to get around this bug:

VBoxManage modifyvm "VM name" --natdnshostresolver1 on

Thanks

comment:7 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use