VirtualBox

Ticket #5666 (closed defect: fixed)

Opened 3 months ago

Last modified 3 months ago

close > save state > restart - leads to deactivating port forwards

Reported by: codemedic Assigned to:
Priority: major Component: network/NAT
Version: VirtualBox 3.1.0 Keywords: nar portforward linux
Cc: Guest type: Linux
Host type: Linux

Description

When I close a VM with port-forwards setup, and opt to save state. Then when I restart the VM, the portforwards are inaccessible from the Host machine.

Attachments

VBox.log.tar.bz (19.8 kB) - added by codemedic on 2009-12-05 12:04:59.
( tar + bz2 )ed log files

Change History

(follow-up: ↓ 2 ) 2009-12-04 16:59:10 changed by frank

Sounds like a duplicate of #5654.

(in reply to: ↑ 1 ) 2009-12-04 17:51:26 changed by codemedic

It isnt similar to #5654 Mine does work normally. The bug I reported gets triggered only after closing with "save state" option, which is then restarted from the saved state. If I shutdown and power off the VM normally; it does work on the next restart.

Sounds like some sort of skipped initialisation on waking up from saved state.

Replying to frank:

Sounds like a duplicate of #5654.

2009-12-04 18:03:45 changed by frank

It sounds like that bug anyway. Because in #5654, the user does static IP assignment in the guest, and after suspend / resume, you have a static IP assignment as well (because your guest still uses the old DHCP lease).

2009-12-04 18:28:26 changed by codemedic

In my case, I use DHCP, and before I closed the VM it was 10.0.2.15 and it remained the same when I restarted the VM. Same with the IP for the host machine from the VM ( 10.0.2.2 ). I am using NAT by the way!

When I restarted, outward connections from the VM is still working. Only the port-forwarding is broken.

2009-12-04 18:38:08 changed by codemedic

Sorry frank

You do have a case here.

My guest OS is Slackware 9.1 ( pain ... ) So once restarted, if I go in and do the below, it gets sorted.

ifconfig eth0 down ifconfig eth0 up dhcpcd -t 10 -h <hostname> -d eth0

(follow-up: ↓ 7 ) 2009-12-04 18:48:17 changed by codemedic

More precisely 

/sbin/ifconfig eth0 down
killall dhcpcd
/sbin/ifconfig eth0 up
/sbin/dhcpcd -t 10 -h dkorah-v3-uk -d eth0

(in reply to: ↑ 6 ; follow-up: ↓ 8 ) 2009-12-05 06:57:27 changed by Hachiman

Replying to codemedic: The way I'm doing fix for #5654 should fix this issue as well, because they have the same root. But could you please add a log file that will help me offer right bits to test.

(in reply to: ↑ 7 ; follow-up: ↓ 9 ) 2009-12-05 11:32:21 changed by codemedic

Replying to Hachiman:

Could you please be a bit more specific on the log file you are interested in. I am pretty new to VirtualBox

(in reply to: ↑ 8 ) 2009-12-05 11:38:48 changed by Hachiman

Replying to codemedic:

Replying to Hachiman: Could you please be a bit more specific on the log file you are interested in. I am pretty new to VirtualBox

sure, they're placed at ~/.VirtualBox/Machines/?[your-vm-name]/Logs I need any one of them. Thank you.

2009-12-05 12:04:59 changed by codemedic

  • attachment VBox.log.tar.bz added.

( tar + bz2 )ed log files

2009-12-05 12:56:29 changed by Hachiman

Thank you, will provide you debug bits for ubuntu 9.04/32 later today.

2009-12-06 10:42:35 changed by Hachiman

Could you please verify if http://www.virtualbox.org/download/testcase/VBoxDD.so.5666.debug.fix fixes problem for you? please replace VBoxDD.so in your installation directory with binary above. Please don't forget save original in the safe place.

2009-12-17 16:02:14 changed by frank

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


Contact – Privacy policy