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:18:43 -0800 [thread overview]
Message-ID: <b1fa291705031114183a47ba38@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E35E5@liverpoolst.ad.cl.cam.ac.uk>
I was confused by the fact that xm insists on it being present in DOM0.
disk = [ 'file:/u/kmacy/mdroot-5.3,xbd0,w' ]
kmacy@shemp sh -x ~/xentmp/xenargs.shemp
+ xm create -f /u/kmacy/xentmp/freebsd.shemp -c
name=xen-vm2.lab.netapp.com vmid=10 kernel=/u/kmacy/kernel
Using config file "/u/kmacy/xentmp/freebsd.shemp".
Error: Error creating domain: vbd: Device not found: xbd0
Thanks.
-Kip
On Fri, 11 Mar 2005 22:09:04 -0000, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > 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' ]
>
> file: does do the loop device allocation. The second parameter is the
> device you want the vbd to appear in the guest as, i.e. usually sda1 or
> hda1.
>
> 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:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 22:09 dynamically allocating loopback devices? Ian Pratt
2005-03-11 22:18 ` Kip Macy [this message]
2005-03-12 1:04 ` Mark Williamson
2005-03-12 1:25 ` Kip Macy
2005-03-12 1:25 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 15:36 Ian Pratt
2005-03-11 21:55 Ian Pratt
2005-03-11 22:05 ` Kip Macy
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=b1fa291705031114183a47ba38@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.