From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes May 15th
Date: Tue, 15 May 2012 16:58:40 +0200 [thread overview]
Message-ID: <87fwb11of3.fsf@elfo.elfo> (raw)
This were the topics discussed Today:
- open-fd-hook
* (anthony): using blockdev is quite complicated. libvirnt would need to
know all images formats.
* (kevin): libvirt already knows it.
* use a filename <-> fd dictionary
We are at: having a command to get an fd from libvirt, or asking to
libvirt to open a file from use.
* should we use a push model?
* using /dev/fd?
- 1.1 changelog, anything missing at http://wiki.qemu.org/ChangeLog/Next?
talk about it on the mailing list
- how is 1.1 looking?
anthony testing rc2.
roadmap for qemu-kvm-1.1
reply other threads:[~2012-05-15 14:58 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=87fwb11of3.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).