qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
	ronnie sahlberg <ronniesahlberg@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Orit Wasserman <owasserm@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv5] block: add native support for NFS
Date: Fri, 03 Jan 2014 12:04:25 +0100	[thread overview]
Message-ID: <52C69939.5070305@kamp.de> (raw)
In-Reply-To: <CAJSP0QUyhMohV7n22jytTgxtO8hyLgGnRKoxyBrVjuYWaikffA@mail.gmail.com>

On 03.01.2014 11:37, Stefan Hajnoczi wrote:
> Looks good.  In order to merge this new block driver qemu-iotests
> support for nfs is required.  That way the block driver can be exercised
> and checked for regressions (I guess you performed manual testing
> during development).
>
> Please see tests/qemu-iotests/common for examples of
> NBD/SSH/Sheepdog/etc support.
>
> The qemu-iotests test suite with raw, qcow2, and vmdk formats should
> work on top of NFS.  Assuming you have an NFS server already running
> on localhost, something like the following should succeed:
>
>    cd tests/qemu-iotests
>    ln -s ../../x86_64-softmmu/qemu-system-x86_64 qemu
>    ln -s ../../qemu-img .
>    ln -s ../../qemu-io .
>    ./check -nfs # raw format by default
>    ./check -nfs -qcow2
>    ./check -nfs -vmdk
>
> Maybe -nfs should take the base NFS URI as an argument to allow more
> flexible test configurations.  It's up to you.
>
> More info on qemu-iotests: http://qemu-project.org/Documentation/QemuIoTests
i need to exclude test 063.

rm -f nfs://

obviously does not work. I wonder how sheepdog and rdb passed this test..

Peter

  parent reply	other threads:[~2014-01-03 11:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 12:48 [Qemu-devel] [PATCHv5] block: add native support for NFS Peter Lieven
2014-01-03 10:37 ` Stefan Hajnoczi
2014-01-03 10:51   ` Peter Lieven
2014-01-03 11:04   ` Peter Lieven [this message]
2014-01-03 11:28   ` Peter Lieven
2014-01-06  1:18     ` Stefan Hajnoczi
2014-01-06  6:53       ` Peter Lieven
2014-01-09 14:13 ` Kevin Wolf
2014-01-09 16:08   ` Peter Lieven
2014-01-10 11:40     ` Kevin Wolf
2014-01-10 12:12       ` Peter Lieven
2014-01-10 12:30         ` Paolo Bonzini
2014-01-10 14:49           ` ronnie sahlberg
2014-01-10 15:05             ` Peter Lieven
2014-01-10 15:46               ` Kevin Wolf
2014-01-10 16:10                 ` Peter Lieven
2014-01-10 17:16                   ` ronnie sahlberg
2014-01-10 18:05                     ` Paolo Bonzini
2014-01-10 18:07                       ` Peter Lieven
2014-01-10 18:24                         ` Paolo Bonzini
2014-01-10 18:47                           ` Peter Lieven

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=52C69939.5070305@kamp.de \
    --to=pl@kamp.de \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /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).