From: Otavio Salvador <otavio@ossystems.com.br>
To: Kevin Wolf <kwolf@suse.de>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: The two image formats called qcow
Date: Wed, 26 Mar 2008 10:03:52 -0300 [thread overview]
Message-ID: <87ej9xeix3.fsf@ossystems.com.br> (raw)
In-Reply-To: <47EA0E3E.4030200@suse.de> (Kevin Wolf's message of "Wed\, 26 Mar 2008 09\:50\:06 +0100")
Kevin Wolf <kwolf@suse.de> writes:
> Is it an option to convert broken images to big endian when it is opened
> for the first time in ioemu? In this case, the fix for older versions
> could be in one place at least instead of being scattered over the whole
> file. Then you wouldn't be able to open such a file with tapdisk again,
> though.
If it could be done, a note in release notes would be required to warn
users that when it has been opened in a newer version using ioemu it
wouldn't be possible to be used again by tap driver anymore.
But yes, this would be an easy to use option if it's not too messy and
takes too long to convert the image (otherwise user can think that the
system has freeze).
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
next prev parent reply other threads:[~2008-03-26 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 17:25 The two image formats called qcow Kevin Wolf
2008-03-25 18:58 ` Otavio Salvador
2008-03-26 8:10 ` Keir Fraser
2008-03-26 8:50 ` Kevin Wolf
2008-03-26 13:03 ` Otavio Salvador [this message]
2008-03-26 13:54 ` Kevin Wolf
2008-03-26 14:02 ` Keir Fraser
2008-03-26 14:07 ` Kevin Wolf
2008-03-26 14:15 ` Keir Fraser
2008-03-26 14:22 ` Kevin Wolf
2008-03-27 9:55 ` [PATCH] tapdisk: Fix L1 table endianess of qcow images Kevin Wolf
2008-03-26 13:23 ` The two image formats called qcow Daniel P. Berrange
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=87ej9xeix3.fsf@ossystems.com.br \
--to=otavio@ossystems.com.br \
--cc=keir.fraser@eu.citrix.com \
--cc=kwolf@suse.de \
--cc=xen-devel@lists.xensource.com \
/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.