From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: dynamically allocating loopback devices? Date: Fri, 11 Mar 2005 14:05:06 -0800 Message-ID: References: Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ian Pratt Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk List-Id: xen-devel@lists.xenproject.org That allows me to bypass the losetup, but what about device allocation? - the examples I see all look like disk = [ 'file:/u/kmacy/mdroot-5.3,loop7,w' ] What I'd really like is to be able to drop the second parameter, or do something like disk = [ 'file:/u/kmacy/mdroot-5.3,*,w' ] -Kip On Fri, 11 Mar 2005 21:55:39 -0000, Ian Pratt wrote: > > > My users' VM disks are all loopback files. Right now they have to run > > losetup on each of their files before starting their VMs. This means > > we have to statically allocate loopback devices. And if they want to > > change the disks used they have to remember to run "losetup -d". Is > > there any way, without my writing extra glue logic, for a user to say > > in his config file "these are my loopback files, I don't care what > > loopback devices they get bound to, just bind them for me and then > > start my VM"? > > Check out the 'file:' syntax for specifying vbd's. > > Ian > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click