Bug 835480

Summary:	RFE: virsh: support '-' as placeholder for /dev/stdin or /dev/stdout
Product:	[Community] Virtualization Tools	Reporter:	David Jaša <djasa>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	crobinso, jrubcop
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-03 16:35:07 UTC	Type:	Bug
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:	636082

Description David Jaša 2012-06-26 10:04:05 UTC

Description of problem:
In unix command line world, it's quite common to use '-' sign as a placeholder for reading from standard input or writing to standard output. Virsh doesn't support this use so some commands using virsh are uglier than they need be:

virsh dumpxml <domain> | virsh domxml-to-native qemu-argv /dev/stdin
vs.
virsh dumpxml <domain> | virsh domxml-to-native qemu-argv -


Version-Release number of selected component (if applicable):
libvirt-0.9.10-21.el6.x86_64

How reproducible:


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


Expected results:


Additional info:

Comment 1 Jonathan Rubenstein 2020-02-01 06:56:09 UTC

To be explicit, '-' shouldn't be redirected to '/dev/std{in,out,err}' or `/dev/fd/{0,1,2}` but should cause virsh to read from stdin or write to stdout.
This is reasonably assumed, but is being stated for the record.

Comment 2 Daniel Berrangé 2020-11-03 16:35:07 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.