From owner-freebsd-xen@freebsd.org Wed Sep 21 18:26:32 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 33829BE2893 for ; Wed, 21 Sep 2016 18:26:32 +0000 (UTC) (envelope-from 010001574dffc3a9-b9aa811c-ac09-45b3-9aea-1be72fcaab67-000000@amazonses.com) Received: from a8-237.smtp-out.amazonses.com (a8-237.smtp-out.amazonses.com [54.240.8.237]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC424E00 for ; Wed, 21 Sep 2016 18:26:31 +0000 (UTC) (envelope-from 010001574dffc3a9-b9aa811c-ac09-45b3-9aea-1be72fcaab67-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57; d=tarsnap.com; t=1474482390; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=FJF1eWoSuFFFSx3SYw+B16EBtQ6Osf1RbDYQDJ1BkLw=; b=Oc7XjqAWrgi4mYDoil5ZndHgdKXXnZd7GcXhbmoFke565gp82EQzwIO0oQXv1gDC HSFdeQzzdrd62vAmzJOtN44nYP861zcMclk93i8VmkEM/ffchHwf2NiJVXSOs7D5nYx oLb5B8yy6OID0ZQjWUEi60AfO8WytOn91NnQsMVA= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1474482390; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=FJF1eWoSuFFFSx3SYw+B16EBtQ6Osf1RbDYQDJ1BkLw=; b=YFcSPVnyVaXJ1Nso3mjE4K3PWvQi9ol5MdRakpnJvXaHMmeG18Bnq8bLx4EaRYvx xCpIFjfKC60lEjkzB9Z970vpeGt0eDbbvXF1/Mi8xMGTDD+9KNnE6FMVd20BiCEjNa1 cNJroNY1HMVzCYt6ZEy5Mlb8yX5RVJlVG6ZEALac= Subject: Re: number of xen block devices To: Michael Sierchio , Julian Elischer 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> Cc: FreeBSD Lists From: Colin Percival Message-ID: <010001574dffc3a9-b9aa811c-ac09-45b3-9aea-1be72fcaab67-000000@email.amazonses.com> Date: Wed, 21 Sep 2016 18:26:30 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2016.09.21-54.240.8.237 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 18:26:32 -0000 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. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid