From: Chris Wright <chrisw@redhat.com>
To: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org
Subject: Virtualization DevRoom at FOSDEM 2013
Date: Fri, 16 Nov 2012 11:46:36 -0800 [thread overview]
Message-ID: <20121116194636.GY14405@x200.localdomain> (raw)
Following on the heels of a successful KVM Forum and oVirt Workshop,
FOSDEM will be hosting a Virtualization DevRoom in February. If you've
been to FOSDEM before, you know this is about developers and code, not
products.
Presentation proposals are due by December 16th 2012.
The full details are here:
http://osvc.v2.cs.unibo.it/index.php/Main_Page
With the relevant topics being:
"Topics covered will include, but not limited to:
- machine virtualization (e.g. KVM, Xen, VirtualBox,...)
- network virtualization (e.g. openvstack, vale, vde, Open vSwitch,...)
- process level virtualization, flexible kernels (e.g. rump anykernel, view-os, ...)
- virt management (e.g. ganeti, libvirt, ovirt, XCP, ...)"
thanks,
-chris
reply other threads:[~2012-11-16 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121116194636.GY14405@x200.localdomain \
--to=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox