KVM call minutes for 2019-06-18

KVM call minutes for 2019-06-18

[Juan Quintela]

Hi

This are the random notes that I took about today community call.
Please review and add anything that you consider relevant.



Multiprocess qemu

Overview
- qemu (basically) runs as a single process
- emulates several devices
- the idea is to run the device emulations in a different process
- QMP/HMP/... still on main process
- rest of devices are going to be in external process
- idea is to reduce priviledge for each process
- questions?
  * how much work is going to be to integrate changes after this
  * most of the changes are new code with proxy objects
  * will not be changes to existing models
  * don't require all emulation run in remote process
  * device backends are run fully on the emulation process
  * leveraging virtio user model
  * expect DMA and IRQ like virtio user
* QEMU assumes that several things have global state
* migration/notifiers/...
* QEMU is able to DMA from one device to other device directly, with multiprocess is difficult
* How to get that global assumptions
* patches already quite big and only do one device so far
* Kevin is experimenthing with an external qemu-storage daemon
* qemu-storage daemon vs process for each image
  * compromise: less isolation but easier to do
* i.e. just doing the full subsystem instead of each device
* multiprocess:
  * devices shouldn't have to be changed, it is the same code that inside qemu
* TCG never claim any security
* qemu: command line and device interface and QMP
  good solotion for QMP, but for the rest
* libvirt/management app will launch the remote devices and just handle fd's to qemu
* When we launch qemu
  qemu needs to know the "proxied" devices through the command line
  move everything to QMP and don't even pass the command line
  spcially don't pass the commandline from qemu to processes
* Any quesntion about how the bus/device are presented?
* why don't use only nemu + virtio?
  nemu and virtio don't handle legacy devices
* cpu usage from multiprocess?
  how much cpu fro the same amount of IOPs:  current implementation use around 9-10% more cpu cycles
  but there are optimizations that could reduce it further
* multiprocess mmio
  create a kernel fd for each multiprocess and decide at device creation time if that range is
  going to be handled by the main qemu or another process.  Something like vhost-user.
  This is an optimizaton, not implemented yet.
* Why do they need legacy?
  Because they are not anly bringing new VM's, also legacy VM's (specially windows).
* Is worth this for legacy?
  Or just enable it for new/modern guests.
* How invasive is this?
  it is important to decide how much security/isolation it brings vs the amount of invasive things
  How much do we gain from using seccomp + unpriviledged qemu + ....
* Discussion about if it makes sense the change
  Does it bring enough new isolation to qemu

Thanks, Juan.

Re: [Qemu-devel] KVM call minutes for 2019-06-18

[Kevin Wolf]

Am 18.06.2019 um 16:49 hat Juan Quintela geschrieben:
> * Kevin is experimenthing with an external qemu-storage daemon
> * qemu-storage daemon vs process for each image
>   * compromise: less isolation but easier to do
> * i.e. just doing the full subsystem instead of each device

This is something that users can do then, but it's not a must.

The storage daemon is just a building block, and it's completely up to
the user whether they start a single daemon with many --blockdev options
and exports, or whether they start many daemons that serve only a single
image each.

Kevin