On Thu, Nov 22, 2012 at 09:48:19AM +0200, Livnat Peer wrote: > On 21/11/12 22:53, Andrew Cathrow wrote: > > > > > > ----- Original Message ----- > >> From: "Moti Asayag" <[email protected]> > >> To: [email protected] > >> Sent: Wednesday, November 21, 2012 12:36:58 PM > >> Subject: [Engine-devel] Report vNic Implementation Details > >> > >> Hi all, > >> > >> This is a proposal for reporting the vNic implementation details as > >> reported by the guest agent per each vNic. > >> > >> Please review the wiki and add your comments. > > > > > > While we're making the change is there anything else we'd want to report - > > MTU, MAC (since a user might try to override), etc ? > > > > About the MAC address - the engine uses the MAC address to correlate > between the guest-agent report and the VNICs defined in the engine. If > the GA reports a MAC that the engine does not recognize the engine can > not associate it with a VNIC. > What the engine can do is to issue a warning to the audit log in case > such a mismatch is recognized, Is that good enough?
Oops, I've been scooped... The guest may also report devices with unknown MAC (bridge, vlan, dummy, etc...), which is not a reason for alarm. If the configured MAC is completely missing, a warning seems valid. > > About MTU - It is not being reported by the guest agent ATM (while IPv4 > IPv6 and MAC are), If we'd like to have it I can open RFE for the GA to > report additional fields. _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
