search for: vir_domain_net_type_direct

...:00:21:3b:eb:e1'/> <source dev='eno1.710' mode='bridge'/> </interface> It's linux macvlan solutions and it's worked at least since libvirt 1.2.7 for us. As I can see, in version 4.1.0 and later, some changes about DIRECT connect was implemented. VIR_DOMAIN_NET_TYPE_DIRECT is still fully supported in src/lxc/lxc_driver.c But in src/lxc/lxc_controller.c --- libvirt-3.9.0/src/lxc/lxc_controller.c 2017-09-28 13:15:43.322712913 +0300 +++ libvirt-4.1.0/src/lxc/lxc_controller.c 2018-02-28 16:21:05.158799006 +0300 @@ -395,8 +395,14 @@ case VIR_DOMAIN_NET...

...;source dev='eno1.710' mode='bridge'/> > </interface> > > It's linux macvlan solutions and it's worked at least since libvirt > 1.2.7 for us. > As I can see, in version 4.1.0 and later, some changes about DIRECT > connect was implemented. > VIR_DOMAIN_NET_TYPE_DIRECT is still fully supported in src/lxc/lxc_driver.c > But in src/lxc/lxc_controller.c > --- libvirt-3.9.0/src/lxc/lxc_controller.c 2017-09-28 > 13:15:43.322712913 +0300 > +++ libvirt-4.1.0/src/lxc/lxc_controller.c 2018-02-28 > 16:21:05.158799006 +0300 > @@ -395,8 +395,14 @...

2015-03-02 23:41 GMT+03:00 Brian Rak <brak@gameservers.com>: > In IRC, I was directed to this patch: > https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html ... > which does exactly what I was looking for. It doesn't build cleanly in that > state, but it's pretty trivial fix (needs actualType added to the function > definition for

...y there's no support for vhost-net (qemu) in an ethernet domain (<interface type='ethernet'>) ? below code from qemu_command.c: if (actualType == VIR_DOMAIN_NET_TYPE_NETWORK || actualType == VIR_DOMAIN_NET_TYPE_BRIDGE || actualType == VIR_DOMAIN_NET_TYPE_DIRECT) { /* Attempt to use vhost-net mode for these types of network device */ -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299