Bug 465927 - RFE: virt-manager does not remove custom option "last_started" from domain config file
Summary: RFE: virt-manager does not remove custom option "last_started" from domain co...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-07 07:27 UTC by Ales Zelinka
Modified: 2009-12-14 21:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-07 14:22:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Ales Zelinka 2008-10-07 07:33:02 UTC
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 Berrangé 2008-10-07 13:39:35 UTC
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 14:11:23 UTC
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 Berrangé 2008-10-07 14:22:12 UTC
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.