qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 893956 <893956@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 893956] Re: qemu-img bug with dynamic vhd
Date: Wed, 5 Sep 2012 07:59:11 +0100	[thread overview]
Message-ID: <CAJSP0QX_USSej-FQtVx30qbZm2n5jQ=Xsn0ndD6A0GaTCVa-uA@mail.gmail.com> (raw)
In-Reply-To: <20120903094143.1115.6377.malone@soybean.canonical.com>

On Mon, Sep 3, 2012 at 10:41 AM, franxico <893956@bugs.launchpad.net> wrote:
> Hi,
>
> I'm having the same problem. I'm using qemu-img 1.0, running from a
> Ubuntu Server 12.04 x64 on a SW RAID, ext4.
>
> The .VHD has 29GB and was made using disk2vhd.
>
> Here is the command and the results:
> sudo kvm-img convert -f vpc -O raw image.VHD image.img
> [sudo] password for sysop:
> kvm-img: Could not open 'image.VHD': File too large
> kvm-img: Could not open 'image.VHD'
>
> Same error doing a simple qemu-img info image.vhd

Please post the output of the following commands:

$ hexdump -C -n 512 image.VHD
$ hexdump -C -n 512 -s $(($(ls -l image.VHD | awk '{ print $5 }') -
512)) image.VHD

This will show the file header/footer, which contains fields that are
validated when opening the file.

Thanks,
Stefan

  parent reply	other threads:[~2012-09-05  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 11:33 [Qemu-devel] [Bug 893956] [NEW] qemu-img bug with dynamic vhd z22lad
2011-11-23 13:35 ` Stefan Hajnoczi
2012-09-03  9:41 ` [Qemu-devel] [Bug 893956] " franxico
2012-09-04 11:41   ` Stefan Hajnoczi
2012-09-05  6:59   ` Stefan Hajnoczi [this message]
2012-09-04 15:00 ` Serge Hallyn
2012-09-05  6:54   ` Stefan Hajnoczi
2012-09-05 14:33     ` Serge Hallyn
2017-06-07  8:43 ` Thomas Huth
2017-06-07 14:42   ` Bobby Dimmette
2017-06-07 17:06 ` Thomas Huth

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='CAJSP0QX_USSej-FQtVx30qbZm2n5jQ=Xsn0ndD6A0GaTCVa-uA@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=893956@bugs.launchpad.net \
    --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).