From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54258) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bygBE-0001IB-4B for qemu-devel@nongnu.org; Mon, 24 Oct 2016 10:24:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bygBA-000416-UL for qemu-devel@nongnu.org; Mon, 24 Oct 2016 10:24:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56172) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bygBA-00040v-OJ for qemu-devel@nongnu.org; Mon, 24 Oct 2016 10:24:44 -0400 References: <1475035789-685-1-git-send-email-ashish.mittal@veritas.com> <20160930083606.GA5411@stefanha-x1.localdomain> From: Paolo Bonzini Message-ID: <1cec99e2-eb93-b897-bf7d-8ae7bd70ed17@redhat.com> Date: Mon, 24 Oct 2016 16:24:35 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ketan Nilangekar , Stefan Hajnoczi , Ashish Mittal Cc: "qemu-devel@nongnu.org" , "kwolf@redhat.com" , "armbru@redhat.com" , "berrange@redhat.com" , "jcody@redhat.com" , "famz@redhat.com" , Ashish Mittal , Abhijit Dey On 20/10/2016 03:31, Ketan Nilangekar wrote: > This way the failover logic will be completely out of qemu address > space. We are considering use of some of our proprietary > clustering/monitoring services to implement service failover. Are you implementing a different protocol just for the sake of QEMU, in other words, and forwarding from that protocol to your proprietary code? If that is what you are doing, you don't need at all a vxhs driver in QEMU. Just implement NBD or iSCSI on your side, QEMU already has drivers for that. Paolo