similar to: latest xen-unstable veth devices missing

-------- Original Message -------- Subject: Re: [Xen-users] network-bridge does not create veth or peth devices Date: Wed, 28 Nov 2007 14:42:25 +0100 From: Ingard Mevåg <ingardm@startsiden.no> Organization: ABCStartsiden To: Luciano Rocha <strange@nsk.no-ip.org> References: <474D6492.5030807@startsiden.no> <20071128130205.GA1838@bit.office.eurotux.com> Luciano Rocha

Hi I am trying to install xen (64bit) on a Dell PowerEdge 2900. The installation process was something like the following: ----- apt-get install iproute bridge-utils python-twisted binutils zlib1g-dev python-dev transfig bzip2 screen ssh debootstrap libcurl3-dev libncurses5-dev x-dev build-essential gettext python-pyopenssl python-pam python-xml latex tetex-extra tetex-base

Hi I am using oprofile 0.9.3 on xen cs 16540 on an Intel system. When I look at the top "hot" functions, I see p2m_change_type being one of the top function in xen-syms. This function is only in the svm (AMD) code and should not appear on an Intel system. I see that this function is not being clled at all when I am running my apps as I have put printk in the functions and they do

Hi, Thanks or all the suggestions. The problem was the lack of hotplug support! The problem was solved by a reinstall of the native linux (RHEL4) with selecting all packages. I had initially chosen some packages and I believe hotplug support was left off (don''t know which package it belonged to. Regards - Padma -------------- Original message ---------------------- From: Nivedita

Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where

Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where

Hi, I have seen many posts regarding this but have not found the soultion. So please cna someone shed some light on this Thanks - padma I get this error when I do try to create a domU guest (xen 3.0.0, 2.6.12.6). The vif is set to vif = [ '' mac=aa:00:00:00:11, bridge=xenbr0'' ] and a "brctl show" shows xenbr0 8000,fefffffff interfaces vif0.0 peth0 Xend.log

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi all ! It seems, that new kernel 2.6.24 offers new feature, that enables me to create pair of virtual Ethernet devices and connect them to each other. This module is called "VETH". However, I have not found any userspace app to use this feature. Please help ! -- -Alexey Eremenko "Technologov"

> On Friday 02 September 2005 17:58, Patrick O''Rourke wrote: > > The network device on our hardware uses a rather large MTU (~16k), but I > > noticed that when setting up bridging, the MTU for the bridge and veth > > device is set to 1500. Trying to set the MTU on the bridge, or eth > > device to match that of the peth is unsuccessful: > > > >

Hi All I am using xen 3.3.0 version and I want to start network virtual interface on Dom U by using the following command # xend start *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is

Hello, I use xen for a few months now and I upgraded to opensuse 10.3 with xen 3.1 (64bit versions) recently. Everything works fine, but there is a problem when I change xend-config.sxp to use my own network script (it''s slightly modified version of network-virtual scripts from http://en.opensuse.org/Xen3_yet_another_Virtual_Network_Concept ) instead of default network-bridge script.

I have pulled a recent (today''s) clone of staging/xen-unstable.hg and I get a failure when trying to create a domain with xend/xm. The failure I get is: Error: (''<domain GUID>'', ''VM_metrics'') I have traced the problem down to where the pci = [ ''02:00.0'' ] parameter (which is the value in my case) from my configuration

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

If I start a domain with a number of vbd devices, it''s a crap shoot if they''ll all show up in the domU''s /proc/partitions. I''ll eventually see all the devices if I keep rebooting the domU. The value of /local/domain/$DOMID/device/vbd/*/state are all 1 for the missing devices, and 4 for the ones that show up. When it works: domU:~# cat /proc/partitions

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for

Hi, I have a problem with networking under XEN, I hope someone can help me out. The problem is that after some time (a day or so) the network suddenly stops working, and it takes some waiting and/or a reboot to fix this. I''m running XEN 3.1.0-rc7 on an Intel Core2 (x86_64). It''s a Fedora 8 system, with the following packages: o Xen version 3.1.0-rc7-2950.fc8

xend cannot start with error: ...ption starting xend: ''module'' object has no attribute ''VIRQ_DOM_EXC'' Traceback (most recent call last): File "/usr/lib/python2.3/xen/xend/server/SrvDaemon.py", line 304, in run self.createFactories() File "/usr/lib/python2.3/xen/xend/server/SrvDaemon.py", line 319, in createFactories

Missed this in the [patch] state. If we are gonna do this can we get a timestamp on every open? or every message? -JX On Oct 25, 2006, at 5:30 AM, Xen staging patchbot-unstable wrote: > # HG changeset patch > # User kfraser@localhost.localdomain > # Date 1161768423 -3600 > # Node ID 0c7923eb6b9846c92f1c15486e06ee9745bcf676 > # Parent 410df40afc014555ce7bfcad2852de9e6d0425f0