Port forwarding for SSH does not work after restoring a snapshot in running state => fixed in SVN/next 7.0.x maintenance

[Osprey]

Steps to reproduce:

• Configure port forwarding rule for some port on host to port 22 on virtual machine (used for SSH)
• Establish SSH session to host port that is forwarded: it is working
• take a snapshot of running VM
• restore a snapshot of running VM
• Try to establish SSH session to host port that is forwarded: connection just hangs and it does not get established (BUG)
• Restart VM and SSH can be established again

The same functionality was working on Virtualbox 6.x with the same VM.

[aeichner]

This is not reproducible here. Please attach a log of the affected VM from the working state (after the snapshot was taken) and non-working state (when the snapshot was restored) and reopen this ticket.

[Osprey]

EDIT: Deleted. Will provide a new update.

[Osprey]

I am uploading a set of logs after the snapshot was taken and when the snapshot was restored (SSH not working after restoring, I think that general port forwarding is not working).

[aeichner]

Thanks for the logs, it looks like one of the requirements is to not restore the VM immediately but you have to wait for a while to make it break. Basically all network related activity seems to be broken until the VM is rebooted. Can you confirm that trying to reach an external host from within the VM doesn't work for you as well when you restored the state?

[blue]

I am having the same issue (can confirm it) with 7.0.4; actually no network seems to be available at all - it is not possible to access the outer network from within the VM (e.g. ping 8.8.8.8) and also none of the port forwardings seem to work anymore (I never experienced similar problems with VBox 6.x); my current (only) solution seems to be to shutdown the VM and start it up again (afterwards networking works fine again).

[aeichner]

So I'm able to reproduce your issue then which is great because it makes debugging it much easier. As a temporary workaround you can try to switch the network adapter from virtio-net to e1000, that one shouldn't exhibit this behavior.

[blue]

Thanks for the confirmation and workaround (I'll try that); now I also understand why not so many other people are experiencing this issue - probably not many did switch to virtio-net (actually the reason I did was that the performance seemed to be much better with it).

[Osprey]

I can confirm that network does not seem to work at all until VM restart. This issue was introduced in 7.x because it was not present in 6.x.

[Osprey]

And I can confirm there is no issue if I switch network adapter.

[Larry Finger]

I can confirm that this is a real bug with virtio-dev. I can also confirm that it is new with 7.0.X. Versions 6.1.X do not show the problem.

[aeichner]

Thanks for the report, this will be fixed in the next 7.0.x maintenance release.

[galitsyn]

Hello,

We just released VirtualBox 7.0.6. This issue should be fixed in this version. You can download it from https://www.virtualbox.org/wiki/Downloads.