From owner-freebsd-xen@freebsd.org  Mon Sep 26 02:11:47 2016
Return-Path: <owner-freebsd-xen@freebsd.org>
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 AE084BEAAB1
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon, 26 Sep 2016 02:11:47 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "vps1.elischer.org",
 Issuer "CA Cert Signing Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8955C85E
 for <freebsd-xen@freebsd.org>; Mon, 26 Sep 2016 02:11:47 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from julian-mbp3.pixel8networks.com
 (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133])
 (authenticated bits=0)
 by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u8Q2BgeG002280
 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
 Sun, 25 Sep 2016 19:11:44 -0700 (PDT)
 (envelope-from julian@freebsd.org)
Subject: Re: number of xen block devices
To: Colin Percival <cperciva@tarsnap.com>,
 Michael Sierchio <kudzu@tenebras.com>
References: <73fad119-03d8-a9ea-c222-f65b22c6feac@freebsd.org>
 <010001574a0207f9-d12e326c-e152-49f9-9763-2cf0161f7458-000000@email.amazonses.com>
 <3132e8d0-68db-940f-5cb1-22fe01b52480@freebsd.org>
 <CAHu1Y70uCjZH92iMe4NVaK3q9+bSfFb0DpT+7OtBCNoXOY-Pag@mail.gmail.com>
 <010001574dffc771-92e1b19d-4165-4e64-ae2a-63456c87d7a6-000000@email.amazonses.com>
Cc: FreeBSD Lists <freebsd-xen@freebsd.org>
From: Julian Elischer <julian@freebsd.org>
Message-ID: <4ef07a55-76f8-a55e-aa93-2a2fdee62696@freebsd.org>
Date: Sun, 25 Sep 2016 19:11:36 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <010001574dffc771-92e1b19d-4165-4e64-ae2a-63456c87d7a6-000000@email.amazonses.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2016 02:11:47 -0000

On 21/09/2016 11:26 AM, Colin Percival wrote:
> On 09/21/16 09:13, Michael Sierchio wrote:
>> Also check if there is a resource limit imposed by AWS. If you are bumping
>> into that, a simple request can get the limit raised for a particular
>> availability zone.
> AWS limits can be an issue, but it would be a limit on the number or size of
> the EBS volumes can *create*.  Once volumes are created, AWS limits won't
> affect whether you can attach them to instances or whether the instances can
> see the attached volumes, so I doubt that's what Julian was running into.
>
yes, Colin has it right..  our virtual device is based on 8.0 plus 
patches from later, and can't see all the devices we create.

I am moving to 10.3 this week so the problem may be self fixing.