similar to: dom0 packet drops caused by domU cpu load

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

We have been using Xen as our vm only recently (about a year now). We recently started to look at the tcp flow control that is coming in and out of the VM. Our configuration is that a physical interface on the host, peth1, is connect to vif1.1 by bridge br1, vif1.1 is instantiated as eth1 inside the vm. We have a data source attached to eth1 that over subscribe the data capacity of peth1.

When I start xen dom0 I get that same dhcp address for eth0 and for xen-br0, dom0 can talk to the world. If I start each of my 3 domU''s mannually, each guest gets a xen-br0 vif with a dhcp address and all 3 can talk to the outside world and each other (my "flat network"). What I want is a tiered network with the first domU acting as a firewall with 3 nics vif = [

Hi! Maybe, I found a bug of xen. My system: - domain0 - gentoo - xen-devel-3.0, kernel 2.6.12.5-r1 - domain1 - debian - kernel 2.6.12.5-r1 (2 interface: vif1.1 = eth0 (0.0.0.0), vif1.2 = eth1 (10.0.1.1 + gw 10.0.1.2)) Bridge: xen-br0 (config as 10.0.1.2) include (vif1.2, vif0.0) xen-br1 (config as 0.0.0.0) include (vif1.1, peth0) On server domain1 I use a pppoe server. If a send a pppoe request

>>> On Sun, Oct 25, 2015 at 02:34:56AM +0000, Patrick Masotta via Syslinux wrote: > Micheal Brown > > > > iPXE's HTTP implementation is definitely not slow. On a Gigabit LAN, > > you should get the full 1000Mbps speed for HTTP downloads: a 200MB test > > file should transfer in under two seconds. For most practical OS boots, > > you won't even

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker

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

Hello @all, thanks for all the helpfull answers in this mailing list. They helped me compiling a new kernel 2.6.10.11 with Xen 2.0.6 (my first one), setting up a dom0 with RAID, LVM and loop devices for domU, integrating a second network as xen-br1 (I''m calling the /etc/xen/scripts/network script from within /etc/init.d/xend to bring up / down the second bridge.) and bootstrapping

Hi, I found this mail about network problems in the archive. I think I have the same network problems with a routing (with or without NAT) domU connected by two network bridges. The dom0 logs thousands of following messages: -- Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet -- and all outgoing TCP packets have wrong TCP checksums (traced on another machine on the

Hello I have a 3 node experiment as detailed below to estimate the bridged networking performance in para-virtualized Xen 3.0 on Emulab (https://www.emulab.net/) Here is how the 3-node topology looks (This topology is specified by means of an NS-2 file) topology: _______________________________ | | Node0:eth0 ------|Node1:eth0

Hi, how would I make it so that a particular virtual network interface of dom0 is attached to a particular bridge created for a particular VM? When I start the VM with 'virsh start <domU>', I get interfaces vif1.0, vif1.1 and vif1.2. After shutting down domU with 'virsh shutdown <domU>' and starting it again as before, the virtual network interfaces are vif2.0,

I think the diagram here: http://wiki.xensource.com/xenwiki/XenNetworking#line-474 should be more like this: http://pastebin.com/cjxbXrJW I''ve asked Stephen for edit rights on the wiki but wanted to ask for confirmation before editing it. Notes: The connections at the top are switch ports bond1 has eth2 and eth3 eth0 maps to bond0.100 and eth1 maps to bond1.200

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi All, Does anyone know, if there is a tool, which is doing the follwing: - Testprogram on host A establishes a sip connection to testprogramm on host B - Testprogram on host A plays a tone and Testprogram B verifies, if tone is playing correctly (without any interruptions) Thank You.

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all

So Working on CEntOS 5 I am trying to sett up Xen with 2 bridges, one that connects dom0 and most of the domU to the physical card and the out to the network. Got that figured out no problem, now i want to have a second bridge that runs a local network for all the doms that doesn''t connect to the network. With code I have found used in multiple places I can easily get 2 bridges, and

Hi, I''ve bit the bullet and gone with Xen, but I get some odd networking. Basically, this was the original idea. eth0 external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get

I have a server running Centos 5.2 as a Xen host. A problem that's shown up recently is that at boot, the dom0 interface eth0 doesn't come up properly, with the result that the host is only accessible via remote console. If I execute 'service network restart', eth0 comes up normally, with an IP address and the correct routing. Three guests have been created via virt-manager

Some what In-Reply-To: <1323092879.2629413.1445740496536.JavaMail.yahoo at mail.yahoo.com> On Sun, Oct 25, 2015 at 02:34:56AM +0000, Patrick Masotta via Syslinux wrote: > Micheal Brown > > > > iPXE's HTTP implementation is definitely not slow. On a Gigabit LAN, > > you should get the full 1000Mbps speed for HTTP downloads: a 200MB test > > file should