search for: virnetworkcr

...pper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createnet.py", line 428, in _async_net_create netobj.create() File "/usr/lib/python3.7/site-packages/libvirt.py", line 3174, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirt.libvirtError: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr3 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name any ideas? thank you m...

...er callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createnet.py", line 472, in _async_net_create netobj.create() File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2993, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirt.libvirtError: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr1 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name. /sbin/iptables exist...

...quot;, line 117, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/network.py", line 82, in start self.net.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2049, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirtError: failed to add iptables rule to allow DHCP requests from 'swan01' I narrowed this down to the fact that firewalld was not running. So I guess there are two bugs: 1) when not specifying dhcp ranges in the xml, it should _not_ try to poke DHCP h...

...job, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/createnet.py", line 472, in >_async_net_create > netobj.create() > File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2993, in >create > if ret == -1: raise libvirtError ('virNetworkCreate() failed', >net=self) >libvirt.libvirtError: internal error: Failed to apply firewall rules >/sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface >virbr1 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No >chain/target/match by that name. > &g...

...job, *args, **kwargs) >   File "/usr/share/virt-manager/virtManager/createnet.py", line 428, in > _async_net_create >     netobj.create() >   File "/usr/lib/python3.7/site-packages/libvirt.py", line 3174, in create >     if ret == -1: raise libvirtError ('virNetworkCreate() failed', > net=self) > libvirt.libvirtError: internal error: Failed to apply firewall rules > /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface > virbr3 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No > chain/target/match by that name...

...y", line 66, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/network.py", line 82, in start self.net.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1863, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirtError: Cannot open network interface control socket: Address family not supported by protocol Anyone have an idea how to fix this? I try also to add a new adapter by hand, but know seems to work her.... so far 4k3nd0

...ot; }, + { name => "virNetworkGetUUID", sig => "net : uuid" }, + { name => "virNetworkGetUUIDString", sig => "net : uuid string" }, + { name => "virNetworkUndefine", sig => "net : unit" }, + { name => "virNetworkCreateXML", sig => "conn, string : net" }, + { name => "virNetworkDefineXML", sig => "conn, string : net" }, + { name => "virNetworkCreate", sig => "net : unit" }, + { name => "virNetworkGetAutostart", sig =&gt...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all