On Tue, Feb 27, 2018 at 04:43:15PM +0100, Michal Skrivanek wrote: > > We're passing the source MAC through into the OVF (see rasd:MACAddress > > and v2v/create_ovf.ml). Does oVirt use it? > > no. Exactly for the reason Tomas mentioned, the MAC spaces are > almost always entirely different and we reallocate a different MAC > every time
That's oVirt's decision, and we can work around it as described by erasing MAC addresses when the target is oVirt. The patch will need to be more complete because it must at the very least deal with NetworkManager & Windows. However ... I'm pretty sure this is going to cause problems for oVirt. It will mean in some circumstances that ethernet ports are swapped (which can be serious - you don't want your public and private LANs to get swapped over, although usually the result will be failure rather than the guest sending out private information over a public port). Also you'll have problems which anything which keys off the MAC address to derive system-unique numbers, like license servers. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
