search for: msg00762

Hi, I have some guests running in the "default" network (virbr0) and I've also created a similar (NAT) network (virbr1). Therefore, the FORWARD chain for the CentOS 6.4 host looks like this: http://fpaste.org/29229/75281379/ ...where line 3-7 are related to virbr0 and 8-12 to virbr1. My 2 questions: 1) I've noticed that I can ping from a guest within virbr0 to any guest on

Hello All- I've looked in several places and haven't found an answer to this question: is it possible to have libvirt add custom rules to iptables for virtual network interfaces? I took a look at the "Firewall and Network Filtering in Libvirt" page and it seems overly complicated for what I want to do. Given an interface virbr2 and its network 192.168.4.0/24, libvirt installs

...ld. It's both paternalizing and annoying and takes away user flexilibity in exchange for nothing. anyways Check the nwfilter page to write own filters for the beginning: https://libvirt.org/formatnwfilter.html#nwfwrite some more info: https://www.redhat.com/archives/libvir-list/2010-June/msg00762.html https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-virtual_networking-applying_network_filtering regards Am Donnerstag, den 30.05.2019, 21:44 -0400 schrieb Joshua Kramer: > Hello All- > > I'...

...ork can reach all other networks (just because it > happens to be the first one defined). Is this the intention (only > default can talk to the others but not the other way around)? *Bump* I found this excellent post by Daniel Berrange: http://www.redhat.com/archives/libvir-list/2010-June/msg00762.html ...which explains all the firewall rules that libvirt creates based on the type of network you choose. Reading this I get the idea that, the intention for NAT virtual-networks, is to allow them to communicate with ANY other virtual-network on your system (since there's an allow rule for...

...ks (just because it >> happens to be the first one defined). Is this the intention (only >> default can talk to the others but not the other way around)? > *Bump* > > I found this excellent post by Daniel Berrange: > > http://www.redhat.com/archives/libvir-list/2010-June/msg00762.html > > ...which explains all the firewall rules that libvirt creates based on > the type of network you choose. Reading this I get the idea that, the > intention for NAT virtual-networks, is to allow them to communicate with > ANY other virtual-network on your system (since there&...

I can''t boot my PV domU domain using a pv_ops 2.6.30.1 kernel. Using the xenified standard debian kernel (2.6.26, the same as in dom0) in DomU it does boot with pvgrub. Any clues, to what to try or test ? Regards, Sander xm dmesg gives: traps.c:437:d12 Unhandled general protection fault fault/trap [#13] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 12