Ritesh Raj Sarraf
2012-Feb-29 10:53 UTC
[Pkg-xen-devel] Bug#655301: Status check for Wheezy
There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run while xend daemon is active With the above 3 steps: I get xapi back and openxenmanager nicely connect to it. After following this bug report's conversation, I did notice that I do not have anything in /etc/default/xen. lnx200-39:/etc/init.d# cat /etc/default/xen # Configuration for Xen system # ---------------------------- # There exists several tool stacks to configure a Xen system. # ? # Attention: You need to reboot after changing this! TOOLSTACK Also with xapi active and running, I get the following from the toolstack command: lnx200-39:/etc/init.d# /usr/lib/xen-common/bin/xen-toolstack /usr/lib/xen-4.1/bin/xm Now in the xend script, I see: TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) and further... xend_start() { if [ -z "$XEND" ] || [ "$(basename "$TOOLSTACK")" != xm ]; then return 0 fi log_progress_msg "xend" Given that, even with xapi enabled, xen-toolstack reports me that the stack is xm. And TOOLSTACK value from /etc/default/xen is not honored by xend init script. It determines the TOOLSTACK value right in its script. Where do we want to fix it? I have filed bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661687 If that is fixed, as part for xcp post-install, just set /etc/default/xen to xcp and we should be good. Okay??? Let's target it for Wheezy -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120229/28df6fb5/attachment.pgp>
Thomas Goirand
2012-Mar-01 04:35 UTC
[Pkg-xen-devel] Bug#655301: Bug#655301: Status check for Wheezy
On 02/29/2012 06:53 PM, Ritesh Raj Sarraf wrote:> I did > notice that I do not have anything in /etc/default/xen. > > lnx200-39:/etc/init.d# cat /etc/default/xen > # Configuration for Xen system > # ---------------------------- > > # There exists several tool stacks to configure a Xen system. > # ? > # Attention: You need to reboot after changing this! > TOOLSTACKMy understanding is that this should be treated as if you had "xm". I already proposed a patch for this almost a month ago, as well as a debconf solution for it, but it's still sitting in the Xen devel list, with apparently no action from Waldi. If others agree, I can upload a new version of Xen with the fix though, at least for fixing the init.d script (which is the most urgent fix). Here's the list of things that needs to be addressed though: 1- /etc/init.d/xendomains needs to be fixed to understand xl and xe. 2- We need a debconf thing for setting the correct value in /etc/default/xen, with xm, xl or xe as valid values (please, nothing else!!!) 3- /etc/init.d/xend needs to be fixed to start xend only if xm (or an empty value) is set in /etc/default/xen 4- We need xe to check the value of the TOOLSTACK variable (xm and xl are doing that already) 5- We need a wrapper around xm, so that we keep compatibility with older software (IMHO). I've already sent patches for 2- and 3-, which haven't received any critics so far (they did in the past, but it was fixed). It's been a loooong time these are ready. The thing is, I'd like to do more, but I don't want to step on Waldi's feet, and upload without his approval. Using SVN for the packaging of Xen is also a blocker for me (I never really learned it), and I'd like to move Xen packaging to Git, but I never received a green light to start that work (neither a refusal either by the way). What do you think? Should I upload a fix? Should I switch Xen packaging to Git? Thomas
Ian Campbell
2012-Mar-01 07:05 UTC
[Pkg-xen-devel] Bug#655301: Bug#655301: Bug#655301: Status check for Wheezy
On Thu, 2012-03-01 at 12:35 +0800, Thomas Goirand wrote:> If others agree, I can upload a new version of Xen with the fix though, > at least for fixing the init.d script (which is the most urgent fix).An NMU would seem to be the right thing here. Ian. -- Ian Campbell Bathquake, n.: The violent quake that rattles the entire house when the water faucet is turned on to a certain point. -- Rich Hall, "Sniglets"