From: Sander Eikelenboom <linux@eikelenboom.it>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0 of 5] xl shutdown compatibility with xm
Date: Thu, 25 Oct 2012 17:32:54 +0200 [thread overview]
Message-ID: <394587962.20121025173254@eikelenboom.it> (raw)
In-Reply-To: <20617.22885.630643.630122@mariner.uk.xensource.com>
Thursday, October 25, 2012, 5:23:17 PM, you wrote:
> Sander Eikelenboom writes ("Re: [PATCH 0 of 5] xl shutdown compatibility with xm"):
>>
>> So Ian, what would your prefer ?
>>
>> A) only fix the xendomains init script, since it's automated and a administator can not intervene, for manual usage of xl shutdown keep the current behaviour
>> B) Drop the -F option and let xl shutdown always try the acpi fallback. In this case you can very well turn around IanC's argumentation:
>> An administrator who knows that a domain can't be shutdown with either the pv or acpi fallback just shouldn't try to use xl shutdown manually.
>> (and if he does probably nothing devastating will happen)
>> C) Invert the -F option, to NOT try to use the apci fallback
>>
>> I think option B is acceptable and preferable:
> I agree with you. But I think we need to convince Ian C.
Ok I tried with the reasoning above.
I agree with his argumentation that for domains that do not properly shutdown with pv and acpi fallback intervention by a admin was and is required.
But i try to explain that for this special case it doesn't matter if xl shutdown tries to do the acpi fallback automatically, since this admin shouldn't use xl shutdown on this domain anyway.
> Ian.
next prev parent reply other threads:[~2012-10-25 15:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 10:09 [PATCH 0 of 5] xl shutdown compatibility with xm Ian Campbell
2012-10-15 10:09 ` [PATCH 1 of 5] libxl: propagate user supplied values into event for_user field Ian Campbell
2012-10-17 15:58 ` Ian Jackson
2012-10-15 10:09 ` [PATCH 2 of 5] xl: Introduce xl shutdown --all support for xm compatibility Ian Campbell
2012-10-17 16:03 ` Ian Jackson
2012-10-18 8:24 ` Ian Campbell
2012-10-15 10:09 ` [PATCH 3 of 5] xl: Add --wait and --all to xl reboot Ian Campbell
2012-10-17 16:04 ` Ian Jackson
2012-10-15 10:09 ` [PATCH 4 of 5] xl: allow def_getopt to handle long options Ian Campbell
2012-10-17 16:05 ` Ian Jackson
2012-10-15 10:09 ` [PATCH 5 of 5] xl: Introduce helper macro for option parsing Ian Campbell
2012-10-17 16:13 ` Ian Jackson
2012-10-18 7:42 ` Ian Campbell
2012-10-15 10:32 ` [PATCH 0 of 5] xl shutdown compatibility with xm Sander Eikelenboom
2012-10-15 10:37 ` Ian Campbell
2012-10-15 11:21 ` Sander Eikelenboom
2012-10-15 11:45 ` Ian Campbell
2012-10-16 8:59 ` Sander Eikelenboom
2012-10-16 9:43 ` Ian Campbell
2012-10-16 10:06 ` Sander Eikelenboom
2012-10-19 10:21 ` Ian Jackson
2012-10-25 15:18 ` Sander Eikelenboom
2012-10-25 15:23 ` Ian Jackson
2012-10-25 15:32 ` Sander Eikelenboom [this message]
2012-10-25 15:47 ` Ian Campbell
2012-10-25 15:55 ` Sander Eikelenboom
2012-10-25 15:56 ` Ian Jackson
2012-10-25 17:27 ` Sander Eikelenboom
2012-10-25 15:34 ` Ian Campbell
2012-10-25 15:41 ` Ian Jackson
2012-10-18 8:35 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=394587962.20121025173254@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.