qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Beregszaszi <alex@fsn.hu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add support for VDI images
Date: Fri, 27 Jul 2007 02:25:25 +0200	[thread overview]
Message-ID: <1185495926.22903.22.camel@localhost> (raw)
In-Reply-To: <200707022034.53206.even.rouault@mines-paris.org>

Hi,

> This patch adds support for reading, writing and creation (and thus 
> conversion) of VDI images (VirtualBox image format). Creation of derived 
> images above read-only base images also works, through a hack (the base image 
> filename is stored as the comment of the derived image)
> It's mainly a thin wrapper around VirtualBox OSE source code.
> It may not compile on non-Linux hosts, and it definitely won't work on big 
> endian hosts. So, there's still a bit of work to do for those interested by 
> running it on those platforms.

What about writing a native implementation? At least with read support,
for importing from Virtualbox.

--
Alex

      reply	other threads:[~2007-07-27  0:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 18:34 [Qemu-devel] [PATCH] Add support for VDI images Even Rouault
2007-07-27  0:25 ` Alex Beregszaszi [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=1185495926.22903.22.camel@localhost \
    --to=alex@fsn.hu \
    --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).