similar to: xend nothing to flush, waiting for peth0 to negotiate

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

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

Hi list! I''m trying to figure out a way to use network configuration scripts provided by the distribution to manage network/bridge configuration with xen.. This means I dont''t want use xen "network-bridge" (or any other) script at all, because they are a bit limited in functionality. I want to setup VLAN interfaces with the scripts/tools provided by the

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

hello, I want to configure 2 interface like this eth0 for LAN is 172.16.0.3 eth1 for SAN is 192.168.0.13 I want all VM can access to all network my configuration is : (network-script ''network-bridge netdev=eth0'') to have peth0 and I have a peth0 interface (network-script ''network-bridge netdev=eth1'') to have peth1but I don''t have a peth1 interface

Hi, I found this mail about network problems in the archive. I think I have the same network problems with a routing (with or without NAT) domU connected by two network bridges. The dom0 logs thousands of following messages: -- Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet -- and all outgoing TCP packets have wrong TCP checksums (traced on another machine on the

Hi *.*, This is a continuation on the 2 NICs thread after some more testing. Just to remember my goal. --------------------------- I want to create a domU with 2 virtual NICS. One of them will contact the outside world, the other one will contact a VPN. No reason in concrete for choosing the bridging protocol, only because its the default one. I installed the dom0 with the 2 NICs active, with

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

> 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

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 -

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

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

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...

Situation peth0 = internet peth1 = local private network Dom0 is only configured to use peth1 and works fine as such I have a DomU setup as a NAT box for the local network to the internet and it is functioning as well. DomU is also running a caching DNS and DHCP for the local network The problem I have is DomO''s gateway is set to the local network IP of the DomU, as is

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 all, I have a strange problem with GPL PV 0.8.8 (0.6.4 did work). On my 2nd vif I cannot establish TCP connections. The 3rd IP packet (ACK from XEN-Image) is not forwarded by XEN/DOM0-Bridge. If I boot Windows without /GPLPV option, everything works fine. I did some investigation and found out that the packages arrive differently if GPLPV is enabled. "br_inet" is a bridge

I have seen those documents, I did not see anything that indicates how _automatic_ bridge configuration could be enabled with xl. For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> peth1). If I have to configure this manually with ifcfg scripts I will, but if an automatic method is provided or is possible with xl I'd prefer to use that. -Gene On Thu, Jan 29,

Hello all, I have a Xen server with 6 network interfaces, I want a bridge on all of them. I use a personal network script like this : #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 "$dir/network-bridge" "$@"

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

Hello, running xen 3.0.4_1 I find the following messages in /var/log/messages: kernel: peth0: received packet with own address as source address Is this something to worry about? The tcpdump shows the following pakets during that time: 14:58:05.546043 fe:ff:ff:ff:ff:ff (oui Unknown) > 09:00:2b:00:00:0f (oui Unknown), ethertype LAT (0x6004), length 81: 0x0000: 2808 0505 0502 131f