Nested oVirt : Unofficial network recommendations wanted
Hello, I'm trying to setup a nested oVirt for the first time, and according to what I read around and experience, some special network settings have to be chosen. For this first try, the bare-metal host is a Debian, running KVM, and the virtual NICs are setup as macvtap in VEPA mode. I'm not up to date with macvtap, but I think I understood that one of its limit was that no packet could be exchanged between the host and the guests. So far, this is leading me to access my own local VMs from another host. Too bad. I'm also witnessing frequent loss of packets. So far, I'm also seeing that guests can not ping each others, so I'm not going further before having solved these basic issues. I'm remembering the good old times of lots of bridges where my VMs could be reached by anyone (this was desired), but virt manager is not offering me this choice. I also would like to avoid NAT for other reasons. To you all (4) people who are playing with nested oVirt : - which is your preferred bare metal OS? - which is your preferred guest (first virt level) OS? - which network setups and modes are working best? Thank you. -- Nicolas ECARNOT
On Thu, Sep 15, 2016 at 3:43 PM, Nicolas Ecarnot <nicolas@ecarnot.net> wrote:
Hello,
I'm trying to setup a nested oVirt for the first time, and according to what I read around and experience, some special network settings have to be chosen.
For this first try, the bare-metal host is a Debian, running KVM, and the virtual NICs are setup as macvtap in VEPA mode.
On what device you attached it? Bridge? the physical nic?
I'm not up to date with macvtap, but I think I understood that one of its limit was that no packet could be exchanged between the host and the guests. So far, this is leading me to access my own local VMs from another host. Too bad.
I'm also witnessing frequent loss of packets.
So far, I'm also seeing that guests can not ping each others, so I'm not going further before having solved these basic issues.
By definition: http://virt.kernelnewbies.org/MacVTap
I'm remembering the good old times of lots of bridges where my VMs could be
reached by anyone (this was desired), but virt manager is not offering me this choice. I also would like to avoid NAT for other reasons.
To you all (4) people who are playing with nested oVirt : - which is your preferred bare metal OS? - which is your preferred guest (first virt level) OS? - which network setups and modes are working best?
Thank you.
-- Nicolas ECARNOT _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------2C489EA73C8DEFB69DF2F697 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Le 15/09/2016 à 23:27, Edward Haas a écrit :
On Thu, Sep 15, 2016 at 3:43 PM, Nicolas Ecarnot <nicolas@ecarnot.net <mailto:nicolas@ecarnot.net>> wrote:
Hello,
I'm trying to setup a nested oVirt for the first time, and according to what I read around and experience, some special network settings have to be chosen.
For this first try, the bare-metal host is a Debian, running KVM, and the virtual NICs are setup as macvtap in VEPA mode.
On what device you attached it? Bridge? the physical nic?
On my physical host, ifconfig is showing the following devices : - lo, obviously - eth0, primary used - wlan0, not used, WIFI... - virbr0 - virbr0-nic The last two devices were created when installing and playing with the KVM Virtual Machine Manager. When trying to assign one of them to a VM, the only choices are : - NAT - eth0: macvtap - wlan0: macvtap - custom and the source mode can be chosen between : - Bridge - VEPA - Private - Passthrough My main goal is simplicity, and I'd rather use simple bridging, no NAT, simple. What would be the simplest choice?
I'm not up to date with macvtap, but I think I understood that one of its limit was that no packet could be exchanged between the host and the guests. So far, this is leading me to access my own local VMs from another host. Too bad.
I'm also witnessing frequent loss of packets.
So far, I'm also seeing that guests can not ping each others, so I'm not going further before having solved these basic issues.
By definition: http://virt.kernelnewbies.org/MacVTap
I'm remembering the good old times of lots of bridges where my VMs could be reached by anyone (this was desired), but virt manager is not offering me this choice. I also would like to avoid NAT for other reasons.
To you all (4) people who are playing with nested oVirt : - which is your preferred bare metal OS? - which is your preferred guest (first virt level) OS? - which network setups and modes are working best?
Thank you.
-- Nicolas ECARNOT _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
-- Nicolas ECARNOT --------------2C489EA73C8DEFB69DF2F697 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Le 15/09/2016 à 23:27, Edward Haas a écrit :<br> </div> <blockquote cite="mid:CALmkdFQxxAC9PEvq0tN-B2by6WB7p+1ddPWFK-pGGXs7MeQKEg@mail.gmail.com" type="cite"> <div dir="ltr"><br> <div class="gmail_extra"><br> <div class="gmail_quote">On Thu, Sep 15, 2016 at 3:43 PM, Nicolas Ecarnot <span dir="ltr"><<a moz-do-not-send="true" target="_blank" href="mailto:nicolas@ecarnot.net">nicolas@ecarnot.net</a>></span> wrote:<br> <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Hello,<br> <br> I'm trying to setup a nested oVirt for the first time, and according to what I read around and experience, some special network settings have to be chosen.<br> <br> For this first try, the bare-metal host is a Debian, running KVM, and the virtual NICs are setup as macvtap in VEPA mode.<br> </blockquote> <div><br> On what device you attached it? Bridge? the physical nic?<br> </div> </div> </div> </div> </blockquote> <br> On my physical host, ifconfig is showing the following devices :<br> - lo, obviously<br> - eth0, primary used<br> - wlan0, not used, WIFI...<br> - virbr0<br> - virbr0-nic<br> <br> The last two devices were created when installing and playing with the KVM Virtual Machine Manager.<br> <br> When trying to assign one of them to a VM, the only choices are :<br> - NAT<br> - eth0: macvtap<br> - wlan0: macvtap<br> - custom<br> <br> and the source mode can be chosen between :<br> - Bridge<br> - VEPA<br> - Private<br> - Passthrough<br> <br> My main goal is simplicity, and I'd rather use simple bridging, no NAT, simple.<br> <br> What would be the simplest choice?<br> <br> <blockquote cite="mid:CALmkdFQxxAC9PEvq0tN-B2by6WB7p+1ddPWFK-pGGXs7MeQKEg@mail.gmail.com" type="cite"> <div dir="ltr"> <div class="gmail_extra"> <div class="gmail_quote"> <div> <br> </div> <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"> I'm not up to date with macvtap, but I think I understood that one of its limit was that no packet could be exchanged between the host and the guests. So far, this is leading me to access my own local VMs from another host. Too bad.<br> </blockquote> <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"> I'm also witnessing frequent loss of packets.<br> <br> So far, I'm also seeing that guests can not ping each others, so I'm not going further before having solved these basic issues.<br> </blockquote> <div><br> By definition: <a moz-do-not-send="true" href="http://virt.kernelnewbies.org/MacVTap">http://virt.kernelnewbies.org/MacVTap</a><br> <br> </div> <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"> </blockquote> <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"> I'm remembering the good old times of lots of bridges where my VMs could be reached by anyone (this was desired), but virt manager is not offering me this choice. I also would like to avoid NAT for other reasons.<br> <br> To you all (4) people who are playing with nested oVirt :<br> - which is your preferred bare metal OS?<br> - which is your preferred guest (first virt level) OS?<br> - which network setups and modes are working best?<br> <br> Thank you.<span class="gmail-HOEnZb"><font color="#888888"><br> <br> -- <br> Nicolas ECARNOT<br> ______________________________<wbr>_________________<br> Users mailing list<br> <a moz-do-not-send="true" target="_blank" href="mailto:Users@ovirt.org">Users@ovirt.org</a><br> <a moz-do-not-send="true" target="_blank" rel="noreferrer" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br> </font></span></blockquote> </div> <br> </div> </div> </blockquote> <br> <p><br> </p> <pre class="moz-signature" cols="72">-- Nicolas ECARNOT </pre> </body> </html> --------------2C489EA73C8DEFB69DF2F697--
On Fri, Sep 16, 2016 at 1:32 PM, Nicolas Ecarnot <nicolas@ecarnot.net> wrote:
Le 15/09/2016 à 23:27, Edward Haas a écrit :
On Thu, Sep 15, 2016 at 3:43 PM, Nicolas Ecarnot <nicolas@ecarnot.net> wrote:
Hello,
I'm trying to setup a nested oVirt for the first time, and according to what I read around and experience, some special network settings have to be chosen.
For this first try, the bare-metal host is a Debian, running KVM, and the virtual NICs are setup as macvtap in VEPA mode.
On what device you attached it? Bridge? the physical nic?
On my physical host, ifconfig is showing the following devices : - lo, obviously - eth0, primary used - wlan0, not used, WIFI... - virbr0 - virbr0-nic
The last two devices were created when installing and playing with the KVM Virtual Machine Manager.
When trying to assign one of them to a VM, the only choices are : - NAT - eth0: macvtap - wlan0: macvtap - custom
and the source mode can be chosen between : - Bridge - VEPA - Private - Passthrough
My main goal is simplicity, and I'd rather use simple bridging, no NAT, simple.
What would be the simplest choice?
With Virtual Machine Manager you can edit-connection details and create bridges on the host that you can connect to. I usually use an isolated network, that does not connect to the outside world and is limited to the host. If I need it to access the outside world, I can either connect one of the nics to the bridge created on the host or just create another vnic that uses nat/macvtap. Note that VMM is mainly focused on simple VM connectivity, using it for nested virtualization is not simple and will require from you additional effort.
I'm not up to date with macvtap, but I think I understood that one of its limit was that no packet could be exchanged between the host and the guests. So far, this is leading me to access my own local VMs from another host. Too bad.
I'm also witnessing frequent loss of packets.
So far, I'm also seeing that guests can not ping each others, so I'm not going further before having solved these basic issues.
By definition: http://virt.kernelnewbies.org/MacVTap
I'm remembering the good old times of lots of bridges where my VMs could
be reached by anyone (this was desired), but virt manager is not offering me this choice. I also would like to avoid NAT for other reasons.
To you all (4) people who are playing with nested oVirt : - which is your preferred bare metal OS? - which is your preferred guest (first virt level) OS? - which network setups and modes are working best?
Thank you.
-- Nicolas ECARNOT _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Nicolas ECARNOT
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Le 16/09/2016 à 20:21, Edward Haas a écrit :
My main goal is simplicity, and I'd rather use simple bridging, no NAT, simple.
What would be the simplest choice?
With Virtual Machine Manager you can edit-connection details and create bridges on the host that you can connect to.
Exact.
I usually use an isolated network, that does not connect to the outside world and is limited to the host. If I need it to access the outside world, I can either connect one of the nics to the bridge created on the host or just create another vnic that uses nat/macvtap.
I get that.
Note that VMM is mainly focused on simple VM connectivity, using it for nested virtualization is not simple and will require from you additional effort.
OK. Would you recommend a better suited solution for nested virtualization? -- Nicolas ECARNOT
On Mon, Sep 19, 2016 at 2:19 PM, Nicolas Ecarnot <nicolas@ecarnot.net> wrote:
Le 16/09/2016 à 20:21, Edward Haas a écrit :
My main goal is simplicity, and I'd rather use simple bridging, no NAT, simple.
What would be the simplest choice?
With Virtual Machine Manager you can edit-connection details and create bridges on the host that you can connect to.
Exact.
I usually use an isolated network, that does not connect to the outside
world and is limited to the host. If I need it to access the outside world, I can either connect one of the nics to the bridge created on the host or just create another vnic that uses nat/macvtap.
I get that.
Note that VMM is mainly focused on simple VM connectivity, using it for
nested virtualization is not simple and will require from you additional effort.
OK.
Would you recommend a better suited solution for nested virtualization?
Lago[1]. Y. [1] lago.readthedocs.org/en/latest/README.html
-- Nicolas ECARNOT _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Le 19/09/2016 à 15:26, Yaniv Kaul a écrit :
Would you recommend a better suited solution for nested virtualization?
Lago[1]. Y.
[1] lago.readthedocs.org/en/latest/README.html <http://lago.readthedocs.org/en/latest/README.html>
Yanniv, I read your tweet some times ago about Lago. Is fedora the recommended OS to play with Lago? -- Nicolas ECARNOT
On Sep 19, 2016 5:50 PM, "Nicolas Ecarnot" <nicolas@ecarnot.net> wrote:
Le 19/09/2016 à 15:26, Yaniv Kaul a écrit :
Would you recommend a better suited solution for nested
virtualization?
Lago[1]. Y.
[1] lago.readthedocs.org/en/latest/README.html <http://lago.readthedocs.org/en/latest/README.html>
Yanniv,
I read your tweet some times ago about Lago. Is fedora the recommended OS to play with Lago?
Yes, both my server and my laptop run F24 with Lago. Previously both were F23. Y.
-- Nicolas ECARNOT
participants (3)
-
Edward Haas -
Nicolas Ecarnot -
Yaniv Kaul