Displaying 9 results from an estimated 9 matches for "peth3".
Did you mean:
eth3
2008 Jun 21
5
Poor network performance on Dom0 [2.6.18-6-xen-amd64]
...0.080/5068.340/12502.274/4207.494 ms, pipe 13
If i listen for icmp traffic from a physical host that is between Dom0
and the one i''m pinging (i.e., on the same LAN), all icmp requests and
replies come and go timely and in perfect order.
However, when i listen for icmp traffic at Dom0 on peth3 (the
interface that is attached to the LAN switch), i can see the same
delays that show up when pinging.
As you can imagine, this problem does not affect only icmp traffic,
but also every tcp-based service running in Dom0 (such as smtp).
Processor load seems fine, and almost never goes above 0.1...
2008 Feb 01
3
No peth interface for xenbr4 and xenbr5
...peth1
xenbr2 8000.feffffffffff no vif0.2
peth2
xenbr3 8000.feffffffffff no vif0.3
peth3
xenbr4 8000.000d88cd4e6f no eth4
xenbr5 8000.000d88cd4e6e no eth5
It doesn''t create peth4 / peth5 and vif0.4 / vif0.5
Where is my problem ?
Thanks
--
''''~``
( o o...
2007 May 14
3
Number of xenbr''s limited to four on openSuSE 10.2 ?
Hi Group
...
havin'' read whatever I could "google" on this
topic, I didn`t find any
solution:
openSuSE 10.2 (out
of the box), xenkernel, running on HP Proliant DL360G5
(dual
internal networking, plus additional 4-port adapter) gives me eth0 -
eth5, but only peth0 - peth3 (as well as vif0 - vif3 and consequentely
xenbr0 - xenbr3).
I increased the number of
loopback-devices to 64 ... no result
Whenever I try to
"/etc/xen/scripts/network-bridge start vifnum=4" I get a
message regarding to a "nonexisting veth4" ...
What am I missing
Thanks for...
2008 May 21
2
outgoing domu network dies after a while
...peth2
vif1.0
vif2.2
xenbr3 8000.fefffffff003 no vif0.3
peth3
vif2.3
xenbr4 8000.00508bcfd44d no eth4
vif2.4
The kernel and xen running is stock opensuse
# xm info
host : enterprise
release...
2008 Sep 26
0
Centos multiple bridging
...ly things i configured.
[root@sv-173 ~]# brctl show
bridge name bridge id STP enabled interfaces
xenbr1 8000.001a64358c26 no peth1
xenbr2 8000.001a643589d0 no peth2
xenbr3 8000.001a643589d2 no peth3
If i startup a machine like this:
virt-install -f /data/machines/tmpl-centos.img -p -l http://url_to_image/centos/5/64/ --vcpus=1 -r 512 -b xenbr1
I got the following error after retrieving the initrd:
virDomainCreateLinux() failed POST-Operation schlug fehl: xend_post: error from xen daemon:...
2017 Nov 01
2
Centos and xen network bridge issue
...ge" "$@" vifnum=3 netdev=eth0 bridge=xen-dmz1
======
#brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr3 8000.feffffffffff no guestname
vif0.3
peth3
======
#ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:22:19:5E:F9:F8
inet6 addr: fe80::222:19ff:fe5e:f9f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:100820 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors...
2008 Sep 09
14
Problems with bridged networking
...pening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
When I try the network-bridge script by hand I get this message:
> server:/etc/xen/scripts# ./network-bridge netdev=eth3 bridge=xenbr3 start
> ifdown: interface eth3 not configured
> Nothing to flush.
> Waiting for peth3 to negotiate link.
> Ignoring unknown interface xenbr3=xenbr3.
I have this problem also with Xen on a Gentoo box. Here Xen only works up to version 3.1.3.
All other versions don''t work, because of the missing bridges.
I searched for this problem but it seems that I''m the onl...
2011 Nov 18
5
XEN multiple bridge problem - VM won' start!
Hi,
I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.
Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are
2008 May 28
6
SSH ping etc not working between dom0 and domU''s
...NING NOARP MTU:1500 Metric:1
RX packets:556 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44043 (43.0 KiB) TX bytes:561 (561.0 b)
Interrupt:22 Base address:0xe000
peth3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:3007 errors:0 dropped:0 overruns:0 frame:0
TX packets:2197 errors:0 dropped:0 overruns:0 carrier:0...