similar to: peth1 not created on boot, now what?

Hi, We''ve been using xen with pc clones for some time now. But now the boss wants to get serious and start using real servers. We''ve been looking at HP. I got in touch with a couple of distributors for prices and much to my suprise, I''ve been told by one HP Partner that Xen does not run on HP hardware. (a ProLiant ML 150) He continued to tell me that he could offer me

If you get a lot of those messages and you don''t want them: peth1: received packet with own address as source address or peth0: received packet with own address as source address This is the way I found to solve this problem on Debian maybe someone can post more information about other distribution like suse or redhat... This problem will occur if you have more than one dom0 on your

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

Hi! I''m not new to Xen but I''m new to this list. I''m having a truely bizarre problem with Xen bridged networking at the moment. This is a new install, on RHEL4. The symptom is that any domU set up simply fails to talk to anything else. It''s there, and running, and it has an ethernet device, but there''s never any response. After digging through the

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

Hello, I''ve recently changed my xen network setup and now, almost expectedly, my configuration has broken access to the Domus from the network, and now I need a little help. Previously, I had four interfaces, only one of which was configured to be used by both dom0 and domu. I have since created a bond between eth2 and eth3, expecting that eth0 would be automatically assigned for use

Hi, I have 3 xen box with 2-3 VM on each. Each server has 2 nic (1 for external and 1 for internal network). All VMs are webserver and they mount a nfs filesystem. I''ve noticed that on each dom0 there are many dropped packets. Server config is: 1- DELL (2xQuad Xeon E5320 @1.86Ghz - 8Gb Ram - Perc5 - Kernel 2.6.18-6 (debian etch)) 2- DELL (2xDual Xeon 5110 @1.60Ghz - 4Gb Ram - Perc5 -

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). This appeared in the messages when i started and stopped a DomU: root at dom0:~# cat messages Aug 31 22:04:52 dom0 kernel: [ 775.569937] device vif6.0 entered promiscuous mode Aug 31 22:04:52 dom0 kernel: [ 775.575993] br_lan: port 2(vif6.0) entering forwarding state Aug 31 22:04:52 dom0 kernel: [

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

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 have problems to get Xen 3.0 working on my notebook (FSC AMILO Pro V3205). I already used different operating systems for the xen0 domain, like FC5, SUSE 10.1 und Debian SID (2.6.16-2-xen-smp) but i always run into the same trouble. When I try to start a xenU domain it always hangs and I get this: ----------------------------------------------------------------------- debian37:~# xm create

Dear Xen-Users, I use Xen 3.1.0_15042 on my OpenSuSE-10.3-computer. Without starting the xen-kernel I can connect my second computer via my native computer to the internet. After starting the xen-kernel the xen-bridge came automatically up. How can I configure the xen-bridge or the xen-devices? I get routing problems: Feb 20 18:31:36 intel6550 kernel: martian source 217.237.149.142 from

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

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

I have followed the nat advice from this guide: http://wiki.kartbuilding.net/index.php/Xen_Networking#Routed_Networking_with_NAT_2 I have googled internet for weeks and read almost every thread in this forum without getting a working NAT on my system. My main question is how exactly will the iptable rules with MASQUERADE or POSTROUTING look like if you want access to the internet from Dom U ,

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 Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

I would like to track DomU bandwidth usage from Dom0 but my OpenSuse Xen install is not tracking DomU bandwidth correctly. My DomU guests are able to access the network and therefore the networking layer appears to be working correctly. It just doesn''t report the traffic correctly in ifconfig. I am currently running OpenSuse10.3 with Xen 3.1.0_15042-51.3 running a xen kernel

Hi folks, I''ve been trying to work out this situation for a few days now without much success and dug all over the archives for similar issues, none of which seem to relate exactly. I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell server. It works fantastic with all the default configurations with one strange flaw - as soon as the /etc/xen/scripts/network-bridge

Hi Folks: I have a strange problem with multiple (2) NICs on a CentOS 5.5 dom0 setup running xen 3.4.3 and have been struggling to fix it for some time. I could not find anything by googling or searching through this list but that is probably because I couldn''t figure out the correct search terms. After I configure my bridges the command "system network restart" fails for eth1