Vmconverter Linux

[duxbuz]

Hi,

Am very pleased that I managed to convert one of my linux machines using vm converter. It was 75gb and it did it very quickly.

Only issue is that network card. From reading on google it seems to be because of mac address.

Not too sure how to fix this.

Strangely it seems to have changed eth0 to eth1, it works but i have some weird stuff going on i dont really understand.

Ifconfig:
eth1 Link encap:Ethernet HWaddr 00:0c:29:a9:9d:a2
inet addr:x.x.x.x Bcast:x.x.x.x Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fea9:9da2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:56010 errors:0 dropped:0 overruns:0 frame:0
TX packets:21513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6675545 (6.6 MB) TX bytes:3726403 (3.7 MB)
Interrupt:18 Base address:0x2000


when i run dmesg | grep eth, I get
[ 3.702564] eth0: registered as PCnet/PCI II 79C970A
[ 3.703218] eth1: registered as PCnet/PCI II 79C970A
[ 3.717896] Driver 'sd' needs updating - please use bus_type methods
[ 4.139348] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection

I originally had on physical server:

ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:ba:be:95:1d
inet addr:x.x.x.x Bcast:x.x.x.x Mask:255.255.255.0
inet6 addr: fe80::250:baff:febe:951d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:159 errors:0 dropped:0 overruns:0 frame:0
TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15036 (15.0 KB) TX bytes:11509 (11.5 KB)
Interrupt:22 Base address:0xa000

dmesg | grep eth
[ 4.061442] eth0: RealTek RTL8139 at 0xa000, 00:50:ba:be:95:1d, IRQ 22
[ 4.061447] eth0: Identified 8139 chip type 'RTL-8139C'
[ 5.725590] Driver 'sd' needs updating - please use bus_type methods
[ 5.726183] sda:<4>Driver 'sr' needs updating - please use bus_type methods
[ 142.460569] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 153.750045] eth0: no IPv6 routers present

I do have 2 NICS in this box, and i thought it was using the second nic.... but actually thats not got a network cable in it so its still using the same one.

Anyone have any pointers before i virtulise the 'live' Linux proxy server

Thanks

[Duke]

I've had something kind of similar before, in the end I told the VMware Converter to run a 'reconfigure' after it had converted the machine (it'll need to start up and reboot to do this) and ensure that VMware Tools are installed. After that things tend to run fine on eth1, and eth0 is just there as an old backup config. If you're running a Red Hat / Fedora / Centos variant, you can just run 'setup' from the command line, go to network adapters and rename the NIC if you want.

Chris