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-ia64-devel

[Xen-ia64-devel] [Bug: 736]Creating VTI domain might meet "Cannot alloca

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] [Bug: 736]Creating VTI domain might meet "Cannot allocate memory"
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Fri, 11 Aug 2006 14:55:11 +0800
Delivery-date: Thu, 10 Aug 2006 23:56:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aca9ExanGnO8GRYWQemPU1p6uK9x6A==
Thread-topic: [Bug: 736]Creating VTI domain might meet "Cannot allocate memory"
Hi all,

I just reported a bug about creating VTI domain failure issue.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=736

This issue is very strange. Sometimes xm report can not allocate memory for my 
VTI domain, after I do a lot of creating and destroy operations. 

But if I try several times "xm create VTI", finally VTI domain can be created 
again. 

Will any kind volunteer fix this issue? :)

Best Regards,
Yongkang (Kangkang) 永康

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

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