similar to: Etch Release / Bond networking

I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

Hi, The attached patch fixes the setup of the bridge ports and the bridge itself. Changes: * move some functions to xen-network-common.sh, so both vif-bridge and network-bridge can use them. * add a new function to configure bridge ports and use it. * make sure arp requests, ipv6 autoconfiguration and ipv6 router solicitations are disabled for the bridge ports and also for the

Hallo, I have running xen-4.2/linux-3.8 (compiled) on any hosts. - dell pe r720: drac, eth0-3:igb squeeze -> boot_xen:ok net:ok bridge:ok - dell pe R620: drac=eth0, eth1-3:tg3 wheezy -> boot_xen:ok net:ok bridge:fail So i running "xend start" (or "xenbridges start") on my patient (R620 with broadcom tg3) network will be lost: RTNETLINK answers: File exists

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, Executive summary: dist-upgrade - squeeze to wheezy. Rebooted machine; no default route on network interface eth0. Commented 'transfer_addrs' function in network-bridge produced a machine which worked after reboot. We're using network-bridge as our xen networking configuration. After rebooting the

Hi, I have a small issue with the SAY command and i hope you can clarify it out for me. I boot my system with the attached extlinux.conf, which has some entries to boot old kernels. When i'm booting the old versions i'd like to have a reminder message recalling me that the most recent kernel is not being used, so that i don't forget to switch back to it, for example after many days of

Hello, Since my last update of xen, I am having problems with bridges and xen. When I want to start a bridge on the dom0 (to run a domU in a different vlan than the default) I run /etc/xen/scripts/network-bridge start netdev=eth0.302 bridge=xen-br302 antispoof=no where eth0.302 is an interface associated with my vlan 302 (it tags with this vlan identifier). The problem I have is that it

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

> > When you run xend it runs network-bridge which creates the bridge, > > renames eth0->peth0 and veth0->eth0 and brings the new eth0 back up. > > kewl, thx Ian. i see network-route doesnt do this. i think > thats a good thing. do you forsee that changing? I expect that in most routed configurations people use their own network script rather than using the

> That''s great, except when you need *two* bridges, for two > independent subnets, and there is no, as far as I can see, peth1. You can have multiple vethX interfaces on recent builds -- see netback/loopback.c. I think the current default is a rather miserly 1 (and should be increased), but can be set on the command line. Ian > Em Wednesday 14 September 2005 16:30, John

I'm trying to get an Archlinux guest running on a Archlinux host. Everything works except ethernet. When I boot the host, --- # dmesg |tail [ 8.265493] Bridge firewalling registered [ 8.514547] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 8.645303] ip6_tables: (C) 2000-2006 Netfilter Core Team --- Then I do --- # virsh -c lxc:/// start gitolite Domain gitolite started #

Hi, I'm running OpenStack on CentOS 6.3 to manage lxc instances. And running into series of problem relating libvirt and lxc interaction. For example, libvirt_lxc segfault ( https://bugzilla.redhat.com/show_bug.cgi?id=874549) which has an upstream fix. And another bugs such as fail to start when SELinux disabled. Finally, I decides to adopt libvirt 0.10.2, self compiled from

Dear I need create second bridge xenbr1 for separate traffic between my virtual machine , I following this step but show message that Link veth0 is missing, how I can create veth0 ? When I run script for create xenbr1 ./network-bridge netdev=eth1 bridge=xenbr1 start Shwo this message Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the

Hello, I''m still having problems with my ''upgrade'' to the FC4 xen packages. I have a domain with two virtual network interfaces, in two different subnets. For a domain with a single interface, the new networkd setup script works fine, but it does work (for me) with two interfaces. It used to work fine, and I used to set it up with simply by more or less blindly doing

Package: xen-utils-common Version: 3.2.0-2 Hello We used the script "network-bridge" on our Xen servers based on "etch" (xen-utils-common 3.0.3-0-2) to setup bridge configuration. This script created a bridge "xenbr0", renamed "eth0" to "peth0", renamed "veth0" to "eth0" and added "peth0" and "vif0.0" to

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

When we create an L2 loop on a bridge in netns, we will see packets storm even if STP is enabled. # unshare -n # ip link add br0 type bridge # ip link add veth0 type veth peer name veth1 # ip link set veth0 master br0 up # ip link set veth1 master br0 up # ip link set br0 type bridge stp_state 1 # ip link set br0 up # sleep 30 # ip -s link show br0 2: br0: