From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
benoit.canet@irqsave.net, Fam Zheng <famz@redhat.com>,
Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
owasserm@redhat.com, Federico Simoncelli <fsimonce@redhat.com>,
ronniesahlberg@gmail.com,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS
Date: Fri, 31 Jan 2014 17:07:20 +0100 [thread overview]
Message-ID: <20140131160720.GC15009@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1391168333-11436-1-git-send-email-pl@kamp.de>
On Fri, Jan 31, 2014 at 12:38:48PM +0100, Peter Lieven wrote:
> This adds v6 of the NFS protocol driver + qemu-iotest adjustments.
>
> v7->v8:
> - bump libnfs requirement to 1.9.2
> - renamed NFSRPC->status to NFSRPC->ret [Benoit]
> - avoid double invocation of nfs_client_close in nfs_file_create [Benoit]
> - fixed error propagation in nfs_file_open [Benoit]
I was able to create a qcow2 image and boot a VM successfully over NFS.
I'm getting qemu-iotests failures:
$ ./check -nfs -qcow2
071 1s ... - output mismatch (see 071.out.bad)
--- 071.out 2014-01-31 13:14:07.066452661 +0100
+++ 071.out.bad 2014-01-31 16:41:52.824898587 +0100
@@ -4,29 +4,19 @@
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=67108864
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
-read 512/512 bytes at offset 0
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 512/512 bytes at offset 229376
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-read 512/512 bytes at offset 229376
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+qemu-io: can't open device nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2: Could not open 'nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2.base': No such file or directory
wrote 512/512 bytes at offset 0
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-blkverify: read sector_num=0 nb_sectors=4 contents mismatch in sector 0
+qemu-io: can't open device nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2: Could not open 'nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2.base': No such file or directory
=== Testing blkverify through file blockref ===
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=67108864
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
-read 512/512 bytes at offset 0
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 512/512 bytes at offset 229376
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-read 512/512 bytes at offset 229376
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+qemu-io: can't open device (null): Could not open 'nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2.base': No such file or directory
wrote 512/512 bytes at offset 0
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-blkverify: read sector_num=0 nb_sectors=4 contents mismatch in sector 0
+qemu-io: can't open device nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2: Could not open 'nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2.base': No such file or directory
=== Testing blkdebug through filename ===
@@ -34,7 +24,7 @@
=== Testing blkdebug through file blockref ===
-read failed: Input/output error
+qemu-io: can't open device (null): Could not open 'nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2': No such file or directory
=== Testing blkdebug on existing block device ===
@@ -55,8 +45,12 @@
Testing: -drive file=TEST_DIR/t.IMGFMT,format=IMGFMT,if=none,id=drive0
QMP_VERSION
{"return": {}}
+{"error": {"class": "GenericError", "desc": "could not open disk image drive0-verify: Could not open 'TEST_DIR/t.qcow2.base': No such file or directory"}}
+{"return": "Device 'drive0-verify' not found\r\n"}
{"return": {}}
-blkverify: read sector_num=0 nb_sectors=1 contents mismatch in sector 0
+{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN"}
+{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "DEVICE_TRAY_MOVED", "data": {"device": "ide1-cd0", "tray-open": true}}
+{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "DEVICE_TRAY_MOVED", "data": {"device": "floppy0", "tray-open": true}}
=== Testing blkverify on existing raw block device ===
@@ -64,8 +58,12 @@
Testing: -drive file=TEST_DIR/t.IMGFMT.base,if=none,id=drive0
QMP_VERSION
{"return": {}}
+{"error": {"class": "GenericError", "desc": "could not open disk image drive0-verify: Could not open 'TEST_DIR/t.qcow2': No such file or directory"}}
+{"return": "Device 'drive0-verify' not found\r\n"}
{"return": {}}
-blkverify: read sector_num=0 nb_sectors=1 contents mismatch in sector 0
+{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN"}
+{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "DEVICE_TRAY_MOVED", "data": {"device": "ide1-cd0", "tray-open": true}}
+{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "DEVICE_TRAY_MOVED", "data": {"device": "floppy0", "tray-open": true}}
=== Testing blkdebug's set-state through QMP ===
072 1s ... - output mismatch (see 072.out.bad)
--- 072.out 2014-01-31 13:14:07.066452661 +0100
+++ 072.out.bad 2014-01-31 16:41:53.285899409 +0100
@@ -9,12 +9,7 @@
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
wrote 512/512 bytes at offset 1024
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-read 512/512 bytes at offset 0
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-read 512/512 bytes at offset 512
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-read 512/512 bytes at offset 1024
-512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+qemu-io: can't open device (null): Could not open 'nfs://127.0.0.1//home/stefanha/qemu/tests/qemu-iotests/scratch/t.qcow2': No such file or directory
Pattern verification failed at offset 0, 512 bytes
read 512/512 bytes at offset 0
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
next prev parent reply other threads:[~2014-01-31 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 11:38 [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 1/5] " Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 2/5] qemu-iotests: change _supported_proto to file for various tests Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 3/5] qemu-iotests: enable support for NFS protocol Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 4/5] qemu-iotests: enable test 016 and 025 to work with " Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 5/5] qemu-iotests: blacklist test 020 for " Peter Lieven
2014-01-31 16:07 ` Stefan Hajnoczi [this message]
2014-01-31 17:32 ` [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS Peter Lieven
2014-01-31 20:41 ` Stefan Hajnoczi
2014-01-31 20:46 ` Max Reitz
2014-02-02 17:41 ` 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=20140131160720.GC15009@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=fsimonce@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=owasserm@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=xiawenc@linux.vnet.ibm.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).