similar to: Xen Cpufreq modules and Networking Issue!

I''m running Xen and created a virtual os called Domain-1. So now I have two systems, Domain-0(dom0) and Domain-1(dom1), both running fedora 8. I only have 1 ethernet device eth0. However, for some reason, my internet doesn''t work in Domain-1. My output for route -n on Domain-0 is: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref

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

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")

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

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, I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following: eth0 Link encap:Ethernet

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

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, If I have a vlan-Id on an interface with an ipv6 address, then I am unable to ping a real router. The problem is that the Neighbour Solicitation originated from the Centos machine is missing the Vlan-Id in the packet. Therefore a real router will drop such a packet. I have tried this with Centos 4.7 and with Centos 5.5 with the same result. If I originate the first Neighbour

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

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

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

Greetings, I am hoping that I am posting my question in the right place, otherwise please accept apologies. The problem that I am trying to resolve has to do with the network and is most likely a very trivial issue, but I simply cannot find any leads to solving it even after several carefully reading several threads on this mailing list and the Xen networking HOWTO. I am trying to setup XP as a

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, When I install xen via yum, using virt-manager to build a machine, I was displayed no options for Shared Physical Device. Here is a pic, just for show http://imgur.com/HiPiY Then, I did yum downgrade xen, got no network options at all. Do I need to restart something or run a script? I want to use peth0. packages (CentOS 5.4): gnome-applet-vm 0.1.2-1.el5 kernel-xen 2.6.18-164.15.1.el5

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

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

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

host and guest both centos 5.5 network is 192.168.62.40 host is setup as follows [root at cloud2 ~]# ifconfig br0 Link encap:Ethernet HWaddr 00:1A:64:12:10:D9 inet addr:192.168.62.199 Bcast:192.168.63.255 Mask:255.255.254.0 inet6 addr: fe80::21a:64ff:fe12:10d9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1705488

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