virtualbox.org

Hello

just wanted to share this experience with you... in case you are spending frustrated nights like me on NAT port forwarding.

- upgraded VB from 2.0.6 to 2.1.0 for Windows Host/RedHat Guest.
- Learnt that NAT port forwarding does not work.
- Concluded issue is with the upgrade to VB 2.1
- Renamed the .VirtualBox folder on Windows for the sake of .VDI and .XML file backup
- downloaded VB 2.0.6 (thanks to Sun for providing downloads of olders)
- uninstalled VB 2.1
- had to physically delete the .VirtualBox folder again
- reboot host
- install VB 2.0.6
- create new virtual disk and machine with identical names and settings
- exit VB
- edit the new XML files VERY CAREFULLY ( you will have atleast two XML files to deal with) to make sure that your UUIDs match with the UUIDs of your backup machine (not the other way round). Do not attempt to copy paste the entire file.
- replace new (dummy VDI) with your old VDI
- Verify that machine is able to start/stop under 2.06
- rerun VBManage commands for port forwarding...since I used the same names, these did not have to be edited again
- moment of truth - check for SSH server using port forwarding works great (I use putty)

so ... it appears that the VDI files have not changed between 2.0.6 and 2.1 versions...which is why the VDI file created under 2.1 worked seamlessly with 2.0.6

... so long till we get release 2.1.1 with the fix

- D

I suspect that 2.1.2 will be out this month.