Re: [Qemu-devel] Why I advise against using ivshmem

[David Marchand <david.marchand@6wind.com>]

On 06/18/2014 05:01 PM, Andreas Färber wrote:
> late onto this thread: SUSE Security team has just recently
> done a thorough review of QEMU ivshmem code because a customer has
> requested this be supported in SLES12. Multiple security-related
> patches were submitted by Stefan Hajnoczi and Sebastian Krahmer, and I
> fear they are probably still not merged for lack of active
> maintainer... In such cases, after review, I expect them to be picked
> up by Peter as committer or via qemu-trivial.
>
> So -1, against dropping it.

Are these patches on patchwork ?

> Vincent, you will find an RFC for an ivshmem-test in the qemu-devel
> list archives or possibly on my qtest branch. The blocking issue that
> I haven't worked on yet is that we can't unconditionally run the qtest
> because it depends on KVM enabled at configure time (as opposed to
> runtime) to have the device available.
> http://patchwork.ozlabs.org/patch/336367/
>
> As others have stated before, the nahanni server seems unmaintained,
> thus not getting packaged by SUSE either and making testing the
> interrupt parts of ivshmem difficult - unless we sort out and fill
> with actual test code my proposed qtest.

Thanks for the RFC patch.

About ivshmem server, yes I will look at it.
I will see what I can propose or if importing nahanni implementation 
as-is is the best solution.

Anyway, first, documentation.


-- 
David Marchand