Bug 515290

Summary:	RFE: storage: provide API for verification of storage volume integrity (qemu-img check)
Product:	[Community] Virtualization Tools	Reporter:	Daniel Berrangé <berrange>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	crobinso, hbrock, veillard, xen-maint
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-03 15:38:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	568280, 636030

Description Daniel Berrangé 2009-08-03 15:46:15 UTC

Description of problem:
Some storage volume formats such as QEMU have non-trivial metadata  that can become corrupted. libvirt needs to expose a command for verifying integrity of these formats. 

This can be accomplished using the 'qemu-img check' command.


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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2009-08-03 15:59:28 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 5 Dave Allan 2010-05-17 19:10:13 UTC

Moving to 6.1

Comment 7 Cole Robinson 2016-03-20 22:36:35 UTC

*** Bug 636128 has been marked as a duplicate of this bug. ***

Comment 8 Daniel Berrangé 2020-11-03 15:38:59 UTC

Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.