When you clone a virtual machine in VirtualBox, even with the option to generate new IDs, some network configurations may still be retained. This can lead to IP address conflicts, especially for static IP configurations. Here are some steps to resolve this issue:
1. Check the network configuration:
– Log into both machines and check their network configurations.
– Run `ip addr show` or `ifconfig` to see the IP addresses assigned to each interface.
2. For DHCP-assigned addresses:
– If the IP addresses are assigned via DHCP, try releasing and renewing the IP address on the cloned machine:
“`
sudo dhclient -r
sudo dhclient
“`
3. For static IP addresses:
– If static IPs are configured, you’ll need to manually change the IP address on one of the machines.
– Edit the network configuration file (usually located at `/etc/netplan/` for Ubuntu 18.04 and later).
– Change the IP address to a different one in the same subnet.
– Apply the changes with `sudo netplan apply`.
4. Check the MAC addresses:
– Ensure that the MAC addresses for the network adapters are different on both VMs.
– You can view and change MAC addresses in the VirtualBox settings for each VM.
5. Regenerate machine-id:
– Sometimes, the machine-id can cause conflicts. Try regenerating it on the cloned machine:
“`
sudo rm /etc/machine-id
sudo systemd-machine-id-setup
“`
6. Restart networking:
– After making changes, restart the networking service:
“`
sudo systemctl restart networking
“`
7. Reboot:
– If issues persist, try rebooting both VMs.
8. Check VirtualBox DHCP settings:
– In VirtualBox, go to File > Host Network Manager.
– Ensure that the DHCP server is enabled for your host-only adapter and has a sufficient IP range.
9. Consider using bridged networking:
– If you’re still having issues, consider using bridged networking instead of host-only, which might simplify IP assignment.
Remember to make these changes on only one of the machines to avoid further conflicts. After making these changes, both VMs should have unique IP addresses.
DevOPs Diary 