qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ben Taylor <sol10x86@cox.net>
To: qemu-devel@nongnu.org
Cc: Francois Visconte <francois.visconte@inria.fr>
Subject: Re: [Qemu-devel] qemu-img qcow and raw format
Date: Thu, 12 Apr 2007 11:19:41 -0400	[thread overview]
Message-ID: <5729339.1176391181022.JavaMail.root@eastrmwml05.mgt.cox.net> (raw)


---- Francois Visconte <francois.visconte@inria.fr> wrote: 
> Hello,
> 
> I'm currently developing an OS deployment tool similar to G4U (ghost for 
> unix).
> This is a very basic tool
>   - boot an initrd
>   - configure network
>   - ssh deployment-server "cat image.dd"  > /dev/sda
>   - reboot
> 
> 
> I'm using qemu to test my initrd and deployment tool and i would like 
> replace my raw image format with qcow images (size/compression and crypto)
> 
>   - ssh deployment-server "cat image.qcow" | qemu-img - -O raw /dev/sda
> 
> The problem is qemu-img can't read from stdin, so i tried :
> 
>   - mkfifo deploy-in.fifo
>   - qemu-img convert deploy-in.fifo -O raw /dev/sda
>   - ssh deployment-server "cat image.qcow" > deploy-in.fifo
>     qemu-img: Could not open 'deploy-in.fifo'

I have not looked at the code in qemu-img (and the associated 
routines).  It appears that qemu-img is probably looking for
a file handle and not a named pipe. Either that, or you need
to shove the ssh command in the background before the 
qemu-img command so qemu-img has a chance to
start processing the data.  It's not clear whether or not
qemu-img is seeing an "empty file" because there's no
data on the pipe, or it can't read from the pipe.

Ben

             reply	other threads:[~2007-04-12 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 15:19 Ben Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-12  8:09 [Qemu-devel] qemu-img qcow and raw format Francois Visconte
2007-04-12 10:17 ` Gildas
2007-04-12 10:51   ` Francois Visconte
2007-04-12 10:54 ` Daniel Silverstone

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=5729339.1176391181022.JavaMail.root@eastrmwml05.mgt.cox.net \
    --to=sol10x86@cox.net \
    --cc=francois.visconte@inria.fr \
    --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).