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/
Home Products Support Community News


Re: [Xen-users] Xen 3.4.1-rc7 network problem (vif/tap)

To: xen-users@xxxxxxxxxxxxxxxxxxx, xensource@xxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.4.1-rc7 network problem (vif/tap)
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Wed, 22 Jul 2009 08:57:23 -0700 (PDT)
Delivery-date: Wed, 22 Jul 2009 08:58:55 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1248278243; bh=DpbzhydoRCTqqyTZ4FMV9oJwpSoXbilyv/0skD81ARg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=rBcEWIBGTVCDpGkJsxkQu3ukaLGEZr3ExX7dET0SzOh0Z/9gEikfDY5nva/FQTJzcneDnerNBkldlVNQ3jRRL7WQRWAcJ6gSdE0Mqgs3pCdksKA151K1emHD4eKPRuZJ9Fu89boPJJ6o9fI+JYIncWDUmA6tN3H6quoXLIe2jLo=
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=E2xoBsobc0+LmDL2pzpVKJxGbKerOjJiDcib3MJN+jx07FOlS8LQ8xKGrnAkAzDwD+8IpfSCBLhS16Fx/lmjlxHHj42SfrsrN9jBCuNvMcltgGSlxQ/DGvuvPl/8L0Bejd7rI6zqGCXAkiGeG1qwx6KF8lKoJTxtP2I0oT5vQpU=;
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
> use eth0 as default bridge name ?

I guess , yes.

However,please, post:-

# brctl show
# ifconfig
Content /etc/init.d/networking (how you configure the bridge ?)
Profile of your DomU


--- On Wed, 7/22/09, xensource@xxxxxxxxxx <xensource@xxxxxxxxxx> wrote:

From: xensource@xxxxxxxxxx <xensource@xxxxxxxxxx>
Subject: [Xen-users] Xen 3.4.1-rc7 network problem (vif/tap)
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Wednesday, July 22, 2009, 11:28 AM


I'm now blocked for 2 days on getting the network to work in my domU. Here is
the problem :

The domU refuses to start when a vif is configured. It's just staying paused
for about 1m40s, then the xm create command line give back with an
"Error: Device 0 (vif) could not be connected. Hotplug scripts not working.",
and the domU is destroyed.

Nothing particular in the xend.log, xend-debug.log or qemu-dm-domUname.log.

However, if I manually unpause the domU, and cancel (<CTRL><C>) the xm create
command to avoid the destruction of the domU after the 1m40s timeout, I get a
perfectly working domU with Network. Strangely, the vif network interfaces are
now named tap[domUid].[interface#] (ie tap2.0).

So, my questions :
- Why is there no clear log about vif-bridge script, and how can I debug this
- Why are the interfaces named tapX.X instead of vifX.X ?
- Is there a default name for the bridge interface ? I'm currently using
xenbr0, but I see that some documentations are talking about eth0, should I
use eth0 as default bridge name ?



My config :

root@UbuntuTST-Blade:~# xm info
host                   : UbuntuTST-Blade
release                : 2.6.31-rc3
version                : #8 SMP Mon Jul 20 15:01:16 CEST 2009
machine                : x86_64
nr_cpus                : 16
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2400
hw_caps                :
virt_caps              : hvm
total_memory           : 36853
free_memory            : 1043
node_to_cpu            : node0:0-15
node_to_memory         : node0:1043
xen_major              : 3
xen_minor              : 4
xen_extra              : .1-rc7
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Wed Jul 15 13:26:50 2009 +0100 19696:22ef8e900a6d
cc_compiler            : gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
cc_compile_by          : root
cc_compile_domain      : local.modernprocessing.lu
cc_compile_date        : Thu Jul 16 21:46:26 CEST 2009
xend_config_format     : 4

Xen-users mailing list

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>