Bug 1682362

Summary:	[RFE] [machines] Display filesystem guest information/usage
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, mmarusak, qiyuan, xchen
Target Milestone:	rc	Keywords:	FutureFeature, Reopened
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 18:03:23 UTC

Description of problem:

Requesting functionality similar to filesystem cockpit-storaged but for 
guest information.

We should print information on filesystem sizes/usage from within the guest

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

cockpit-machines-184.1-1.el8.noarch

How reproducible:

100%

Steps to Reproduce:
1. Start a VM.
2. Click `Usage` tab
3. Only vRAM and vCPUs info is displayed


Actual results:

No information for filesystem guest usage/sizes is showed in `Usage` tab.


Expected results:

Cockpit UI should show information about guest's filesystem usage.

Comment 3 Katerina Koukiou 2020-11-19 12:59:16 UTC

For this we would need to add a new optional dependency, probably to virt-df tool provided by libguestfs-tools-c.
I would like to know the opinion of @mpitt or @mmarusak before I ack this feature request.

Comment 6 RHEL Program Management 2021-02-01 07:37:12 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 9 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.