qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: 马磊 <aware.why@gmail.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] reading files from qcow2-formated image disk for windows system
Date: Thu, 10 Jan 2013 13:01:06 +0100	[thread overview]
Message-ID: <20130110120106.GA30946@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CA+ePHTDfd3QLaMQ1DMsAMan0P1M1s6iLePJTFyGL5f-Zr08WaA@mail.gmail.com>

On Wed, Jan 09, 2013 at 03:31:50PM +0800, 马磊 wrote:
> Hi,
> >>     The final effect is as follows:
> >>
> >>
> >> *[malei@xentest-4-1 Fri Dec 28 ~/honeypot/xen/xen-4.1.2]$ qemu-img-xen
> >> cat -f /1/boot.ini ~/vm-check.img *
> >> *[boot loader]*
> >> *timeout=30*
> >> *default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS*
> >> *[operating systems]*
> >> *multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
> >> Professional" /noexecute=optin /fastdetect*
> >>
> >> [malei@xentest-4-1 Fri Dec 28 ~/honeypot/xen/xen-4.1.2]$ qemu-img-xen ls
> >> -l -d /1/ ~/vm-check.img
> >> *【name                 size(bytes) dir?      date
> >>  create-time】*
> >> *AUTOEXEC.BAT 0                file 2010-12-22        17:30:37*
> >> *boot.ini               211                file 2010-12-23
> >>  01:24:41*
> >> *bootfont.bin  322730                file 2004-11-23        20:00:00*
> >> *
> >> *
> >> *
> >> *
> >> *
> >> *
> >>
> >> *As you see above, the patch add two sub-commands for qemu-img-xen:cat
> >> and ls.*
> >> *
> >> *
> >> *For details in the patch, please check the attachment. *
> >>
> >>
> >>
> *Does anyone prefer this feature?!*

This is already possible with http://libguestfs.org/.

Or you can use qemu-nbd to mount the image on the host as explained
here:
http://blog.vmsplice.net/2011/02/how-to-access-virtual-machine-image.html

Although adding file system code to qemu-img integrates this feature
more closely, I think the maintenance overhead and duplication of having
read-only file system implementations is too much.  Therefore, I'm
against merge a patch like this.

Stefan

      parent reply	other threads:[~2013-01-10 12:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09  7:31 [Qemu-devel] [PATCH] reading files from qcow2-formated image disk for windows system 马磊
2013-01-09 21:37 ` Blue Swirl
     [not found]   ` <CA+ePHTC0npDVESeqg4FMEJT68rCvujSufG080mhJ-di3wBBdUQ@mail.gmail.com>
2013-01-10  8:04     ` 马磊
2013-01-10  8:33       ` 陳韋任 (Wei-Ren Chen)
2013-01-10  8:44         ` 马磊
2013-01-10  8:50           ` 陳韋任 (Wei-Ren Chen)
2013-01-10  8:57             ` 马磊
2013-01-10  8:37       ` Paolo Bonzini
     [not found]         ` <CA+ePHTBOKSizctD+MJTaKfa8Ufag=SnGMcWiibVM9E7r7c0UuA@mail.gmail.com>
2013-01-10  8:50           ` 马磊
2013-01-10 12:20   ` Daniel P. Berrange
2013-01-11  3:39     ` 马磊
2013-01-11  6:28       ` Wanlong Gao
2013-01-11  7:27         ` 马磊
2013-01-11  9:26           ` Stefan Hajnoczi
2013-01-12 12:00           ` Blue Swirl
2013-01-14  2:04             ` Wanlong Gao
2013-01-14  9:13             ` Stefan Hajnoczi
2013-01-17 20:22               ` Blue Swirl
2013-01-18 11:54                 ` Stefan Hajnoczi
2013-01-10 12:01 ` Stefan Hajnoczi [this message]

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=20130110120106.GA30946@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=aware.why@gmail.com \
    --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).