From owner-freebsd-xen@freebsd.org Fri Feb 26 18:16:30 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 786E6AB5D17 for ; Fri, 26 Feb 2016 18:16:30 +0000 (UTC) (envelope-from prvs=8571d395d=roger.pau@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A57B119F for ; Fri, 26 Feb 2016 18:16:29 +0000 (UTC) (envelope-from prvs=8571d395d=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.22,498,1449532800"; d="scan'208";a="341445634" Subject: Re: Porting the block-iscsi hotplug script To: =?UTF-8?Q?Gustau_P=c3=a9rez?= References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu> <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com> <555EF542.3090002@citrix.com> <555F9B3F.1000600@entel.upc.edu> <55602512.1090702@citrix.com> <56C6FA2F.8040900@gmail.com> <56CAC8CB.8030107@gmail.com> <56CADEDA.4050007@citrix.com> <56CB0057.1060509@gmail.com> <56CB041E.1020009@citrix.com> <56CB2D90.5080809@gmail.com> <56CB34BA.6060809@citrix.com> <56CC24BD.6050609@gmail.com> <56CC32E5.5010101@citrix.com> <56CC7637.3080408@gmail.com> <56CF5668.6090605@citrix.com> <56D0091F.80408@gmail.com> <56D02863.7040100@citrix.com> <56D03D95.9090509@gmail.com> <56D04E5F.8070901@citrix.com> <56D07392.60005@gmail.com> CC: FreeBSD XEN From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= Message-ID: <56D0965D.1070400@citrix.com> Date: Fri, 26 Feb 2016 19:15:57 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56D07392.60005@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2016 18:16:30 -0000 (re-adding freebsd-xen) El 26/2/16 a les 16:47, Gustau Pérez ha escrit: > > > El 26/02/16 a les 14:08, Roger Pau Monné ha escrit: >> >> It shouldn't be too hard, as I said the code is already there. The only >> issue I foresee is that you will have to find somewhere to store the >> information about the disk you have locally-attached, so you can remove >> it when the guest is destroyed. > > I fear that keeping state externally could be dangerous if something > fails to destroy the association between a domain and the locally > attached storage when the guest finishes. > > In any case, I suppose there are no restrictions on which kind of > storage is used to track that information, right? I suppose easier to > read, easier to edit and common formats would be better, like json or > thing like, right? I'm not a maintainer of libxl myself, but my first suggestion would be to store this information inside of xenstore. There's already a "/libxl" directory used in order to stash some toolstack specific info, adding a new directory/hierarchy there to store the local attachments seems like the best option IMHO. Roger.