All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, 马磊 <aware.why@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] reading files from qcow2-formated image disk for windows system
Date: Thu, 10 Jan 2013 12:20:29 +0000	[thread overview]
Message-ID: <20130110122029.GN6021@redhat.com> (raw)
In-Reply-To: <CAAu8pHs3ve0JA3eavYXevdX5hGUs9EgV-PaPFuTUFN08iVjjMQ@mail.gmail.com>

On Wed, Jan 09, 2013 at 09:37:54PM +0000, Blue Swirl wrote:
> On Wed, Jan 9, 2013 at 7:31 AM, 马磊 <aware.why@gmail.com> 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?!
> 
> Nice feature, but this approach would just clutter QEMU and give only
> readonly FAT or NTFS support. I think a more generally useful approach
> would be to use NBD or iSCSI to export the block device data from the
> image file (qemu-nbd already exists) and then make a tool that uses
> some combination of NBD/iSCSI client, all GRUB file systems and FUSE
> or other user space methods to access the contents of the filesystem.
> Probably also UML with a simple guest agent could provide read/write
> access to any file system that Linux supports.

The latter is what libguestfs already provides. It boots a Linux kernel
and mini initrd containing a guest agent, to provide APIs to do arbitrary
manipulation of guest OS images.

The reason libguestfs used a linux guest was precisely to avoid having
to re-implement drivers for every filesystem in existance like this
patch is trying todo.

I don't think QEMU wants to be in the business of maintaining filesystem
drivers, so I'd reject this proposed patch.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  parent reply	other threads:[~2013-01-10 13:17 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 [this message]
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

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=20130110122029.GN6021@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=aware.why@gmail.com \
    --cc=blauwirbel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.