Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The virsh command to start a guest instance is 'start', to stop the command is 'shutdown' and to restart the command is 'reboot'.
Unless there is a strong reason why these terms were chosen it seems that it would present a more consistent user interface to either use the commands 'start, 'stop' and 'restart' OR 'boot', shutdown' and 'reboot'. The present admixture of dissimilar terms places an easily avoidable intellectual burden on operators which serves no evident useful purpose.
My own preference is that all six commands should be provided and that 'boot' be aliased to 'start', 'restart' to 'reboot', and 'stop' to 'shutdown'. This approach would avoid impacting those who are already familiar with the existing scheme.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
The patches are trivial, and only impact virsh. Done for upstream with:
commit 5f63a5cb42642f945696c51bbce7fdc160325510
Author: Eric Blake <eblake>
Date: Tue Nov 6 08:09:32 2012 -0700
virsh: document which term is older
Make it clear that the alternate terms have no difference except
for length of time they were supported.
* tools/virsh.pod (start, shutdown, reboot): More documentation.
commit ff86b0c97b0525a2cd26048a0dbf16e600aaeb7b
Author: Eric Blake <eblake>
Date: Mon Nov 5 12:54:59 2012 -0700
virsh: add aliases 'boot', 'stop', and 'restart'
https://bugzilla.redhat.com/show_bug.cgi?id=873344 suggested that
the grouping 'boot', 'shutdown', 'reboot'; as well as the grouping
'start', 'stop', 'restart'; might be easier to remember than the
current mix of 'start', 'shutdown', 'reboot'.
Also, touch up the wording of 'reboot' to be more accurate.
* tools/virsh-domain.c (domManagementCmds): Add other command names.
* tools/virsh.pod (start, shutdown, reboot): Document the aliases.
Moving out of POST - upstream is seriously considering reverting these patches, in which case this bug should be closed as WONTFIX. Final determination will be made by the time upstream releases 1.0.1.
Retitling. Upstream rejected the patches in comment 4. All upstream is willing to support is the creation of virsh aliases, but no one has started work on that yet.