similar to: Bug#679533: Traffic forwarding issue between, Xen domU/dom0

retitle Traffic forwarding issue between Xen domU/dom0 thanks This week again this bug occurred again so we are trying to create some kind of reproduce algorithm. First we've created two virtual machines named koekiemonster.bofh.hq.mendix.net and netappsim.bofh.hq.mendix.net. We've added 29 vifs to koekiemonster.bofh.hq.mendix.net. During this tests we've always had a ping

After turning off hibernation this issue did not occur anymore in Squeeze. Now we've turned on hibernation again, ran the test to reproduce this issue and this issue occurred within 10 minutes on Squeeze with Hibernation on. Then we've upgraded our test environment from Squeeze to Wheezy and ran the test to reproduce this issue again on Wheezy with hibernation turned on. This test

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Hi, We're seeing weird behaviour regarding network traffic between a Xen dom0 and domU. I reported this issue yesterday to the openvswitch-discuss mailing list, but it seems this could also be a (regression?) bug in the xen hypervisor or the linux kernel... (we've upgraded xen-hypervisor-4.0-amd64 4.0.1-4 -> 4.0.1-5.2 and

Kevin, Would you mind taking a look at #679533 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679533) and give some feedback about how similar this issue is to your report in #631102 here? There was a hint 631102 might be similar, but from the text in this bug report it's not clear to me if this is about the same issue. Maybe you could comment on it. First results of a big shoot-out

Processing commands for control at bugs.debian.org: > retitle 679533 Traffic forwarding issue between Xen domU/dom0 Bug #679533 [xen-hypervisor-4.0-amd64] Traffic forwarding issue between Xen domU/dom0 and ovs Changed Bug title to 'Traffic forwarding issue between Xen domU/dom0' from 'Traffic forwarding issue between Xen domU/dom0 and ovs' > thanks Stopping processing here.

Package: xen-utils-common Version: 4.1.2-3 Severity: normal When configurating a duplicate custom vifname for interfaces in the Xen dom0 that are added to a bridge (which is obviously a configuration error), the hotplug scripts fail silently to rename the new vifX.0 to the custom vifname, if it's already existing. The result of this, is that the domU will start normally, but no network

Whoops, that patch is obviously missing an extra line containing a fi statement. Fixed version attached. And configurating is obviously not english. :) -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenburg at mendix.com | www.mendix.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

Package: xen-utils-common Version: 4.1.4-2 Severity: normal Hi, During some research I encountered incorrect information in the man page of xm, about the dump-core functionality: The man page says: "Defaults to dumping the core without pausing the domain if no I<OPTIONS> are specified." When taking a look at the source code of this process, the default behaviour is to actually

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-8 Severity: normal Tags: patch The Xen hypervisor in Debian Jessie does not boot on recent HP server hardware (e.g. the current dl360 gen9 series) when using normal "legacy" boot. During boot, it panics with the message "System without CMOS RTC must be booted from EFI". This message was introduced in upstream commit

2005/9/21, Cole, Ray <Ray_Cole@bmc.com>: > I saw something similar running Xen 2.0-testing on a machine with a P4. I''d been running on it just fine, but I decided to see how performance would be with and without hyperthreading enabled. So I went into the system setup and disabled hyperthreading. Domain 0 started booting and when it got to the point of starting my guest domains

Hi, I can''t get rid of an annoying domU machines hanging issue with Hyperthreading enabled in my BIOS. Hardware config: IBM x325 series 2 * CPUs Intel Xeon 3.06 Ghz Xen version: 3.0.0 Kernel version: 2.6.12.6 Linux distrib: Debian Sarge 3.1 r1 I run 1 domU machine on my dom0, here is my Xen config: . xen0: /etc/xen/xend-config.sxp : (dom0-num-cpus 0) .

Hello all, My machine is a dual xeon x5520 server with NUMA support. I have some question about xen dom0 kernel. Since xen hypervisor has provided vcpu schedule, do we need to compile the following feature in dom0 kernel? - Tickless System (Dynamic Ticks) - High Resolution Timer Support - AMD IOMMU support - SMT (Hyperthreading) scheduler support - Multi-core scheduler suppor

Hi, I am using xen 3.1.3 on a Celeron, a netbsd 4.0 dom0, and netbsd 4.0 and slackware 11 (with 2.6.18.8-xen kernel) domU''s, and a bridge to communicate between those. I noticed traffic between (both ways) netbsd dom0/domU is rather slow (4Mb/s max), and traffic from the linux domU to dom0 is about 18Mb/s, while traffic from dom0 to the linux domU is rather slow again (4Mb/s max). Any

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Xen Networking[1] works by creating a new pair of virtual ethernet interfaces (vifN.M in dom0 and ethM in domU with id N) and connecting then by an internal "crossover ethernet cable". My understanding of the "internal crossover" thing is that networking statistics should be the same no matter if you measure

Hi list, We, an OSS advocacy group, setup a Xen 3.1 machine composed of : . a 64 bits dom0 running Debian stable amd64 . 2 hvm domUs running OpenBSD amd64 . 2 hvm domUs running NetBSD i386 This machine is to be hosted and reachable from the Internet, but it will only have one public IP. Naturally, our first tought was to port-forward using iptables / netfilter. We didn''t really

I'm just dumping all I got in here, after initial feedback we can see how to organize todo's around it. tl;dr: * Does not upgrade cleanly from 4.8 packages, so we have to prevent this from entering testing until we fix that. * Live migration is broken, explodes with memory allocation errors. ---- >8 ---- 1. Build packages * I have built salsa/master using pbuilder targeting sid.

Hello I''ve got Debian sarge 2.6.18 Traffic Manager setup as a bridge. This server is p4 hyperthreading with 3Gb of memory. Yesterday on 10:00pm start to see in my syslog that ip_conntrack was full and on 12:00pm the server was frozen ... I precise that I''ve already change CONNTRACK_MAX=131072 and HASHSIZE=65536 values I''m not sure that is a direct conntrack

On Tue, May 16, 2017 at 10:26 PM, Jerry <jerryubi at gmail.com> wrote: > Howdy, > > I recently went through a frustrating experience trying to get Xen 4 > running on a CentOS 7 system. After a fresh install, fully updating the > system, rebooting, then trying to install Xen4CentOS it would fail to boot > into the 4.9 kernel, sitting there with a blinking cursor

>but if I disable hyperthreading (noht on the kernel line in lilo/grub) Could the same result could be obtained if hyperthreading is disabled from the BIOS ? Supermicro Motherboards (most Phoneix based) have this option Also, would we see same pops and clicks in a dual CPU box (Zeon) then ? SW Message: 1 Date: Wed, 07 Jan 2004 14:32:16 -0500 From: Jeremy McNamara <jj@nufone.net> To:

Hello all, I''ve been trying to setup some iptables on dom0 and the standard xen bridge-network. If I set the default policy on FORWARD to DROP iptables -P FORWARD DROP all traffic stops working. Can someone please explain this too me? Thanks. Chris. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com