Stefan, Any pointers on likely culprits here?
I pass all 15/15 tests that actually run when I just run './check -pvfs2' When running './check -pvfs2 -qcow2' I fail 39 of 44 tests. These seem to be the most common errors: +IOError: [Errno 2] No such file or directory: 'pvfs2:/home/tscott2/qemu/tests/qemu-iotests/scratch/t.qcow2' +qemu-img: Header extension too large +qemu-img: Could not open 'pvfs2:TEST_DIR/t.qcow2': Invalid argument Failures:001 002 003 004 005 007 008 009 010 011 013 014 015 017 018 019 020 021 022 023 024 026 027 028 029 031 032 033 034 035 036 037 038 039 043 046 047 052 054 When I manually run 'qemu-img -f qcow2 pvfs2:scratch/t.qcow2 2g' a 193k image is successfully created. Joe On Thu, Jul 4, 2013 at 4:41 AM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > On Wed, Jul 03, 2013 at 11:41:08AM -0400, Timothy Scott wrote: > > In testing my block driver implementation, I am receiving the following > > error when trying to run an orangefs protocol with a qcow2 image format: > > > > +Header extension too large > > +qemu-io: can't open device pvfs2:/... > > +no file open, try 'help open' > > > > Is './check -pvfs2 -qcow2' a valid usecase in the iotests suite for > > specifying a qcow2 format file over the orangefs protocol? > > I haven't run IMGPROTO + IMGFMT tests but looking at the code it should > work. > > The "Header extension too large" error message comes from block/qcow2.c > so it seems the header data is corrupt. > > I suggest running "./check -pvfs2" first to make sure it passes the raw > image tests. > > Once that seems okay it's worth looking into issues from "./check -pvfs2 > -qcow2" and installing/running guests. > > Stefan > -- T. Joe Scott Clemson University '14 College of Engineering and Science
