search for: pethx

Hi all, Up until now, we''ve been using Xen 3.0 on CentOS 5.x. Under this setup, dom0 was given a virtual ''ethX'' with the original ''ethX'' (now ''pethX'') IP address. Under this older config, neither ''pethX'' or ''xenbrX'' had an IP address. The logic was to keep traffic from the domU''s, through the bridge and out ''pethX'' without dom0 seeing anything. This is particularly usefu...

...s detect an network adapter, was putting: vif = [''type=ioemu''] I also tryied: vif = [''type=ioemu, bridge=xenbr0''] Could never ping a external from DomU!! What I know: - the ethX device is a logical device and the physical device is renamed to pethX; - the vifX.Y devices are linked with ethY from DomX (ie.: vif1.0 <-> Dom1 eth0); - there is also a vethX ... What configuration I have to do on Dom0? What configuration I have to do on DomU? When rebooting I have always need to do ''ifconfig ethX up'' !!! thanx...

...so that might run it, so I assume >> it's xend doing that, but there's no error in any log. > >Kai, > >Snooping around I found this in /etc/xen/qemu-ifup: > ># ># Old style bridge setup with netloop, used to have a bridge name ># of xenbrX, enslaving pethX and vif0.X, and then configuring ># eth0. ># ># New style bridge setup does not use netloop, so the bridge name ># is ethX and the physical device is enslaved pethX ># ># So if... ># ># - User asks for xenbrX ># - AND xenbrX doesn't exist ># - AND t...

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0)

Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge

Hi Is there anyone who has successfully resolved the low throughput problem in Guest communication. I am using Xen3.4.1 with PV os kernel 2.6.30-rc6-tip On fedora11. While running netperf benchmark on guests throughput results are very low DomU to DomU    0.29 Mbps Why is it so? What would be the problem. Is there any issue with fc11 platform? Regards, Fasiha Ashraf Add whatever you love

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

...t;$bridge" ] then bridge=$(brctl show | cut -d " " -f 2 | cut -f 1) if [ -z "$bridge" ] then fatal "Could not find bridge, and none was specified" fi else # # Old style bridge setup with netloop, used to have a bridge name # of xenbrX, enslaving pethX and vif0.X, and then configuring # eth0. # # New style bridge setup does not use netloop, so the bridge name # is ethX and the physical device is enslaved pethX # # So if... # # - User asks for xenbrX # - AND xenbrX doesn't exist # - AND there is a ethX device which is...

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

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, Currently we have severe problem and are struggling to investigate it. The problem is data broken. Reproduce pocess is following, 0. test FTP function between guest domain and FTP client(other PC). 1. put data from FTP client to guest domain. 2. get data from guest domain to FTP client. 3. compare put data and get data on FTP client. 4. repeat process from step1 to step3.

...d running, and it has an ethernet device, but there''s never any response. After digging through the system for a while and comparing it to another system I have that works, I discovered that the bridge appears to only be partially set up on boot. Specifically, it''s empty, and the pethX (in my case peth1) device is missing entirely. I have dredged through the network-bridge script and run through as much of it as I can in my head, it *seems* like the situation I''m encountering should be impossible unless something is failing in an odd manner in the middle of the script....

When I try to create a PV domU, the VM starts up and I can access it through "xm console <id>", but when I try to connect to it through VNC, the port just hangs. I''ve tried using RealVNC and TightVNC, and also tried on Linux and Windows. All that happens on the client is that it says that the connection has established, and hangs there. I''ve tried running