Hi All,
I have Ubuntu desktop 12.04 (fully updated) with virtual box 4.2.14. I also have a VM - Ubuntu 12.04 server - fully updated. The VM is configured as a bridged network interface and has some servers - Apache, SSH, Squid etc.
The issue - if I upgrade to any 4.2 version of VirtualBox - the machine starts behaving almost as a NAT (I can not access the servers from another machine on the LAN but I can access them from the host).
Each time before trying to upgrade VirtualBox - I make a backup with clonezilla. So when I see that things go wrong - I revert with clonezilla and everything is fine again. However - I still can not upgrade to anything newer.
Today I had a different test - I export the VM to .OVA file as a backup. If I am to import this backup in VirtualBox as is - it works fine (again - no change to the virtualbox 4.2.14). However - if during the import I am to "re initialize" the network interface so I can have a new MAC address - the VM can not obtain an IP - the network interfaces can not be configured (needless to say - it is a bad state).
Guys - if you have seen something like this or have any idea how I can go around it - please help.
Ahead of time - for me this is a production machine - used heavily on daily bases so my tests would be limited and likely over the weekend. Never the less - I do appreciate help.
I haven't yet tried upgrade to virtual box 4.3
Thank you,
BB
I have Ubuntu desktop 12.04 (fully updated) with virtual box 4.2.14. I also have a VM - Ubuntu 12.04 server - fully updated. The VM is configured as a bridged network interface and has some servers - Apache, SSH, Squid etc.
The issue - if I upgrade to any 4.2 version of VirtualBox - the machine starts behaving almost as a NAT (I can not access the servers from another machine on the LAN but I can access them from the host).
Each time before trying to upgrade VirtualBox - I make a backup with clonezilla. So when I see that things go wrong - I revert with clonezilla and everything is fine again. However - I still can not upgrade to anything newer.
Today I had a different test - I export the VM to .OVA file as a backup. If I am to import this backup in VirtualBox as is - it works fine (again - no change to the virtualbox 4.2.14). However - if during the import I am to "re initialize" the network interface so I can have a new MAC address - the VM can not obtain an IP - the network interfaces can not be configured (needless to say - it is a bad state).
Guys - if you have seen something like this or have any idea how I can go around it - please help.
Ahead of time - for me this is a production machine - used heavily on daily bases so my tests would be limited and likely over the weekend. Never the less - I do appreciate help.
I haven't yet tried upgrade to virtual box 4.3
Thank you,
BB