similar to: 3.2.1 HVM network packets dropped

Hi! I have a problem with my new Xen setup. I have installed Debian etch with netinstall and I''m using 2.6.18-6-xen-amd64 kernel in my dom0 and 3.0.3-0-4 version xen hypervisor. I''m using four network cards on my system and using three of them as xen bridges and dom0 is using the fourth one only for it''s own. So basicly both of my virtual servers use a network card

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; -*-

Hi, I''m trying to set up networking on a new machine. I''m not getting any networking from the domU''s I notice that I have two bridges being created: xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:3024 errors:0 dropped:0

Hello, There is a xen setup in which "brctl show" gives the following output. bridge name bridge id STP enabled interfaces eth1 8000.003048c9d4df no peth1 vif1.0 vif2.0

I''ve looked everywhere for the error message I''ve posted in the title, doesn''t seem like anyone else has it (lots of missing hotplugs scripts). We''re using network-nat. ifconfig -a outputs this: eth0 Link encap:Ethernet HWaddr 00:19:99:a8:f4:5c inet addr:X.X.X.X Bcast:X.X.X.X Mask:255.255.255.255 inet6 addr: X::X:X:X:X/64 Scope:Link

Hello everybody, Here again with a Xenbr0 bridge problem I''m a Gentoo user, xen-sources-2.6.34 and I always used the bridge from eth0 to xenbr0. Here''s what I get at boot time: * Bringing up interface eth0 * null [...] * Starting Xen control daemon ... And the bridge doesn''t come up. The normal behaviour should be that the Xenbr0 bridge comes up automatically, but

Hi, I''m now blocked for 2 days on getting the network to work in my domU. Here is the problem : The domU refuses to start when a vif is configured. It''s just staying paused for about 1m40s, then the xm create command line give back with an "Error: Device 0 (vif) could not be connected. Hotplug scripts not working.", and the domU is destroyed. Nothing particular

Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance.

Hi, I''ve setup a box with xen. For the root machine, it''s ok, it see the network card: alian@yoda:~> /sbin/lspci ... 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 Gigabit Ethernet Controller (rev 19) alian@yoda:~> lsmod .... sk98lin 208748 1 alian@yoda:~> /sbin/ifconfig eth0 Lien encap:Ethernet HWaddr 00:15:F2:39:D4:DF

Greetings, I have two vms, one is a router and the other one is a client, for some reason, the client vm is unable get ip via dhcp from the router vm. here are outputs: vm1.xml: <interface type='bridge'> <mac address='52:54:00:54:78:be'/> <source bridge='virbr0'/> <model type='virtio'/> <address

I am installed Xen 3.0 on a Fedora Core 4(2.6.12-1.1454_FC4xen0) machine. This machine is currently running one host domain: [root@]# xm list Name Id Mem(MB) CPU VCPU(s) State Time(s) Domain-0 0 128 0 1 r---- 49.1 fc4-vm1 1 63 0 1 -b--- 18.5 Following is the network configuration for Domain-0: eth0 Link

Hi all, I have a very strange situation, which I can''t explain. On a Core 2Quad server with 8GB RAM, we have 10 xen domU''s, as follows: vps.animalsaregreat.info login: root@zaxen01:[~]$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 4 r----- 232.2 actionco.vm

Hi, I have a new xen hosting platform. I have given the bridge a static IP which I can ping/ssh to etc, when I create a new vm all works well apart from the networking. If I give DomU a static IP I can''t ping out from the box, Dom0 can''t ping the vm. I''m suspecting it just isn''t seeing the bridge but am unsure where to start looking. This is a very standard

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

I am running Fedora 16 64bit and installed libvirt. I have the VM running with arm emulation with this one issue I can't figure out. I used Virtual Machine Manager to manage the VM and can access its console there. The Ethernet appears to be eth1 and the guest can set an IP on it etc. However, I cannot see any traffic from the Host when dumping any of the interfaces. I've tried

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

TEQL and Subnet problem I have a network topology shown below, and I am trying to use TEQL. My problem is: When I ping to P3.teql0 from P2 ("[P2]# ping 16.119.144.66"), the traffic can never go from P2.eth1, and all traffic only goes to P1.eth0. What P2.eth1 (16.119.144.33) did is broadcasting an ARP asking for the MAC address of 16.119.144.66, although I have specified the route to

Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255

I installed 64-bit xen 3.1.0 (from xensource.com tarballs) on three new machines today, using a configuration setup that I''ve used successfully many times before. However, I encountered a new problem. These are Dell Poweredge 1950 servers, by the way. >From lspci 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet

Hi, I hope someone could help me out. Pls find the details below. dom0: ifconfig before "xend start" eth0 Link encap:Ethernet HWaddr 00:0C:76:53:44:FB inet addr:10.0.0.3 <http://10.0.0.3> Bcast:10.0.0.255 <http://10.0.0.255>Mask: 255.255.255.0 <http://255.255.255.0> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX