similar to: eth0 on dom0 not working on a bridged conf

Hello. I''ve just started with Xen and configuring Dom0. My hardware is Core2Duo based Xeon server and I installed Debian etch for amd64 architecture. The Xen related pachages installed are the following. linux-image-2.6.17-2-xen-amd64 linux-modules-2.6.17-2-xen-amd64 xen-hypervisor-3.0.3-1-amd64 xen-tools xen-utils-3.0.3-1 xen-utils-common My problem is that when xend is

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

Hello, I''m used to using Xen in a bridge mode where my dom0 and all domUs are on the same layer 2 network. However now I have to set up a server whose eth0 is on one network and the domUs will be on another /29. So, for example, if the eth0 of dom0 is 192.168.1.214/24, then I have 10.1.1.0/29 (10.1.1.0 -> 10.1.1.7) routed to it for use in domUs, how would I go about setting that up?

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

Hi, My bridging stops when I start a third Xen domain !?!? I have a few domains setup (mail, wiki, pbx). If I start two domains bridge networking works great. But if I start a third, either the new domains does not work or one of the other DomUs stops working! By stop working I mean I can''t route traffic outside of Dom0. I have been looking at this on and off for a couple of weeks.

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

Hello. I have installed the SuSE Linux 10 XEN kernel but no domU yet. Now I cannot ping to and from dom0. I get lots of ARP broadcasts from dom0 but dom0 seems to ignore ARP answers. When pinging to dom0 it ignores arp requests. This happens regardless xend is running or not. This happens in the xen kernel only, when booting stock kernel all works as expected. What can I do? Robert

Hi ALL, Here is a weird problem comfusing me for a long time. i''v installed xen 4.0.1 with linux kernel 3.1.0-rc9+ Everything works fine except i cannot ping to the gateway in a PVM domU. i''v installed bridge-utils and brctl show like this bridge name bridge id STP enabled interfaces eth0 8000.00219b480d56 no

Hi, I was hoping someone on this forums could help me out with a problem I was facing with Xen. When I compiled the kernel for Xen-3.1.3 using "make world"(I know this is an old version but I need to use it for some compatibility issues), the kernel was missing the Xen netloop module. There was no /kernel/drivers/xen/netback/netloop.ko in the newly compiled kernel. I think we would

Hi guys, i use xen3.2. how can i manually create the xenbr0 ? which parameters have i to choose for brctl ? thanks, -- Viele Grüße Dominique Holger Schramm | Linux Administrator http://schwarz-weiss.cc/ | Life between PuTTy and reality http://ihr-linuxadmin.eu/ | Commercial Admin Service _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello! Has anybody experienced network latency problems with combination of Windows 7, GPLPV drivers and RDP connection? Any Windows pop-up message(such as "command not found" error message in "Run command:" dialog, or dividing by zero in windows calc) causes a short freeze of RDP session and looks like that from dom0: PING 192.168.44.65 (192.168.44.65) 56(84) bytes of data.

Hi, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things

Hi all, My setup is Debian testing dom0/domUs with a 2.6.32 pvops kernel from Debian unstable. Hypervisor is 3.4.2 from Debian testing. I use network- and vif- route with a default route in domU pointing to the nic because multiple IPs with bridge would trigger port shutdown on the switch (only one mac-address allowed per port). A subnet is routed to the dom0, which then knows which addresses the

Hi, I have a strange problem with my networking setup. I read all forums around the world where people had similar problems, but couldn''t find a solution. I have an Attansic L1 gigeth chip on my mainboard. This chip works OK in stock Ubuntu Gutsy (development) 2.6.22-9-generic kernel. When I boot into Xen, and after the bridge is created, the network stops working. Some info: - If I

Hi all, Does anyone know what the correct steps are to add a XEN bridge, let''s say xenbr0 to Debian Squeeze? I have added the following to /etc/network/interfaces # XEN Bridge auto xenbr0 iface xenbr0 inet manual bridge ports eth0 bridge_stp off bridge_fd 0 And then rebooted the server but brctl show still shows eth0 as bridge: newusaxen:~# brctl

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

Dear, After reboot server I can not start any VPS Client. Dom-0 is running, but when I start any Dom-U this error message appear: - Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err ''Device 0 (vif) could not be connected. Could not find bridge device xenbr0''). Please help, Wendy _______________________________________________

It seems that with their specific Xen packages, Debian likes to go against the norm, and rather than calling the Xen bridging device something sensible like "xenbr0", they rename the main physical ethernet device "eth0" to "peth0" and create "eth0" as the Xen bridge (as far as I can tell, anyways). Anyone know where exactly they do this so I can reverse it?

Thanks a lot for your hints Pasi. Due to your suggestion I open a new thread here. I have tested with model=e1000 (HVMs). As HVM configs are identical (not iso images and LVM volumes) I guess it is a xen 4.1.2* issue .. or just involved domU OS-kernels (however as it is HVM it should not play any role) Tested and correctly working OSes (getting an IP address and pinging of

I just got an inexpensive VPS too have an outside server to play/test with. I am pinging it every 5 minutes and graphing with MRTG on another CentOS box. This works fine to all servers but the VPS. The first ping to the VPS is always crud and following ones are fine. [root at ns1 scripts]# ping X PING X 56(84) bytes of data. 64 bytes from X: icmp_seq=1 ttl=55 time=773 ms 64 bytes from X: