qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bobby Dimmette <bjdimmette@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 893956] Re: qemu-img bug with dynamic vhd
Date: Wed, 07 Jun 2017 14:42:31 -0000	[thread overview]
Message-ID: <18c801d2df9c$4b822bc0$e2868340$@gmail.com> (raw)
In-Reply-To: 149682501508.8386.15479145248309541889.malone@gac.canonical.com

No, sorry. The environment was retired in 2014 and we took a different
direction.


-Bobby

-----Original Message-----
From: bounces@canonical.com [mailto:bounces@canonical.com] On Behalf Of Thomas Huth
Sent: Wednesday, June 07, 2017 4:44 AM
To: bjdimmette@gmail.com
Subject: [Bug 893956] Re: qemu-img bug with dynamic vhd

Can you still reproduce this problem with the latest version of QEMU
(currently version 2.9.0)?

** Changed in: qemu
       Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/893956

Title:
  qemu-img bug with dynamic vhd

Status in QEMU:
  Incomplete

Bug description:
  Hye, i found a problem with qemu-img when trying to get info of a
  dynamic vhd. I made imgae of my 60GB computer hard drive with
  disk2vhd. The dynamic vhd is 21gb size.

  With 1.0-rc3 version :
  running command: qemu-img info 60_GB.VHD
  qemu-img:  Could not open '60_GB.VHD' : File too large

  0.14.1 version give me wrong information :
  image: 60_GB.VHD
  file format: vpc
  virtual size: 127G (136899993600 bytes)
  disk size: 21G

  Thanks for reply.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/893956/+subscriptions

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893956

Title:
  qemu-img bug with dynamic vhd

Status in QEMU:
  Incomplete

Bug description:
  Hye, i found a problem with qemu-img when trying to get info of a
  dynamic vhd. I made imgae of my 60GB computer hard drive with
  disk2vhd. The dynamic vhd is 21gb size.

  With 1.0-rc3 version :
  running command: qemu-img info 60_GB.VHD
  qemu-img:  Could not open '60_GB.VHD' : File too large

  0.14.1 version give me wrong information :
  image: 60_GB.VHD
  file format: vpc
  virtual size: 127G (136899993600 bytes)
  disk size: 21G

  Thanks for reply.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/893956/+subscriptions

  reply	other threads:[~2017-06-07 14:56 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
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 [this message]
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='18c801d2df9c$4b822bc0$e2868340$@gmail.com' \
    --to=bjdimmette@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).