Bug 1680679 - [RFE] [machines] Allow to save VM's memory and CPU state - managedsave
Summary: [RFE] [machines] Allow to save VM's memory and CPU state - managedsave
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Pitt
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-25 14:05 UTC by Javier Coscia
Modified: 2023-07-20 06:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-16 07:27:20 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-94853 0 None None None 2021-09-18 08:02:15 UTC
Red Hat Knowledge Base (Solution) 3937681 0 Supportability None Allow to save VM's memory and CPU state - managedsave 2019-02-25 14:18:33 UTC

Description Javier Coscia 2019-02-25 14:05:33 UTC 
Description of problem:

Currently it is not possible to save VM's memory and CPU state to later 
start/restore it from that state.

`managedsave` function in virsh or `save` in virt-manager

Version-Release number of selected component (if applicable):

cockpit-machines-184.1-1.el8.noarch

How reproducible:

100%

Steps to Reproduce:
1. Have a running linux VM.
2. Search for a `Save` or `ManagedSave` button in the cockpit UI.
3. Not possible to use this feature.

Actual results:

There's no current way to save VM's state through cockpit UI

Expected results:

User should be able to use this functionality which is present in 
virt-manager and virsh.
Comment 4 RHEL Program Management 2021-02-01 07:33:16 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 7 RHEL Program Management 2022-03-16 07:27:20 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.