Bug 465927 - RFE: virt-manager does not remove custom option "last_started" from domain config file
RFE: virt-manager does not remove custom option "last_started" from domain co...
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager (Show other bugs)
5.2
All Linux
low Severity medium
: rc
: ---
Assigned To: Daniel Berrange
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-07 03:27 EDT by Ales Zelinka
Modified: 2009-12-14 16:17 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-07 10:22:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Comment 1 Ales Zelinka 2008-10-07 03:33:02 EDT
Please consider including option "last_started" into the list of supported domain
config options (so that it doesn't get removed when configuration changes)

syntax:
last_started = "date" ; date is in format specified by rfc 3339, recognized by date from coreutils package (date --rfc-3339=seconds)

semantics:
date and time when the domain was last started. 

Used for deciding which domain should be stopped to save resources (in environment where domain are not meant to run forever and their owners forget to stop them manually after they're done with them)
Comment 2 Daniel Berrange 2008-10-07 09:39:35 EDT
I don't see any 'last_started' config option in either the RHEL-5 or latest upstream Xen config file handling ? Can you point to the Xen code which is defining this config parameter.
Comment 3 Ales Zelinka 2008-10-07 10:11:23 EDT
There is no such code. This option is recognized and used by our project only
(that's why I call it _custom_ option). What I'd like to achieve is
virt-manager ignoring this option (just like xm does) instead or removing.
Comment 4 Daniel Berrange 2008-10-07 10:22:12 EDT
Closing for same reason as bug 465923. We cannot support use of random invented
config parameters.

Note You need to log in before you can comment on or make changes to this bug.