From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org, KVM devel mailing list <kvm@vger.kernel.org>
Subject: [Qemu-devel] KVM call minutes Mars 13th
Date: Tue, 13 Mar 2012 15:32:29 +0100 [thread overview]
Message-ID: <87haxstvuq.fsf@elfo.elfo> (raw)
Hi
Today was a short call, list of issues discussed:
Release dates for 1.1
- Soft-freeze: 15st April
- Hard-freeze: 1st May
- Change to 3 months release cycle?
discuss on list.
- nodev config?
* should it respect machine types
* cpu models are a mess (go figure)
* try to use andreas patches to use qdev for that
* how to manage the same machine type from one machine to other
* put configuration files on a shared place
- nodev; reads no config files
- if libvirt wants something specific: just reads the file that it wants
- agreement on this one
Later, Juan.
reply other threads:[~2012-03-13 14:33 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=87haxstvuq.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).