On Fri, Sep 23, 2022 at 11:53:22AM +0800, ho...@yusur.tech wrote: > On Thu, 22 Sep 2022 09:34:41 +0800 Jason Wang<jasow...@redhat.com> wrote: > > > >On Thu, Sep 22, 2022 at 1:58 AM Raphael Norwitz > ><raphael.norw...@nutanix.com> wrote: > >> > >> If I read your response on the other thread correctly, this change is > intended > >> > >> to prioritize the MAC address exposed by DPDK over the one provided by > the > >> > >> QEMU command line? Sounds reasonable in principle, but I would get > confirmation > >> > >> from vDPA/vhost-net maintainers. > > >I think the best way is to (and it seems easier) > > >1) have the management layer to make sure the mac came from cli > >matches the underlayer vDPA > > Agreed, that's no problem. > > >2) having a sanity check and fail the device initialization if they don't > match > > However, one MAC address for integrity check is from the cli, and the > other > MAC address is from the vDPA device, > How to get it? > > The current situation is if MAC came from cli don't match the underlayer > vDPA, the virtual machine can still start without any hints. > > Thanks > >
Let me ask then, why are you supplying the incorrect MAC on the cli? -- MST