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 2012-10-02
Date: Tue, 02 Oct 2012 16:20:15 +0200 [thread overview]
Message-ID: <87mx057y74.fsf@elfo.mitica> (raw)
2012-10-02
----------
- TODO to finish off qemu-kvm.git/master... (anthony)
posibilibites: Problems of compatability (options, migration, ...)
* configuration file to specify what versions are done
* scripts that converts the format
* documentation
* look at argv[0] and start from there giving warnings changing options,
and we ship a symlink.
Anthony: rename: pc-0.12 to qemu-pc-0.12 and the qemu-kvm ones as kvm-pc-0.12
and create alias depending on argv[0] for instance.
- cpu-hotplug status?
developers want
- migration changes for migration format.
they are compatible, but default machines are not.
- vga framebuffer size is 16MB, and can't be changed
upstream have already configurability for this
- tasks:
compatability of options
migration compatibility
anthony offers to do the machine compatibility thing
reply other threads:[~2012-10-02 14:20 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=87mx057y74.fsf@elfo.mitica \
--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).