Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Useful metadata about VMs #2388

Open
4 tasks
rootkovska opened this issue Oct 21, 2016 · 4 comments
Open
4 tasks

Useful metadata about VMs #2388

rootkovska opened this issue Oct 21, 2016 · 4 comments
Labels
C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@rootkovska
Copy link
Member

rootkovska commented Oct 21, 2016

It would be useful if core maintained (and exposed e.g. through qvm-prefs) a few metadata about each of the VMs, such as:

  • Has the VM ever been connected to network (sticky bit)
  • Creation time
  • Last run time
  • User-provided optional custom description

IIRC there was a ticket mentioning at least some of the above, but can't find it easily.

@rootkovska rootkovska added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. C: core labels Oct 21, 2016
@rootkovska rootkovska added this to the Release 4.1 milestone Oct 21, 2016
@woju woju self-assigned this Oct 21, 2016
@woju
Copy link
Member

woju commented Oct 21, 2016

There are several:

Creation time and last run was requested on ML, can't find reference.

@woju woju added the T: task Type: task. An action item that is neither a bug nor an enhancement. label Oct 21, 2016
@Rudd-O
Copy link

Rudd-O commented Oct 28, 2016

Please add a feature / metadata entry for "automatically started by user execution request" or "automatically started on boot" or "manually started with qvm-start". This'll make it easier to do things like upgrade VMs and the shut them down if the VMs have been instantiated by the upgrade process.

marmarek added a commit to marmarek/qubes-core-admin-client that referenced this issue Jun 19, 2017
marmarek added a commit to marmarek/qubes-core-admin-client that referenced this issue Jun 19, 2017
marmarek added a commit to marmarek/qubes-core-admin-client that referenced this issue Jun 19, 2017
marmarek added a commit to marmarek/qubes-core-admin-client that referenced this issue Jun 19, 2017
@woju
Copy link
Member

woju commented Apr 18, 2018

This issue is abandoned, so I'm going to close it. If that's a mistake, feel free to reopen.
@marmarek @andrewdavidwong

@woju woju closed this as completed Apr 18, 2018
@marmarek
Copy link
Member

Oh, I think this is still useful, maybe as an core extension.

@marmarek marmarek reopened this Apr 18, 2018
@andrewdavidwong andrewdavidwong added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. and removed T: task Type: task. An action item that is neither a bug nor an enhancement. labels Feb 5, 2022
@andrewdavidwong andrewdavidwong removed this from the Release 4.2 milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

5 participants