Bug 1680679

Summary:	[RFE] [machines] Allow to save VM's memory and CPU state - managedsave
Product:	Red Hat Enterprise Linux 8	Reporter:	Javier Coscia <jcoscia>
Component:	cockpit-appstream	Assignee:	Martin Pitt <mpitt>
Status:	NEW ---	QA Contact:	YunmingYang <yunyang>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	kkoukiou, qiyuan, xchen
Target Milestone:	rc	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-16 07:27:20 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.