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] Bug

To: "'Xen Users'" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Bug
From: "Venefax" <venefax@xxxxxxxxx>
Date: Fri, 21 Nov 2008 11:13:45 -0500
Delivery-date: Fri, 21 Nov 2008 08:19:52 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=sCp4Y270lGhFdtHGXvevIFddQc5FipexlK3k2K1WlBQ=; b=oxX08yQ/J3dMwXT51VmPQo6aXn1ebkUMHCsjNIYPT4nk0le/xMtCA/EmtQLUHKpMHb wwY3AF1d5CJWEZdN/uDGEZKCOrb5P5SZGpdxVpLg51P2yGot7sAEDFgor03/RkDiKa6H mIJ5LlHBZRIl1JmsRkwEKjmlAjIPbq61GE5qg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; b=D4eYjdXp1Co/BxeiixAT85DxdsCByEGTtwUyR1rpCr/J+wapWVlQP/CFquApvPtK33 kVxQaA1DPYiEf6v19uOYRvIOSj98HSLYxPjUX/+lhKp2hfaFGFQARwSwaAiO79xDYpc4 id7DE0RE7YVwdq/tJLZalJjt8o/uAnEb9zG0M=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0154FC96@trantor>
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>
References: <1227099936.26845.12.camel@xxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0154FC44@trantor> <1227267195.6701.13.camel@xxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0154FC96@trantor>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclLzR3Vt4gel2W4TiOMUE/NOq/SMwAAySEwAAi/woA=
There is a huge bug in Xen that it is a pain in the neck to solve. In a
production scenario, I set all DomUs to avoid using proc 0 (reserved for
Dom0 exclusively). This is done, only, by using this trick

Xm list --long NameOfDomU > NameOfDomU.sxp

Edit NameOfDomu.sxp and add (cpus 1-X) after the vcpus line.

Xm del NameOfDomU

Xm new -F NameOfDomU.sxp

The problem is that if you reboot the server, and Xen brings up all the VM's
listed in /etc/xen/auto, all this work is lost, it does not get preserved
between reboots. If you have a large amount of DomU's, you need to create
your own starup script that basically goes over the list of DomU's and does
a "xm new -F name.sxp". Xen should preserve those changes automatically
between reboots.

Federico





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