search for: peth0

...e(s) Domain-0 0 3919 2 r----- 706.5 [root@wing godwing]# /usr/sbin/xm create -c /etc/xen/balthasar Using config file "/etc/xen/balthasar". Error: Boot loader didn''t return any data! While rebooting : xend : nothing to flush... waiting peth0 to negotiate link ? And I find no veth0, veth1, vif[x].[x] Following I attach the results, thus you might examine: [root@wing godwing]# /usr/sbin/brctl show bridge name bridge id STP enabled interfaces eth0 8000.00173f0a7a26 no peth0 eth1...

...age: 196299 Jun 27 07:36:56 xmao kernel: ------------[ cut here ]------------ 196300 Jun 27 07:36:56 xmao kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x105/0x16a() 196301 Jun 27 07:36:56 xmao kernel: Hardware name: Tecal RH2285 196302 Jun 27 07:36:56 xmao kernel: NETDEV WATCHDOG: peth0 (bnx2): transmit queue 0 timed out 196303 Jun 27 07:36:56 xmao kernel: Modules linked in: iptable_filter nfs fscache nfs_acl auth_rpcgss bridge stp llc autofs4 ipmi_devintf ipmi_si ipm i_msghandler lockd sunrpc ipv6 xenfs dm_multipath fu...

...have XP running. Ultimately I would really like you to show me the documentation that tells me how to fix this. I am pretty sure it exists but my googling has not been effective in this area. Some things that seem dubious to me are the fact that eth0(the bridge) looks like an exact clone of peth0 from ifconfig. I would have expected them to have different HWaddr and at the very least different inet addr. Another dubious thing is the routing table, double routes one for each interface. Shouldn''t that confuse the heck out of the OS? Lastly I have no clue why the next line is...

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 still seem to work. So my questio...

...lowing packages: o Xen version 3.1.0-rc7-2950.fc8 (kojibuilder@(none)) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) Tue Oct 23 12:21:08 EDT 2007 o xen-3.1.0-13.fc8 o kernel-xen-2.6.21-2950.fc8 The error message the kernel gives me is the following: Nov 16 14:38:31 xen2 kernel: NETDEV WATCHDOG: peth0: transmit timed out Nov 16 14:38:31 xen2 kernel: sky2 peth0: tx timeout Nov 16 14:38:31 xen2 kernel: sky2 peth0: disabling interface Nov 16 14:38:31 xen2 kernel: sky2 peth0: enabling interface Nov 16 14:38:31 xen2 kernel: sky2 peth0: ram buffer 48K Nov 16 14:38:31 xen2 kernel: eth0: port 1(peth0) e...

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

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... | 7.1 MB 00:01 POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 0 (vi f) could not be connected. Hotplug script...

I''m having trouble getting ingress policing to work on a bridged device. The bridge contains several interfaces: peth0, vif0.0, vif[1-7]0.1, vif[25].1 . (This is under xen, in case the vif''s didn''t give that away, so peth0 is renamed eth0.) The tc rules I have are: tc qdisc del dev peth0 root tc qdisc del dev peth0 ingress handle ffff: tc qdisc add dev peth0 root handle 1: htb default 1 tc cla...

...(XendCPUPool:747) recreate_active_pools check the /var/log/messages: 9690 Apr 26 10:16:46 houyi-vm12 smbd[3981]: Unable to connect to CUPS server localhost:631 - Connection refused 9691 Apr 26 10:17:11 houyi-vm12 kernel: Bridge firewalling registered 9692 Apr 26 10:17:11 houyi-vm12 kernel: bnx2: peth0: using MSIX 9693 Apr 26 10:17:11 houyi-vm12 syslogd: sendto: Network is unreachable 9694 Apr 26 10:17:11 houyi-vm12 kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready 9695 Apr 26 10:17:14 houyi-vm12 kernel: bnx2: peth0 NIC Copper Link is Up, 1000 Mbps full duplex 9696 Apr 26 10:17:14 houyi-vm12...

...addr:127.0.0.1 Mask:255.0.0.0 After starting xend i have some ungly interfaces: eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF...

...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 enabled interfaces eth0 8000.001d609d5af4 no peth0 vif1.0 "ip address" in Dom0: 1: lo: 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 brd 127.255.255.255 scope host lo inet 127.0.0.2/8 brd 127.255.255....

...n. However, both of the bridges are configured with the same hardware address: xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF I think this is causing the following messages to show up on logs: Jul 9 17:15:25 kernel: peth0: received packet with own address as source address Jul 9 17:19:38 kernel: peth0: received packet with own address as source address Jul 9 17:19:38 kernel: peth0: received packet with own address as source address Jul 9 17:19:42 kernel: peth0: received packet with own address as source a...

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? It''s throwing my thinking off, because in all other Linux distros, I''ve always gone for the eth0 device when needing to do networking,...

...32.18 from 4.0.1''s `make prep-kernels` Below is a log, the things i''m concerned with is the XENBUS errors and the deprecated iptables stuff. Any ideas whats going on here? ---------------------------------------------------- Bridge firewalling registered ADDRCONF(NETDEV_UP): peth0: link is not ready igb: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready device peth0 entered promiscuous mode eth0: port 1(peth0) entering forwarding state XENBUS: Unable to read cpu state XENBUS: Unable to read cpu state XENBUS: Unabl...

Hello, my server has massive problems with my NIC. I got: "Detected Tx Unit Hang". At the moment I use 2.6.31 from Jeremy, does anyone know if it''s fixed in 2.6.32 or newer tree? Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i noticed that the ingress qdisc is not working properly anymore in 3.0.4-1 (back in 3.0.2 the ingress qdisc was working for me): Install the ingress qdisc to peth0: # tc add qdisc dev peth0 ingress ... generate some traffic ... # tc -s qdisc show dev peth0 qdisc pfifo_fast 0: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 324884 bytes 1749 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 qdisc ingress ffff: --------...

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal Hi, I am getting the following message in dmesg about twice a minute: peth0: received packet with own address as source address A patch is available in the upstream BTS: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339 -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /b...

...and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips? Google is failing me, im not sure what to even search for other than "xen Attempting to checksum a non-TCP/UDP packet". Im wondering if this has something to do with why my guests were seeming to have network timeout/freezing problems, I...

...and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips? Google is failing me, im not sure what to even search for other than "xen Attempting to checksum a non-TCP/UDP packet". Im wondering if this has something to do with why my guests were seeming to have network timeout/freezing problems, I...

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel