From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Mark Ryden <markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvmfs
Date: Sun, 06 May 2007 18:30:04 +0300 [thread overview]
Message-ID: <463DF47C.4000104@qumranet.com> (raw)
In-Reply-To: <dac45060705060810n5ec7b1eehda15b3d91f277b3d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Mark Ryden wrote:
> Thanks, Avi.
>
> I thought that this kvmfs is somehow connected to
> "a synthetic file system that can be used to control one or more KVM
> virtual machines running on a computer."
>
> see:
> http://www.linuxsymposium.org/2007/view_abstract.php?content_key=102
>
> I assume there is no connection between your kvm and this project ?
>
Ah, okay. There are two kvmfs's.
What I described is a kvm-internal thing. The paper appears to describe
something that is used to manage kvm as a whole. I don't really know
anything about it, I guess I'll have to attend the presentation.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-05-06 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 11:38 kvmfs Mark Ryden
[not found] ` <dac45060705060438i204b8ed3lb98606b913a616c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-05-06 11:51 ` kvmfs Avi Kivity
[not found] ` <463DC137.1000601-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-06 15:10 ` kvmfs Mark Ryden
[not found] ` <dac45060705060810n5ec7b1eehda15b3d91f277b3d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-05-06 15:30 ` Avi Kivity [this message]
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=463DF47C.4000104@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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.