From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: Karen Noel <knoel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] QEMU & KVM at devconf.cz 7-9 February in Brno, Czech Republic
Date: Tue, 11 Feb 2014 18:33:52 +0100 [thread overview]
Message-ID: <52FA5F00.8070905@redhat.com> (raw)
In-Reply-To: <20140211171105.GU28427@otherpad.lan.raisama.net>
Il 11/02/2014 18:11, Eduardo Habkost ha scritto:
> On Tue, Feb 11, 2014 at 06:07:39PM +0100, Stefan Hajnoczi wrote:
>> On Fri, Jan 31, 2014 at 5:10 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>>> Several QEMU and KVM community members will be at devconf.cz 7-9
>>> February in Brno, Czech Republic. See the schedule for details on KVM
>>> and virtualization talks:
>>>
>>> http://devconf.cz/schedule
>>>
>>> Thin provisioning in the KVM virtualization stack - how we got there - Paolo Bonzini
>>> KVM and CPU feature enablement - Eduardo Habkost
>
> http://wiki.qemu.org/File:Cpu-models-and-libvirt-devconf-2014.pdf
Good idea, I was wondering where to put mine. :)
http://wiki.qemu.org/File:Devconf14-bonzini-thin-provisioning.pdf
Paolo
>>> Virtual vs physical machines - what's the difference to software? - Karen Noel
>>
>> Paolo, Eduardo, Karen: Please post links to your slides.
>>
>>> VIRTIO 1.0: Paravirtualized I/O devices for KVM and beyond - Stefan Hajnoczi
>>
>> http://vmsplice.net/~stefan/virtio-devconf-2014.pdf
>>
>> Stefan
>
next prev parent reply other threads:[~2014-02-11 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 16:10 [Qemu-devel] QEMU & KVM at devconf.cz 7-9 February in Brno, Czech Republic Stefan Hajnoczi
2014-02-11 17:07 ` Stefan Hajnoczi
2014-02-11 17:11 ` Eduardo Habkost
2014-02-11 17:33 ` Paolo Bonzini [this message]
2014-02-11 22:36 ` Karen Noel
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=52FA5F00.8070905@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=knoel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).