From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Jan 11
Date: Tue, 11 Jan 2011 07:53:40 -0800 [thread overview]
Message-ID: <20110111155340.GC25929@x200.localdomain> (raw)
KVM Forum 2011
- expand the scope? yes, continue up the stack
- how long? 2 days (maybe 2 1/2 - 3 space permitting)
- where? Vancouver with LinuxCon
Spice guest agent:
- virt agent, matahari, spice agent...what is in spice agent?
- spice char device
- mouse, copy 'n paste, screen resolution change
- could be generic (at least input and copy/paste)
- send protocol details of what is being sent
- need to look at how difficult it is to split it out from spice
(how to split out in qemu vs. libspice)
- goal to converge on common framework
- more discussion on char device vs. protocol
- eg. mouse_set breaks if mouse channel is part pv and part spice specific
- Alon will send link to protocol and try to propose new interfaces
migration and block devices:
- need to invalidate data after first read on target,
because it can be stale
- close + reopen is what was done for NFS
- iscsi: can issue ioctl(BLKFLSBUF) to flush, but it's CAP_SYS_ADMIN only
- O_DIRECT to avoid cache (concerns that it's not guaranteed)
- agree change the default (cache=none for
qemu patch queue is long:
- slow to return from break
- patience and more patch review will help make sure things are applied
and don't fall through cracks
next reply other threads:[~2011-01-11 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 15:53 Chris Wright [this message]
2011-01-11 18:33 ` spice vdagent protocol, was Re: [Qemu-devel] KVM call minutes for Jan 11 Alon Levy
2011-01-13 15:01 ` Adam Litke
2011-01-13 19:18 ` Alon Levy
2011-01-13 19:44 ` Adam Litke
2011-01-13 20:11 ` Alon Levy
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=20110111155340.GC25929@x200.localdomain \
--to=chrisw@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).