From: Kip Macy <kip.macy@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: dynamically allocating loopback devices?
Date: Fri, 11 Mar 2005 14:05:06 -0800 [thread overview]
Message-ID: <b1fa29170503111405567983a0@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E35E3@liverpoolst.ad.cl.cam.ac.uk>
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 <m+Ian.Pratt@cl.cam.ac.uk> 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
next prev parent reply other threads:[~2005-03-11 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 21:55 dynamically allocating loopback devices? Ian Pratt
2005-03-11 22:05 ` Kip Macy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 15:36 Ian Pratt
2005-03-11 22:09 Ian Pratt
2005-03-11 22:18 ` Kip Macy
2005-03-12 1:04 ` Mark Williamson
2005-03-12 1:25 ` Kip Macy
2005-03-12 1:25 ` Mark Williamson
2005-03-11 21:28 Kip Macy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1fa29170503111405567983a0@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.