qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/7] block-vpc: Improve support for VHD images
Date: Tue, 27 Jan 2009 10:20:40 +0100	[thread overview]
Message-ID: <497ED1E8.6000003@suse.de> (raw)
In-Reply-To: <20090126215239.GA9296@shareable.org>

Jamie Lokier schrieb:
> Kevin Wolf wrote:
>> This patch series improves the support for Virtual PC images. Until
>> now, support for this image format is read-only and broken for large
>> images. With these patches applied, you can create and write to VHD
>> Dynamic Disks and some bugs in the read support are fixed. They have
>> been tested with qemu-img convert from and to raw images and a
>> successful openSUSE installation on a fresh VHD image.
> 
> Ooh, I look forward to trying these patches. :-)
> 
> I have some VHD image of Windows which always resulted in lots of
> scandisk errors when Windows booted from it (using -snapshot), and the
> same when converted to a QCOW2 file by qemu-img.

I think there is only one integrity patch in the series which fixes
images > 4 GB. Is this the case with your image?

> (By the way, VPC took *ridiculously* long - about 8 hours for an 80GB
> sparse image.  VirtualPC appears to use unbuffered writes (equivalent
> to O_DIRECT) at least when over SMB, but they are small writes and not
> overlapped, so it trickles along very slowly).

Well, my implementation probably isn't that fast as well. It's the
simplest one I could think of and it's mostly to have at least something
to convert images. I don't think I would run a VM on it except for testing.

> So I look forward to trying these patches on that image, which I don't
> use know but kept for this very purpose, and seeing if it's fixed the
> errors.

Thanks for testing and please report back. I hope it works fine now.

Kevin

      reply	other threads:[~2009-01-27  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 16:59 [Qemu-devel] [PATCH 0/7] block-vpc: Improve support for VHD images Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 1/7] block-vpc: Split up struct vpc_subheader Kevin Wolf
2009-01-26 20:27   ` Anthony Liguori
2009-01-26 16:59 ` [Qemu-devel] [PATCH 2/7] block-vpc: Adapt header structures to official documentation Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 3/7] block-vpc: Fix disk size Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 4/7] block-vpc: Fix support for images > 4 GB Kevin Wolf
2009-01-27 11:03   ` Kevin Wolf
2009-01-27 14:30     ` Anthony Liguori
2009-01-27 14:29   ` Anthony Liguori
2009-01-26 16:59 ` [Qemu-devel] [PATCH 5/7] block-vpc: Use the qemu block layer Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 6/7] block-vpc: Write support Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 7/7] block-vpc: Create images Kevin Wolf
2009-01-26 21:52 ` [Qemu-devel] [PATCH 0/7] block-vpc: Improve support for VHD images Jamie Lokier
2009-01-27  9:20   ` Kevin Wolf [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=497ED1E8.6000003@suse.de \
    --to=kwolf@suse.de \
    --cc=jamie@shareable.org \
    --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).