From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img
Date: Fri, 13 Feb 2009 09:27:24 -0500 [thread overview]
Message-ID: <20090213142724.GK15807@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1234458957.3827.9.camel@TuxBox.mobab>
On Thu, Feb 12, 2009 at 06:15:57PM +0100, D. Schreiber wrote:
> is it possible to add "pipe"-Mode like this?
>
> dd if=/dev/sda | qemu-img convert -f raw - -O qcow2 newImage.img
Does this work:
dd if=/dev/sda | qemu-img convert -f raw <(dd if=/dev/sda) -O qcow2 newImage.img
> I know i can read directly from device, but in some cases (i.e. get data
> from netcat) it would be nice to convert from stdin. Alternative: read
> from fifo.
>
> Another wish is to mount an compressed qcow-Image as loop-Device.
I suspect you have to write a loop device handler for the kernel to
support that. Sounds perfectly doable.
--
Len Sorensen
next prev parent reply other threads:[~2009-02-13 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 17:15 [Qemu-devel] qemu-img D. Schreiber
2009-02-13 10:03 ` Kevin Wolf
2009-02-13 14:27 ` Lennart Sorensen [this message]
2009-02-13 15:52 ` Jamie Lokier
2009-02-13 16:42 ` Lennart Sorensen
2009-02-13 19:09 ` [Qemu-devel] qemu-img D. Schreiber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090213142724.GK15807@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).