On Mon, Sep 3, 2012 at 10:41 AM, franxico <893...@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
Serge Hallyn introduced the size check when VHD files are opened, you can read about the background here: http://patchwork.ozlabs.org/patch/106736/ I'm not sure if QEMU has a bug or lacks support for the file format version used by disk2vhd. > > Thanks for your help > > -- > 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: > New > > 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 >
