[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Bug


  • To: "'Xen Users'" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Venefax" <venefax@xxxxxxxxx>
  • Date: Fri, 21 Nov 2008 11:13:45 -0500
  • Delivery-date: Fri, 21 Nov 2008 08:19:52 -0800
  • 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=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.