On donderdag 1 maart 2012 01:09:08 Alan M. Evans wrote: > On Thu, 2012-03-01 at 00:01 +0100, Freek de Kruijf wrote: > > 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. > > Thanks for the quick reply. > > Please forgive my further questions. I'm just trying to understand you > here. You are suggesting that I bind the MAC of the (hardware) network > card in the new host to the same as the network card on the old host? > (That's what the HardwareAddress entry is: the hardware MAC on the > host.)
I had the same problem and this was the solution. The point in my case is that udev in the guest associates the Ethernet interface using the MAC address of that interface with the parameters like IP address (fixed or using DHCP etc.) of the stored configuration. If it finds a new MAC address it does not associate and the Ethernet interface is left without any configuration. If the interface name is eth0 than the new interface will be eth1. So you will not be able to connect to that guest through the network because the virtual hardware of eth0 is not there and eth1 does not have a configuration. > Forgive my skepticism, but if that's the problem then how does migrating > a VM *ever* work? > > Anyway, certainly nothing in the guest.vbox file refers to the host's > MAC, either on the old or new host. It is not the MAC address of the host, it is the MAC address of the guest. > Old host guest.vbox snippet: > > <Adapter slot="0" enabled="true" MACAddress="080027943BC1" > cable="true" speed="0" type="82540EM"> <DisabledModes> > <NAT> > <DNS pass-domain="true" use-proxy="false" > use-host-resolver="false"/> <Alias logging="false" proxy-only="false" > use-same-ports="false"/> </NAT> > </DisabledModes> > <BridgedInterface name="eth0"/> > </Adapter> > > New host guest.vbox snippet: > > <Adapter slot="0" enabled="true" MACAddress="0800271626A0" change "0800271626A0" to "080027943BC1" and try again. Just make sure the old guest is not active on the same network. > cable="true" speed="0" type="82540EM"> <DisabledModes> > <NAT> > <DNS pass-domain="true" use-proxy="false" > use-host-resolver="false"/> <Alias logging="false" proxy-only="false" > use-same-ports="false"/> </NAT> > </DisabledModes> > <BridgedInterface name="eth0"/> > </Adapter> > > Both only refer to "eth0". The MACAddress in each is, of course, > virtual, and only for the guest. > > It just seems really unlikely to me that it should be necessary to match > the host systems hardware MACs. In any case, I would have to try it > sometime after hours, since the old host runs several services besides > the VM. And while the VM would only run on one host at a time, both > hosts must be up simultaneously for the time being. I don't think it > would be a good idea to be screwing with the network interfaces and MAC > addresses on the old host while most of the building is trying to use > the server. > > -Alan > > > > --------------------------------------------------------------------------- > --- Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > VBox-users-community mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/vbox-users-community -- fr.gr. Freek de Kruijf ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
