#5666 closed defect (fixed)
close > save state > restart - leads to deactivating port forwards
Reported by: | DK | Owned by: | |
---|---|---|---|
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 (1)
Change History (13)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
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.
comment:3 by , 15 years ago
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).
comment:4 by , 15 years ago
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.
comment:5 by , 15 years ago
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 comment:6 by , 15 years ago
More precisely
/sbin/ifconfig eth0 down killall dhcpcd /sbin/ifconfig eth0 up /sbin/dhcpcd -t 10 -h dkorah-v3-uk -d eth0
follow-up: 8 comment:7 by , 15 years ago
follow-up: 9 comment:8 by , 15 years ago
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
comment:9 by , 15 years ago
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.
comment:11 by , 15 years ago
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.
comment:12 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Sounds like a duplicate of #5654.