From: Kevin Wolf <kwolf@redhat.com>
To: Timothy Scott <tscott2@clemson.edu>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] PVFS2 Block Driver Support
Date: Wed, 10 Jul 2013 16:31:50 +0200 [thread overview]
Message-ID: <20130710143150.GR3898@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <CA+4Zj17pM1rDBERHCZODincTmYKTZwbi_pFJBrWmZu9d9LwXnA@mail.gmail.com>
Am 10.07.2013 um 16:08 hat Timothy Scott geschrieben:
> 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.
Can you run something like 'qemu-io -c "read 0 128M" pvfs2:scratch/t.qcow2'
on that manually created image? (This, and a write on the same area, is
essentially what the test 001 does)
Kevin
prev parent reply other threads:[~2013-07-10 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:25 [Qemu-devel] PVFS2 Block Driver Support Timothy Scott
2013-06-27 14:43 ` Stefan Hajnoczi
2013-06-27 14:53 ` Stefan Hajnoczi
2013-06-27 21:40 ` Alex Bligh
2013-07-01 8:47 ` Stefan Hajnoczi
2013-07-03 15:41 ` Timothy Scott
2013-07-04 8:41 ` Stefan Hajnoczi
2013-07-08 14:54 ` Timothy Scott
2013-07-10 14:08 ` Timothy Scott
2013-07-10 14:31 ` Kevin Wolf [this message]
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=20130710143150.GR3898@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=tscott2@clemson.edu \
/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).