VirtualBox

Ticket #4567 (closed defect: fixed)

Opened 8 months ago

Last modified 5 months ago

Internal network stops working after suspend

Reported by: greenrd Assigned to:
Priority: major Component: network
Version: VirtualBox 3.0.2 Keywords:
Cc: Guest type: Linux
Host type: Mac OS X

Description

This is with OSE 3.0.2 with two Linux guests on an internal network. After suspending the host, the guests also suspend as expected, and automatically resume, and when I try to use the internal network, it doesn't work. Cannot connect to the other machine and pings fail. Bringing down and up the interface on both machines does not change anything.

Each guest has 2 network cards; all 4 are the same type. On one of the guests, the internal networking is attached to the first network card; on the other, it's attached to the second. The other network cards are NAT. The NAT network cards are both configured to do DNS masquerading.

Attachments

VBox.log (44.8 kB) - added by greenrd on 2009-07-18 13:06:49.
Log file for first machine
VBox.2.log (38.2 kB) - added by greenrd on 2009-07-18 13:07:56.
Log file for second machine

Change History

2009-07-18 13:06:49 changed by greenrd

  • attachment VBox.log added.

Log file for first machine

2009-07-18 13:07:56 changed by greenrd

  • attachment VBox.2.log added.

Log file for second machine

2009-07-21 17:16:29 changed by greenrd

It turns out it doesn't require a suspend - it seems to be caused by the network being left almost idle for a period of time (although there may be some operating system packets transmitted, so I don't know if it's completely idle).

2009-09-17 11:30:00 changed by greenrd

This still happens on VirtualBox 3.0.6.

2009-10-27 17:53:18 changed by eskild

I see the same problem with suspend/resume on 3.0.6. Host: WinXP; guest: Fedora Core 10 with e1000 NIC.

2009-10-27 18:40:46 changed by greenrd

I am no longer experiencing this bug - I think due to upgrading my guests.

2009-10-27 20:29:12 changed by frank

eskild, I'm quite sure that this bug was fixed in 3.0.8, please verify.

2009-10-29 16:50:24 changed by frank

  • status changed from new to closed.
  • resolution set to fixed.

Please reopen if this problem persists, 3.0.10 is about to be released.


ContactPrivacy policy