qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] KVM call minutes for Oct 26


From: Chris Wright
Subject: [Qemu-devel] KVM call minutes for Oct 26
Date: Tue, 26 Oct 2010 08:02:50 -0700
User-agent: Mutt/1.5.20 (2009-12-10)

Guest Agents
- need to get to guest userspace for many actions
- virtio for userspace
- host backend needs to terminate in QEMU
- portable across guest OS's
- virt-agent
  - bi-directional RPC (XML-RPC just since it's easy)
  - cmd: shutdown, reboot, dmesg, execute command, read/write file
    - query guest type
- Matahari
  - consolidate agent proliferation
  - w/ or w/out networking (virtio-serial is fine)
  - may or may not have access to host
  - using amqp
- single transport
- use of qpid (C++, not C friendly)
  - put qemu bits in library and wrap (similar to libvirt, netcf, etc)
- e.g. shutdown, where does it live?
  - ACPI shutdown can trigger dbus, dialog, etc.
  - can already do ACPI, agent is for direct "shutdown -h now"
  - is there an async notification on shutdown (know it's been sucessful)
  - perhaps another library like libsysconfig
- openvmtools
  - useful as reference, GPL (requires copyright assignment)
  - uses PIO (or socket)

0.13.1
- vmmouse is broken
- assertion failure in block layer
  - just qemu-img: https://bugzilla.redhat.com/show_bug.cgi?id=646538
    - patch posted, thanks Stefan
- hotplug fixes
- fix for seabios SCI level triggered (broken host initiated powerdown on 
FreeBSD)
  - regression <-- any regression needs to be considered seriously
  - was planning to move to 0.6.1 (vs. latest git snapshot)
  - kevin indicated ok with stable/tagging/branch for seabios

bootindex patch series
- qdev name vs specific name
- fine for seabios interface
- migration needs stable address too
  - worth holding up series for this?
  - one more try, then fallback to plan b (new callback)

migration issues
- keep using network after VM has stopped
- sent hacky patch for virtio-net, but need a generic sol'n
- virtio-block flushes after stop
- need a similar stop/flush for other devices
- unclear how anything is running w/out getting back to main loop
  - happening after migration completes

networking interfaces
- old vlan vs new netdev...be nice to finish off and simply internal
  interfaces



reply via email to

[Prev in Thread] Current Thread [Next in Thread]