[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Xen startup takes long time. network-bridge ownership lock

  • To: XenUsers <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: jd <jdsw2002@xxxxxxxxx>
  • Date: Wed, 30 Jun 2010 17:59:14 -0700 (PDT)
  • Delivery-date: Wed, 30 Jun 2010 18:02:38 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=dys0smACueH1kCp3tl5W7JIt9XbiXwoq/kmxIoBwiX+HNzq0hewCyIK8IAV3x4WD/zTMycWeJUyCNYrdlmPMBf0NCAjKM6xFJi4Jz0Cv7141DFt9r6I5H1ia9kP14Xx4YcAL65n+nIB9gJfbPp7fi99ncPjMcvizEXvvayhq8H4=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi guys

I have two nics and have created a custom script to create bridge. It is taking 
long time to bring up the interfaces while booting. 

The platform is SLES 11 SP1.

dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

I put -x in the network-bridge and it seems to be waiting for some lock 
ownership. And this process is repeated for both interfaces.

log is attached. Any pointers are appreciated.



Attachment: boot.msg
Description: Binary data

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.