Quoting Stefan Hajnoczi (893...@bugs.launchpad.net): > On Tue, Sep 4, 2012 at 4:00 PM, Serge Hallyn <893...@bugs.launchpad.net> > wrote: > > Though that commit and the comments were about 127G images. HIs is only > > 27G. > > The 127 GB limit applies to the virtual disk size, not to the size of > the image file itself.
I thought he had converted a roughly 26GB physical disk, assumed (perhaps wrongly) that was the virtual disk size. > > Also, 'qemu-img info' is also showing the error, which shows that this > > is not being done on vpc_create(). > > I'm not sure what you mean. Your commit (efc8243d00) added an -EFBIG > return to vcp_open(), not vpc_create(). This will affect qemu-img > info. Oops, good point. Thanks. > We need the header/footer contents to be sure what's going on here. -- 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