From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: "Williamson, Mark A" <mark.a.williamson@intel.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: questions about production use
Date: Sat, 24 Jan 2004 08:46:04 +0000 [thread overview]
Message-ID: <20040124084604.GA16163@axis.demon.co.uk> (raw)
In-Reply-To: <CF8C1D789F0AD0459192CDEAF3A7EC5001E53BD9@swsmsx402.ger.corp.intel.com>
On Fri, Jan 23, 2004 at 08:26:15PM -0000, Williamson, Mark A wrote:
> > If Xen could run using files that would be most interesting to us - it
> > would mean the minimum change to our current setup.
>
> Currently, it's not possible to use a file as a block device for a guest
> domain. Hoewver, the new virtual disk management in 1.2 allows
> file-based disk images to be imported to Xen virtual disks and
> vice-versa. Virtual disks are allocated within a pool of free space
> made up of devices and partitions on your system that you have set aside
> for the purpose.
Sort of like LVM but run by Xen? Tha sounds very interesting.
> You can extend this free pool when you want. Virtual disks can also
> be enlarged by allocating more space from the free pool (Currently,
> they can't be enlarged whilst mounted by a domain and have that
> domain see the changes. But that wouldn't be hard to implement).
That sounds like just the job. We'd also want to be able to access
all the virtual disks from Domain0 for administrative purposes (backup
/ transfer to a new host etc) but I guess that is possible.
> > Maybe these could be served from Domain0 in some efficient fashion I
> > don't know... I guess you could do it using the nbd but a more
> > efficient mechanism would be nice. Something like iSCSI but over a
> > Xen transport.
>
> Right now, you probably could serve them from domain using something
> like NBD, but that won't be necessary once the next gen IO stuff is in
> place. That will allow lots of cool things, including efficiently serve
> out files as block devices AND have them appear as ordinary Xen virtual
> block devices to guests, so your guests don't have to run any weird
> network protocols and can easily use them as their root file system.
Excellent!
How much of this and the above is implemented now? Should I be
checking out Xen 1.2 and reading the docs?
Cheers
Nick
--
Nick Craig-Wood
ncw1@axis.demon.co.uk
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-24 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 20:26 questions about production use Williamson, Mark A
2004-01-24 8:46 ` Nick Craig-Wood [this message]
[not found] <20040123145905.A9C0D1102@gg104015.zipptec.de>
2004-01-23 17:26 ` Manfred.Herrmann
2004-01-23 17:37 ` Ian Pratt
2004-01-23 20:01 ` Nick Craig-Wood
2004-01-23 19:46 ` Nick Craig-Wood
2004-01-24 1:09 ` Stephen Evanchik
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=20040124084604.GA16163@axis.demon.co.uk \
--to=ncw1@axis.demon.co.uk \
--cc=mark.a.williamson@intel.com \
--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.