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] Re: XEN 3.1: critical bug: vif init failure after creating 1

To: Eric Tessler <maiden1134@xxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: XEN 3.1: critical bug: vif init failure after creating 15-17 VMs (XENBUS: Timeout connecting to device: device/vif)
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 13 Jul 2007 07:29:44 +0100
Cc: "mark.williamson@xxxxxxxxxxxx" <mark.williamson@xxxxxxxxxxxx>
Delivery-date: Thu, 12 Jul 2007 23:24:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <959281.86321.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfFFzNccc6Q8jEKEdyTSAAWy6hiGQ==
Thread-topic: XEN 3.1: critical bug: vif init failure after creating 15-17 VMs (XENBUS: Timeout connecting to device: device/vif)
User-agent: Microsoft-Entourage/11.3.3.061214
Can you try 3.0.4 domU kernel agaianst 3.1 dom0 kernel, and vice versa? Also, turn on debug tracing in Xen (boot options ‘loglvl=all guest_loglvl=all’) and see what appears at the end of ‘xm dmesg’.

 -- Keir


On 13/7/07 02:19, "Eric Tessler" <maiden1134@xxxxxxxxx> wrote:

At the same time in dom0, we see the following error message in /var/log/messages:
  
"vif vif-16-3: 1 mapping shared-frames 2310/2311 port 11"
  
(the error message above means that netif_map failed for some reason in XenBus)
  
 
  
If we repeat this same exact test using XEN 3.0.4, we never have any problems. All vifs in all VMs work correctly. This problem must be specific to XEN 3.1.

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