qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PATCH] Add a blog post with the presentations from the FOS


From: Thomas Huth
Subject: [Qemu-devel] [PATCH] Add a blog post with the presentations from the FOSDEM 2017
Date: Fri, 10 Feb 2017 11:30:39 +0100

The videos are now available online, so here's a blog post
that contains the links to the QEMU-related videos.

Signed-off-by: Thomas Huth <address@hidden>
---
 _posts/2017-02-10-fosdem-presentations.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 _posts/2017-02-10-fosdem-presentations.md

diff --git a/_posts/2017-02-10-fosdem-presentations.md 
b/_posts/2017-02-10-fosdem-presentations.md
new file mode 100644
index 0000000..707d5c7
--- /dev/null
+++ b/_posts/2017-02-10-fosdem-presentations.md
@@ -0,0 +1,30 @@
+---
+layout: post
+title:  "Presentations from the FOSDEM 2017"
+date:   2017-02-10 11:30:00 +0100
+author: Thomas Huth
+categories: presentations
+---
+During last weekend, on February 4th and 5th, the
+[FOSDEM 2017](https://fosdem.org/2017/) conference took place in Brussels,
+which featured a [Virtualisation and IaaS
+track](https://fosdem.org/2017/schedule/track/virtualisation_and_iaas/).
+
+Some people of the QEMU community attended, and the videos of the
+presenters are now available online, too:
+
+* [Incremental Backups -- Good things come in small
+   packages!](https://fosdem.org/2017/schedule/event/backup_dr_incr_backups/)
+  by John Snow
+
+* [Internal APIs and conflicting world views -- How abstractions inside QEMU
+  (don't) work 
together](https://fosdem.org/2017/schedule/event/iaas_qemintapi/)
+  by Eduardo Habkost
+
+* [Network Block Device -- how, what,
+   why](https://fosdem.org/2017/schedule/event/iaas_netblodev/)
+  by Wouter Verhelst
+
+* [Using NVDIMM under KVM -- Applications of persistent memory in
+   virtualization](https://fosdem.org/2017/schedule/event/iaas_usinvdund/)
+  by Stefan Hajnoczi
-- 
1.8.3.1




reply via email to

[Prev in Thread] Current Thread [Next in Thread]