WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Fwd: Strange network problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Fwd: Strange network problem
From: Benjamin Schweikert <b.schweikert@xxxxxxxxxxxxxx>
Date: Tue, 04 May 2010 18:03:06 +0200
Delivery-date: Tue, 04 May 2010 09:06:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type; bh=TzZ9Uaby5i0J9t2Vom041qaux5vXc0yEp8HyjWTj+f4=; b=iCii5boNZwVH9hk3FZSiJ27egMlm8dsvw07ApzHK61u2HJKk8jXCVpBPd74uplQxmw s0k4Ck1XTou+E4F1DyUqpcaXQFSo8HtZFbGs69F43xwBdhLWcVEZRgXipC9g+49vHLFF pGkVDmLYFUyf2LD8ENL0Z5RWjJ9Fl6+XWIzI0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; b=SW740dRmeY8OitRsdHMqIofDwCLIgwLQEbw91DoGfx1m8F+0c5ai5c0NdY8Rr490iU KmL1a/UWdeZ0gv1EjEh4ZjeWmQZR7iZcq78W16XOd5KFfrSR8LTZ4zhW4++6X3jTe8CU UQyQ5F4KCapzSc0LzG17zcrMMnrFLEZ8hjR6s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100426 Thunderbird/3.0.4
Problem still not solved, or any idea whats wrong.

here are some msgs:
device vif1.0 entered promiscuous mode
  alloc irq_desc for 1246 on node 0
  alloc kstat_irqs on node 0
brI: port 2(vif1.0) entering learning state
device vif1.1 entered promiscuous mode
brE: port 2(vif1.1) entering learning state
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
brI: port 2(vif1.0) entering forwarding state
brE: port 2(vif1.1) entering forwarding state
blkback: ring-ref 8, event-channel 10, protocol 2 (x86_32-abi)
  alloc irq_desc for 1245 on node 0
  alloc kstat_irqs on node 0
blkback: ring-ref 9, event-channel 11, protocol 2 (x86_32-abi)
  alloc irq_desc for 1244 on node 0
  alloc kstat_irqs on node 0
blkback: ring-ref 10, event-channel 12, protocol 2 (x86_32-abi)
  alloc irq_desc for 1243 on node 0
  alloc kstat_irqs on node 0
blkback: ring-ref 11, event-channel 13, protocol 2 (x86_32-abi)
  alloc irq_desc for 1242 on node 0
  alloc kstat_irqs on node 0
  alloc irq_desc for 1241 on node 0
  alloc kstat_irqs on node 0
  alloc irq_desc for 1240 on node 0
  alloc kstat_irqs on node 0
nfsd: last server has exited, flushing export cache
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
brE: port 2(vif1.1) entering disabled state
brE: port 2(vif1.1) entering disabled state
brI: port 2(vif1.0) entering disabled state
brI: port 2(vif1.0) entering disabled state
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
device vif2.0 entered promiscuous mode
brI: port 2(vif2.0) entering learning state
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
device vif2.1 entered promiscuous mode
brE: port 2(vif2.1) entering learning state
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
brI: port 2(vif2.0) entering forwarding state
brE: port 2(vif2.1) entering forwarding state
blkback: ring-ref 8, event-channel 10, protocol 2 (x86_32-abi)
blkback: ring-ref 9, event-channel 11, protocol 2 (x86_32-abi)
blkback: ring-ref 10, event-channel 12, protocol 2 (x86_32-abi)
blkback: ring-ref 11, event-channel 13, protocol 2 (x86_32-abi)



and when i start xend i get the following:

blktapctrl_linux.c:92: couldnt find device number for blktap0
blktapctrl.c:859:couldnt open blktap interface
blktapctrl.c:922:unable to start blktapctrl


any ideas?

Ben

-------- Original-Nachricht --------
Betreff: Strange network problem
Datum: Mon, 03 May 2010 08:22:02 +0200
Von: Benjamin Schweikert <b.schweikert@xxxxxxxxxxxxxx>
An: xen-users@xxxxxxxxxxxxxxxxxxx


Hi,
I am using the following setup:
Dom0:
Gentoo 64 Bit with a 2.6.33.2 Pv ops kernel
cpu: amd athlon II 605e
bridged network.

As domu I want to use ipfire which has a pv xen kernel based on the 
opensuse xen patches (like andy lyon does).
If I use an old dom0 xen kernel with xen 3.4.x everything is working. 
But if I use a new dom0 kernel (different xen versions doesn't change 
anything)
networking is not really working. From domu and dom0 ping does work, but 
i am unable to sync the portage tree of the dom0. From my lan i am unable
to ping. But I am able to surf from the lan (for example icq, 
jabber,.imap,.. doesnt connect, too). If i start the domu as a hvm 
domain everything is working. so i think, the bridges are working. Any 
ideas whats going wrong?

Ben
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>