similar to: about removing the peth0

Hi, I would like to ask concerning problems after installing xen 3.3 on Centos 5.2 I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After done with make world and make install, I did mkinitrd and placing it in /boot changing the grub and reboot.. succeded I do not install libvirt and the domUs from the previous xen 3.0 (built-in Centos 5.2) are NOT able to start : [root@wing

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

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

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

Hi, Creating a new domain is a lot easier in opensuse 11. I follow the instruction on the website and build a virtual machine which uses opensuse 11 as well (I installed it from iso image). Everything works fine except the network. I cannot access the Internet from DomU. Here is some information. P.S. the DomU id is 1. "brctl show" in Dom 0: bridge name bridge id STP

(if this post gets line-feed-mangled please read http://www.dl.reneschmidt.de/shorewallxenpost.txt - that''s an unmangled version, thank you) Hello, first I would like to thank the Mr. Eastep and contributors for this great piece of software and superb documentation. I have a SOHO server (Debian testing) that I''m using for several purposes so I''ve set up a Xen

> That''s great, except when you need *two* bridges, for two > independent subnets, and there is no, as far as I can see, peth1. You can have multiple vethX interfaces on recent builds -- see netback/loopback.c. I think the current default is a rather miserly 1 (and should be increased), but can be set on the command line. Ian > Em Wednesday 14 September 2005 16:30, John

I'm having some issues with Internet access from CentOS7 server which is installed in Vmware Workstation 10.0.3 build-1895310 in Windows 7 x64. At this point I can't get if the error is on CentOS configuration or it's another problem so I leave here what I did in order to get Internet working on that VM. 1) */etc/resolv.conf* # Generated by NetworkManager nameserver 8.8.8.8 nameserver

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

I''ve just installed Xen on a new CentOS 5.1 system, and I can''t seem to make xenbr0 connect to the network. This system has a single physical network card. Apart from creating a few DomU guests, I have not changed any of the configuration. After running network-bridge, xenbr0 and friends are created, but the address and routing info is not moved. James # ip addr

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?

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.

Hi All, I just started using Xen a few days ago on Ubuntu Feisty Server. Did a binary install of 3.1 and within very little time had 2 windows 2000 domUs up and running. This made me very happy until I realized I was unable to access dom0 or either of the domU''s from the network. The domUs can access the network if they initiate the connection. After attempting to ping dom0 or domU from

Last problem I had involved changing one character in my configuration scripts. Really easy once someone showed me what was wrong. Well I think this issue is just the same. The moment I used apt to install the Xen kernal and tools I lost internet connectivity. I have been managing because I can restore connectivity be deleting the bridge mpower@dodtsair:~$ sudo ifdown eth0

shorewall version 2.0.7 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:48:53:25:b2 brd ff:ff:ff:ff:ff:ff inet 81.169.188.152/32 brd 81.169.188.152 scope global eth0 3: eth1:

I can''t find network device in domU. Debian domU shows Configuring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device and Fedora domU shows: eth0: unknown interface: No such device Dom0 is using Fedora with: kernel-xen-guest.i686 2.6.15-1.29_FC5 installed kernel-xen-hypervisor.i686

Hi, I have a linux server running kernel 2.6.19 that is connected with 2 seperate 100Mbit links to the same isp: +---+ +---------------+ | I | +---------------+ | | | S | | | | eth0 --+--------------+ P | | |

Hi, I''m using Xen 3.0.3 on two servers with Debian Etch (amd64). These servers have 10 nics (2 onboard and 8 in two 4-port cards) so that every vm can have its own interface. This worked so far with the Xen Version from Etch with a wrapper script wich started 10 bridges at boot time. But now I''ve updated Xen on one of these server to Xen 3.2.0 from backports.org and now the

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

Command just times our for me virt-install --paravirt --vcpus=4 --name server1 --ram 4096 --file /opt/xen-images/hlcnwmmp01.img -x "ks=http://10.203.1.11/kickstart/ks-xen.cfg" --file-size 40 --location http://128.61.111.11/pub/centos/5.4/os/x86_64 -b peth0 Starting install... Retrieving file vmlinuz... | 1.9 MB 00:00 Retrieving file initrd.img...