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

Re: [Xen-users] Re: XEN 3.1: critical bug: vif init failure after creati

To: Thomas Ronner <thomas@xxxxxxxx>
Subject: Re: [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: Wed, 25 Jul 2007 09:15:15 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 25 Jul 2007 01:13:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46A705F5.4000107@xxxxxxxx>
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: AcfOk+3jLKpEajqHEdyM2wAX8io7RQ==
Thread-topic: [Xen-users] Re: 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
On 25/7/07 09:12, "Thomas Ronner" <thomas@xxxxxxxx> wrote:

>> The driver in domU. If you never saw this problem with Xen2, then that's
>> because the domU kernels you used at that time did not have the normal SCSI
>> subsystem compiled into them.
>>   
> Other domUs with similar configs and the same kernel run fine. It was
> only until I started the 7th domU the problems begun.

I have to be skeptical about that. If you run the same kernel and basically
same configuration, this problem should occur deterministically for all such
domains. So something must be different in domUs 1 thru 6!

 -- Keir


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>