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
From:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stephen
Spector
Sent: Friday, November 21, 2008 10:27 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen Documentation
Denny:
I appreciate your comments on the Xen documentation. I
have been looking for people in the community to assist with updating or
creating new documents. I have some people working on various documents but
there is still no formal community effort. I am currently working on the new
Xen Roadmap document and plan to start updating other documents once that is
complete. If you are interested in working on something for the community
please let me know so I can keep track of who is doing what. Thanks.
Stephen Spector
Xen.org Community Manager
stephen.spector@xxxxxxx
(772) 621-5062
BLOG: http://blog.xen.org
------------------------------
Message: 5
Date: Fri, 21 Nov 2008 16:57:21 +0100
From: Denny Schierz <linuxmail@xxxxxxxx>
Subject: [Xen-users] Xen documentation are still too old
To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Message-ID: <1227283041.27101.30.camel@kusanagi>
Content-Type: text/plain; charset="us-ascii"
hi,
i'm a real Xen user since version 2.0.7 and i still believe
on the power and charme from Xen. I used Xen for my costumers, for my own and
I'm proud to tell everybody about Xen, what they can do with the hypervisor and
i've written severals German HOWTOs. But, where the sun is, the shadow isn't
far away: Xen lacks absolutely on actual docs. The ManPages are still not
updated (many FIXME), not all parameters are listed in (5), for example
cpu_cap and cpu_weight? How can i define it in a DomU
config? (i know it, now)
another example:
"dom0-min-mem" is listed, but where is
"enable-dom0-ballooning yes" ?
Take a look, what you have with "xm help" and
what you get in the manpage.
At this time, i have to read the sourcecode, to know,
what this means.
Xen has so many features, but without good manpages,
nobody knows about them. Also the ("make -C docs") the documentation
in the Xen source code, is more for developers (and still to old too), than for
new users.
They better searching with Google for HowTos.
So, why it is so hard to take some time for a good documentation,
instead of developing new features, where nobody knows,that they exists, if
they don't read the source code or the mailinglists?
cu denny
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil Url
: http://lists.xensource.com/archives/html/xen-users/attachments/20081121/2622d965/attachment.bin
------------------------------
