All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>,
	libvir-list@redhat.com, ceph-devel@vger.kernel.org,
	sheepdog@lists.wpkg.org
Subject: Re: [libvirt] [PATCH v2] add network disk support
Date: Thu, 09 Dec 2010 12:13:49 -0700	[thread overview]
Message-ID: <4D012A6D.3080602@redhat.com> (raw)
In-Reply-To: <20101209110925.GA5313@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

On 12/09/2010 04:09 AM, Daniel P. Berrange wrote:
> On Mon, Dec 06, 2010 at 04:24:09PM +0900, MORITA Kazutaka wrote:
>> This patch adds network disk support to libvirt/QEMU.  The currently
>> supported protocols are nbd, rbd, and sheepdog.  The XML syntax is like
>> this:
>>
>>     <disk type="network" device="disk">
>>       <driver name="qemu" type="raw" />
>>       <source protocol='rbd|sheepdog|nbd' name="...some image identifier...">
>>         <host name="mon1.example.org" port="6000">
>>         <host name="mon2.example.org" port="6000">
>>         <host name="mon3.example.org" port="6000">
>>       </source>
>>       <target dev="vda" bus="virtio" />
>>     </disk>
>>
>>  docs/schemas/domain.rng |   31 +++++++

Hmm; missing a corresponding update to docs/formatdomain.html.in to
document the new XML.

> ACK

NACK.  After applying this patch, I get 'make check' failures:

TEST: vmx2xmltest
      /bin/sh: line 5: 15285 Segmentation fault      (core dumped)
abs_top_builddir=`cd '..'; pwd` abs_top_srcdir=`cd '..'; pwd`
abs_builddir=`cd '.'; pwd` abs_srcdir=`cd '.'; pwd` CONFIG_HEADER="`cd
'..'; pwd`/config.h"
PATH="$abs_top_builddir/src:$abs_top_builddir/daemon:$abs_top_builddir/tools:$PATH"
SHELL="/bin/sh"
LIBVIRT_DRIVER_DIR="/home/remote/eblake/libvirt/src/.libs" LC_ALL=C
${dir}$tst
FAIL: vmx2xmltest
TEST: xml2vmxtest
      ...!!!!!!!!!!...............!!!!!!!!!..  39  FAIL

I haven't looked into root cause.  Kazutaka, would you mind preparing a v3?

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2010-12-09 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 20:49 [PATCH] add network disk support MORITA Kazutaka
2010-12-02 13:19 ` Daniel P. Berrange
     [not found]   ` <20101202131928.GV2502-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-12-06  7:24     ` [PATCH v2] " MORITA Kazutaka
2010-12-07 19:54       ` [PATCH 0/2] rbd " Josh Durgin
     [not found]       ` <1291620249-19645-1-git-send-email-morita.kazutaka-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2010-12-07 19:56         ` [PATCH 1/2] qemu: Add RBD support and some network disk fixes Josh Durgin
2010-12-09 11:10           ` [libvirt] " Daniel P. Berrange
2010-12-07 19:57       ` [PATCH 2/2] tests: Add tests for network disks Josh Durgin
2010-12-09 11:10         ` [libvirt] " Daniel P. Berrange
2010-12-09 11:09       ` [PATCH v2] add network disk support Daniel P. Berrange
2010-12-09 19:13         ` Eric Blake [this message]
2010-12-09 21:31           ` [libvirt] " Eric Blake

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=4D012A6D.3080602@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=sheepdog@lists.wpkg.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.