Re: [VBox-users] Trouble migrating a VM

[Freek de K. <f.d...@gm...>]

On woensdag 29 februari 2012 23:41:08 Alan M. Evans wrote:
> 
> On the old host:
> 
>         [root@oldhost]# VBoxManage list bridgedifs
>         Name:            eth0
>         GUID:            30687465-0000-4000-8000-bcaec5b2407e
>         Dhcp:            Disabled
>         IPAddress:       192.168.0.35
>         NetworkMask:     255.255.255.0
>         IPV6Address:     fe80:0000:0000:0000:beae:c5ff:feb2:407e
>         IPV6NetworkMaskPrefixLength: 64
>         HardwareAddress: bc:ae:c5:b2:40:7e
>         MediumType:      Ethernet
>         Status:          Up
>         VBoxNetworkName: HostInterfaceNetworking-eth0
> 
> On the new host:
> 
>         [root@newhost elan]# VBoxManage list bridgedifs
>         Name:            eth0
>         GUID:            30687465-0000-4000-8000-0019b9fddfac
>         Dhcp:            Disabled
>         IPAddress:       192.168.0.91
>         NetworkMask:     255.255.255.0
>         IPV6Address:     fe80:0000:0000:0000:0219:b9ff:fefd:dfac
>         IPV6NetworkMaskPrefixLength: 64
>         HardwareAddress: 00:19:b9:fd:df:ac
>         MediumType:      Ethernet
>         Status:          Up
>         VBoxNetworkName: HostInterfaceNetworking-eth0
> 
The problem might be that the guest is not able to associate the parameters 
for the network device with the changed MAC address of the new VM. So try to 
change the MAC address (HardwareAddress) above to the same address as on the 
old host.

If you want both guest systems to be active on the same network, you may 
temporarily add a second network interface on the old host to the guest with 
the address on the new host and configure the associated interface in the 
guest. After that you remove the second network interface in the old host, now 
the parameters for that interface are still present in the guest. So when you 
start the guest in the new host, that second interface will be active and will 
give you access to that system.

-- 
fr.gr.

Freek de Kruijf