similar to: How to Networking Bridge?

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0)

Hi Is there anyone who has successfully resolved the low throughput problem in Guest communication. I am using Xen3.4.1 with PV os kernel 2.6.30-rc6-tip On fedora11. While running netperf benchmark on guests throughput results are very low DomU to DomU    0.29 Mbps Why is it so? What would be the problem. Is there any issue with fc11 platform? Regards, Fasiha Ashraf Add whatever you love

Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge

Hi all, Up until now, we''ve been using Xen 3.0 on CentOS 5.x. Under this setup, dom0 was given a virtual ''ethX'' with the original ''ethX'' (now ''pethX'') IP address. Under this older config, neither ''pethX'' or ''xenbrX'' had an IP address. The logic was to keep traffic from the domU''s, through

Hi, in the official XenNetworking ( http://wiki.xensource.com/xenwiki/XenNetworking ) i didn''t find reported how the NAT configuration works with xen. Does anybody know how the vifX.Y (10.X.X.128), gateway of any domU ethX (10.X.X.1) talk with the real ethX of the dom0? Thanks Enrico _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Still trying to make my VMs appear on a subnet of their very own and route traffic to/from them from the Dom0. This network-multinet script sounds ideal for what I want: http://thepenguinpriest.com/linux/scripts/network-multinet.html However, the description of building a routed network says I need to call the script and give it the "virtual ethernet device (vethX)" that lives in

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt at centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E at MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

Hello, My first post on Xen-Users, so .. i''ve discovered a strange problem. Setup: -A Windows server 2003R2 (x86) with GPL PV driver 0.9.9 ipferf 1.7.0 (from 2003) -dom0 a opensuse 11.0 xen: # rpm -q -a |grep -i xen kqemu-kmp-xen-1.3.0pre11_2.6.25.5_1.1-7.1 kiwi-desc-xenboot-2.38-67.1 xen-3.2.1_16881_04-4.2 xen-tools-3.2.1_16881_04-4.2 xen-libs-3.2.1_16881_04-4.2

This patch causes "xm mem-set" to be lower bound on domX-min-mem option in xend-config. Another configuration option called domU-min-mem has been introduced, which works similarly to dom0-min-mem. This is prevents users from freezing the system when doing "xm mem-set" on very low values like 32M. Signed-off-by: Aravindh Puthiyaparambil

I run configure in a build folder using CC=gcc CXX=g++ ../configure --prefix=/project/scratch/packages2/clang \ --enable-targets=host --enable-shared The configure runs fine but when I type make I get the error: make[1]: Entering directory `/project/scratch/tmp/llvm-3.3/build/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build In file included from

On Mon, Jun 24, 2013 at 6:17 PM, Jorge Rodrigues <skeept at gmail.com> wrote: > Norm, > > thanks for the help. Applying the fix solves the issue I mentioned but now I > have more issues. > > I can install clang, but when running I cannot compile and link files. > If I compile with -c flag it works but compiling the following x.c file > gives an error: >

On Jun 24, 2013, at 4:18 PM, Stefan Teleman <stefan.teleman at gmail.com> wrote: > I'll file the bug about the endian stuff, but we'll also have to have > an <endian.h> in Solaris as well. Do you still have issues after r182419? commit 01ef4f6982451e6a7c00a713d9ae677d3a15d042 Author: Jakob Stoklund Olesen <stoklund at 2pi.dk> Date: Tue May 21 13:36:13 2013

Package: xen-utils-4.17 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are

Hi guys, I''m just beginning to use RSpec and I ran into the issue of testing a named_scope. I''m not actually trying to test its behavior, as it''s not my code, but I wanted to test at least that it''s defined. I tried doing this: describe Post, ".most_recent" do it "should be defined" do Post.method_defined?(:most_recent).should be_true

Hi all, With help from others, I''ve been able to get Olaf''s patch for enabling MTUs >1500 for vifX.y and tapZ devices working. I''ve been able to boot dom0, launch domU and live-migrate without having the bridge''s MTU degrade at any time. Would the Xen RPM maintainers (and others) mind taking a look at the following patches? Kernel part:

Hi, I've tried to use SIPSAK to understand the troubles i'm having about sending my voice to the person I've called (extension), after doing this tests below I always got this error "error: this FQDN or IP is not valid: voicegw". This could cause problems (namely audio problems)? Best regards, Helder voicegw:~# sipsak -C empty -a password -s

Hello, I''m new to Xen (and this mailing-list) and facing some problems with the network. I''m stuck and don''t know how to continue. And Google isn''t very helpful either... My setup: - Ubuntu 7.10 for dom0 and Debian 4.0 for all domU - 4 physical NIC (DHCP from my ISP, internal LAN, DMZ & WLAN) - 1 Dom as firewall/router - 1 domU with internal services

Norm, thanks for the help. Applying the fix solves the issue I mentioned but now I have more issues. I can install clang, but when running I cannot compile and link files. If I compile with -c flag it works but compiling the following x.c file gives an error: x.c: int main(void) { return 0; } > ./clang x.c /project/helder/scratch/packages2/bin/ld: unrecognized option '-C'

> It means that you are using a broken XML parser and you should delete the > comment before the namespace is defined near the top of the config file. > > Comments are the tags that look like <!- this --> (in case you didn't > know) > > That should fix the problem. > -- Tnx, now the XML parse error don't appare. But...yes, there's a but: Unknown