Re: nested vms and nested macvtaps

[jsl6uy js16uy <js16uy@xxxxxxxxx>]

Thanks much sir

Ease I think mainly
adding a macvtap is pretty quick, performant and works. And last but definitely not least, ignorance of other quick easy solutions.

Well, also macvtap works on older hardware where I don't have physical functions to passthrough via sr-iov, that is what you are pointing to with "macvtaps in the most outer one VM and pass them thru to inner layer
VMs"?

Currently I can use macvtaps with an old HP xw8600 desktop with the integrated  broadcoms

yeah ease/hardware/ignorance

On Mon, Jul 11, 2016 at 6:52 AM, Michal Privoznik <mprivozn@xxxxxxxxxx> wrote:

On 08.07.2016 22:23, jsl6uy js16uy wrote:
> Hello all, hope all is well
>
> this maybe outside of libvirt-users....
> Can you nest macvtap devices to ultimately receive a real routable ip on
> the nested vm?
>

I have never tested it, but why do you want to nest macvtaps? Why not
have macvtaps in the most outer one VM and pass them thru to inner layer
VMs?

Michal

_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users