VMware Workstation 10 - Redmine VM network interfaces wont come up
I have a major problem.
I have a remine VM installed and the Nic is configured in vMware for bridging network.
All was working but as soon as I shutdown the machine "Sudo shutdown -h now" and restarted the machine,I can seem to get a network connection for my redmine VM, I have tried everything restarted the Host machine and also run CMD and restarted via cmd
net stop vmnetbridge
net start vmnetbridge
and then again did a Sudo shutdown -h now and started the Redmine VM up again but still no comms.
This is freaking me out as all my confidential projects are on this redmine.
Any help would be greatly appreciated to get this working again please!
I have a remine VM installed and the Nic is configured in vMware for bridging network.
All was working but as soon as I shutdown the machine "Sudo shutdown -h now" and restarted the machine,I can seem to get a network connection for my redmine VM, I have tried everything restarted the Host machine and also run CMD and restarted via cmd
net stop vmnetbridge
net start vmnetbridge
and then again did a Sudo shutdown -h now and started the Redmine VM up again but still no comms.
This is freaking me out as all my confidential projects are on this redmine.
Any help would be greatly appreciated to get this working again please!
ASKER
@gheist
OK sure correct me please so do I do:
sudo -i
nano /etc/udev/rules.d/70-persi
and then look for mac addresses and just remove the mac addresses there???
thank you so much for your assitance
OK sure correct me please so do I do:
sudo -i
nano /etc/udev/rules.d/70-persi
and then look for mac addresses and just remove the mac addresses there???
thank you so much for your assitance
That's correct....
you may find in your VM, you may have two network interfaces
eth0 and eth1.
But remove the mac address, and when the rules are re-generated, your actual mac address of your VM will be included.
This is a known issue with "cloning" Linux VMs.
you may find in your VM, you may have two network interfaces
eth0 and eth1.
But remove the mac address, and when the rules are re-generated, your actual mac address of your VM will be included.
This is a known issue with "cloning" Linux VMs.
ASKER
I only have one vm Nic ,
I just did a rm /etc/udev/rules.d/70-persi
first backed up file though
Afterwards I did a /etc/init.d/networking restart
in VM WS
under the redmine VM Settings>NIc is set to Bridged:....... and also Replicate physical network connection state
However still no IP address for my Redmine VM
I just did a rm /etc/udev/rules.d/70-persi
first backed up file though
Afterwards I did a /etc/init.d/networking restart
in VM WS
under the redmine VM Settings>NIc is set to Bridged:....... and also Replicate physical network connection state
However still no IP address for my Redmine VM
can you check the mac address of the VM and VM Settings are the same ?
Can you also test NAT ?
Can you also test NAT ?
ASKER
Did you select NAT in the VM network settings ?
ASKER
no bridge, its always worked with bridge settings though and the cmd restart has always worked , just happened this morning when I shut the Redmine VM down and then started it up??
I just want to check if you get an IP Address in NAT mode
ASKER
I get an IP in NAT mode weird but its not on the same subnet as I am working on now
ie 10.0.0.x is current LAN
ip from VM is 192.168.0.x
Seems we half way there, any suggestions
ie 10.0.0.x is current LAN
ip from VM is 192.168.0.x
Seems we half way there, any suggestions
The IP Address, from NAT is from VMware Workstation internal DHCP server.....
this IP Address is NATTED to your Internal LAN (10.0.0.x)
So this proves the VM is working correctly.....e.g. mac address can get a DHCP IP Address....
so do you have a DHCP serve on your LAN ?
It seems Bridged Mode, is not working or receiving DHCP ip addres....
this IP Address is NATTED to your Internal LAN (10.0.0.x)
So this proves the VM is working correctly.....e.g. mac address can get a DHCP IP Address....
so do you have a DHCP serve on your LAN ?
It seems Bridged Mode, is not working or receiving DHCP ip addres....
ASKER
I do have a DHCP Server on my LAN yes
Do you have more than one nic in the host?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Your comments were right how ever this didnt work as I had to do an ifconfig eth0 mac x.x.x.x and then do sudo reboot .After the reboot it picked up an IP Address again
You can set fixed MAC via vmware too.
Though best is to just clear stored MAC ans dtart new life
Imagine person at next desk deploying same VM with same MAC....
Though best is to just clear stored MAC ans dtart new life
Imagine person at next desk deploying same VM with same MAC....
ASKER
OK cool mind explain to me where in vMware I set the fixed MAC?
Edit the VMX file.
ASKER
legend! will this propagate though to my linux vm?
Yes, the udev net rules rules will pick it up, and add it to the
70-persistent-net.rules
this is what causes the issue, because at VM startup, the MAC address is written to the file.
If the MAC Address of the VM mismatches the MAC address in the file, networking does not work too well!
70-persistent-net.rules
this is what causes the issue, because at VM startup, the MAC address is written to the file.
If the MAC Address of the VM mismatches the MAC address in the file, networking does not work too well!
ASKER
Thanks mate,
As I said Legend as I have been battling with this issue contantly
As I said Legend as I have been battling with this issue contantly
It is just one time action - boot vm in single mode ONCE AFTER MAC CHANGE
Delete udev rules file
Delete MAC from ifcfg
and reboot like nothing happened.
Delete udev rules file
Delete MAC from ifcfg
and reboot like nothing happened.
You need to delete permanent udev rules (/etc/udev/rules.d/70-*) and remove MAC addresses from network scripts (Fedore/Rhel)