similar to: network-routing

Hello, A bit of history ================ 1) I''ve got a normal 2.6.20 x64 Fedora 6 Linux server running several things 2) I''ve downloaded and installed the XenSource Administrator Console for Windows 3) I''ve added 2.6.20-1.2962.fc6xen kernel, xen and vnc packages on my Linux server 4) I rebooted the Linux server, and started xend as per user guide Configuration

I''ve setup Xen 3.0.2-2 (binary install) on Ubuntu 6.06, got my domUs up and running, got them connected to the Internet but I can''t even ping to any of these VMs. Now I''m not linux/xen genious but could the problem be that xen-br0 doesn''t have an IPv4 address? (it''s got an IPv6 address) Since I don''t use IPv6 on my network this seems a

Has anyone ran into this issue before? 2 physical nics: eth0 hooked up to 10.175.8.0/21 eth1 hooked up to 10.150.8.0/24 Ifconfig -a looks like this: [root@mgixen1 ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3 inet addr:10.175.8.158 Bcast:10.175.15.255 Mask:255.255.248.0 inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link UP

I just did a fresh install of centos 5.0 from cd, followed by yum update which installed 399 packages. No failures or errors that I can see. I have three nics in the box, but am only setting up one at the moment. The box can ping others in my network, but if I try ssh, telnet, ftp, etc I get this: [root at cm network-scripts]# ftp watchdog ftp: connect: No route to host ftp> [root at cm

Hi all, Has anyone seen this before? I''m running a CentOS 5.3 with xen 3.0 and the server has been running fine for a long time. In fact, it was up for 186 days before I had to reboot after the "network died", and I couldn''t fix it. The server has multiple domU''s on it, which all still works when the host node (dom0)''s network dies with these

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the

Hi All, We have a single Centos 5.11 server running a xen hypervisor that went down hard after an extended power outage this weekend. I'm mostly familiar for KVM as that is the majority of what our guests run under and have tried getting up to speed on xen bridging to no avail. The problem is that after the xen server spun back up, the previously defined xen bridges were lost. I've

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

Greetings! I finally got the install done for a couple of gust OSs (Win 2003 server & Suse Enterprise 10) Bothe gusts are up and running, but - no networking. My setup: Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB NICs Host OS- Suse Linux Enterprise server 10 Xen - 3.0.2_09749-0.4 Config file for Win 2003 server guest: # -*- mode: python; -*-

Well where do I start...I have a domU (ubuntu) booting and appears well but I don''t have an eth0 listed at all, dom) looks good. DomU: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

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

Hi all, my dom0 is centos5.2 and domU paravirtualized is centos5.1 I can play sound on dom0 but not in domU (name: gasphar), moreover I use wifi as my inet connection and on installing domU cento5.1, I used virt-manager. I know that libvirtd made virbr0 and when changing to xenbr0, I cannot connect to internet but ssh to dom0 is fine! so how do I enable sound device on domU and changing to

Hello, I have the following Xen 3.0.2-2 related problem: A host system with Centos 4.4 in the dom0, guest systems are Fedora Core 5 (images from jailtime.org) mounted on LVM. Networking on the domUs is not working, Iptables in the guests are not working either. Each Guest system should have at least 1 dedicated public IP assigned to it, but should have the capability to have more than 1

Hello everyone. I just installed Xen 3.0.3 in a debian etch box. Linux server1.example.com 2.6.18-6-xen-686 #1 This server1 has two real nic (eth0 with real MAC 00:13:72:57:7B:AE and eth1 with real MAC00:13:72:57:7B:AF). I made a network-bridge custom like this: ----------------------------------------------------------------------- #!/bin/bash dir=$(dirname "$0")

Hello, The basic details of my host and XEN configuration and network configuration all appear below. Whilst I have come this far, a lot of it has been intuitive so I now have plenty of questions. Firstly I would like some help and clarification with regard to ebtables and especially how it works in a Virtualized environment on Novell SUSE 10 SP1 (1) ebtables Installation ebtables was not

I''ve got a system with 3 nics. eth0 is down, eth1 is external and eth2 is internal. (This is in a "lab" so the "external" is a 10.x.x.x address.) Before starting xen, the broadcast for eth2 is 192.168.1.255, after starting it becomes 0.0.0.0 - which sure doesn''t look right to me - plus I''m getting networking problems. Been digging for a while and

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port

Hello, I have problems with installation of my second DomU. I cannot ping it from the outside world and I cannot access outside world from this domain. I see it from Dom0 and my first DomU, same as my second DomU can ping Dom0 and my first DomU. I use xen 3.0.3 on ubuntu 6 LTS. DomU is running on debian. I also network-bridge script in the xend config.

Hello everybody, I have an odd problem with iptables using a Xen bridge setup. I don''t know if it would be better to post to netfilter Mailing-List. But I hope someone here know how to solve it. If it''s OT here, please let me know. I''ll try to do a little bit ASCII-Graphics to explain the topo better: _________ ________

Hi, We''re trying to run Xen on a Debian "Etch" base system (kernel 2.6.18-6-xen-amd64), but have come across a strange networking error whenever bridging (vif-bridge/network-bridge) is in operation. The symptom is that the dom0 base system loses all network connectivity to the outside world while the two guest instances function perfectly well. As far as we can tell, we