qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM developer call minutes (Jan 19)
Date: Tue, 19 Jan 2010 09:31:21 -0800	[thread overview]
Message-ID: <20100119173121.GA11561@x200.localdomain> (raw)


Minutes (please reply w/ corrections or follow-ups):

how is stable branch working (both qemu and kvm)?
- qemu 0.12 cherry picking pretty aggressively
  - could use more community involvement
  - any distro patches for qemu/kvm packages?
    - doesn't sound like it

vhost-net command line syntax
- Anthony not a huge fan of current syntax, but will take it
- long term, 0.13, like to revisit all network syntax
  - feature driven UI instead of interface driven UI (user shouldn't
    have to know about tun/tap).
- hard to properly express proper raw socket interface
  - users confused by subtle differences between raw and tun/

SR-IOV network device status
- require new enough host kernel to allocate VFs
- once allocated, can be used as PCI networking device in the host
  - shared device w/ bridge and taps
  - assigned device, assigned to guest
- need vhost-net above to get VF dedicated to guest via something like
  raw socket
- not capable to manage the embedded bridge, host OS needs these interfaces

todo collection/status updates
- can use this call for some quick status updates on feature development
- could also use this to highlight areas where feature is stuck or the
  todo list could use some community help.
- may prove useful as a running todo list...

mmio bug fix
- Avi is adding SSE support (kills 8 byte assumption, can be 16 bytes)

vmchannel integration
- qemu merge status
  - buffering should be done by guest not qemu (to avoid using host memory)
    - can't inform guest about the size of buffer (can't be infinite)
    - makes transport unreliable
  - guest driver should not succeed on write until consumed by host
    - guest app writes buffer
    - put data into ring queue
    - move entries to used queue, now complete write (notify guest)
    - guest kernel can force guest app to block
- VNC clipboard copy/paste
  - working w/ Amit's scripts, but needs proper GNOME integration (d-bus
    pointers appreciated)
- virtio console just doing one-byte at a time
- qemu char device will either block when full or drop bytes
  - desparately needs to be re-written

SPICE code overview tomorrow (Wed, Jan 20, 15:00 UTC)
- Send email to Dor Laor <dlaor@redhat.com> if interested

QMP status update
- working on feature negotiation, RFC coming tomorrow
- still working on switching libvirt to using QMP handlers
  - few series outstanding on libvirt list
- Markus working on self-description for protocol

             reply	other threads:[~2010-01-19 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 17:31 Chris Wright [this message]
2010-01-19 21:11 ` [Qemu-devel] Re: KVM developer call minutes (Jan 19) Dustin Kirkland

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=20100119173121.GA11561@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).