Results 1 to 3 of 3
Hi folks,
host - Ubuntu 1004 64 bit
new vm - Ubuntu 1004 64 bit (cloned on another VM)
After creating this new vm it starts/works
Edit /etc/network/interface to change ...
- 08-08-2010 #1Linux Guru
- Join Date
- Sep 2004
- Posts
- 1,546
VM can't ping host and Internet
Hi folks,
host - Ubuntu 1004 64 bit
new vm - Ubuntu 1004 64 bit (cloned on another VM)
After creating this new vm it starts/works
Edit /etc/network/interface to change the IP address
Edit /etc/hosts and /etc/hostname to change hostname
reboot vm
$ hostname
showing the correct/new hostname
But vm can't ping host nor Internet. Nor host can ping the new vm.
This is NOT my first time cloning vm. There are many cloned vm running on this VBox. I have spent more than an hour unable to solve the problem. Please help.
/etc/resolv.conf
is correct showing the DNS IP of ISP
Edit:
The browser, Firefox, can connect Internet. On terminal it can ping Internet but not host/gateway
B.R.
satimisLast edited by satimis; 08-08-2010 at 03:28 AM.
- 08-09-2010 #2Linux Newbie
- Join Date
- Jul 2005
- Location
- Australia (Down Under)
- Posts
- 141
I personally would check the following:
- Make sure that the Virtual Machines network adapter is set to the correct mode, )(most likely "Bridged connection")
- check that the netmask is correct
- set IP address to DHCp and once obtained an IP see if it works then. (Obviously you will need a DHCP Server on the network to do this)
Hope that helpsLinux is the OS of tomorrow, Here today!!
- 08-09-2010 #3Linux Guru
- Join Date
- Sep 2004
- Posts
- 1,546
Hi,
Thanks for your advice.
Problem solved already. I missed one important step.
On VM edit /etc/udev/rules.d/70-persistent-net.rules
changing the line;as;Code:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:ba:ae:16", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
Code:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:ba:ae:16", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
"eth1" to "eth0"
Reboot VM, all problem gone.
During cloning, VBoxManage assigned Name="eth1" in the cloned VM because the
original VM already taking up Name="eth0" on its MAC address.
I made lot of VM cloning. Recently only on Windows therefore I forgot this
important step. I have been wondering a step missed but at the beginning unable to recall.
Anyway, thanks again for your advice.
B.R.
satimis


Reply With Quote
