Displaying 6 results from an estimated 6 matches for "libvivrt".
Did you mean:
libvirt
2014 Jun 12
0
Why I advise against using ivshmem
...for my dislike range from practical to
> philosophical.
>
> My practical concerns include:
>
> 1. ivshmem code needs work, but has no maintainer
See David's contributions:
http://patchwork.ozlabs.org/patch/358750/
> 2. There is no libvirt support
One can use qemu without libvivrt.
> 3. Out-of-tree server program required for full functionality
We have the source code, it provides the documentation to write our own
better server program.
> 4. Out-of-tree kernel uio driver required
No, it is optional.
> These concerns are all fixable, but it'll take serious...
2014 Jun 13
5
[Qemu-devel] Why I advise against using ivshmem
...;t cover ivshmem.c.
>>
>> - The last non-trivial commit that isn't obviously part of some
>> tree-wide infrastructure or cleanup work is from September 2012
>> (commit c08ba66).
>>
>> 2. There is no libvirt support
>
> One can use qemu without libvivrt.
You asked me for my reasons for disliking ivshmem. This is one.
Sure, I can drink my water through a straw while standing on one foot,
but that doesn't mean I have to like it. And me not liking it doesn't
mean the next guy shouldn't like it. To each their own.
>> 3. Out-of-...
2014 Jun 13
5
[Qemu-devel] Why I advise against using ivshmem
...;t cover ivshmem.c.
>>
>> - The last non-trivial commit that isn't obviously part of some
>> tree-wide infrastructure or cleanup work is from September 2012
>> (commit c08ba66).
>>
>> 2. There is no libvirt support
>
> One can use qemu without libvivrt.
You asked me for my reasons for disliking ivshmem. This is one.
Sure, I can drink my water through a straw while standing on one foot,
but that doesn't mean I have to like it. And me not liking it doesn't
mean the next guy shouldn't like it. To each their own.
>> 3. Out-of-...
2014 Jun 12
3
Why I advise against using ivshmem (was: [Qemu-devel] Using virtio for inter-VM communication)
Henning Schild <henning.schild at siemens.com> writes:
> On Thu, 12 Jun 2014 08:48:04 +0200
> Markus Armbruster <armbru at redhat.com> wrote:
>
>> Vincent JARDIN <vincent.jardin at 6wind.com> writes:
>>
>> > On 10/06/2014 18:48, Henning Schild wrote:> Hi,
>> >> In a first prototype i implemented a ivshmem[2] device for the
>>
2014 Jun 12
3
Why I advise against using ivshmem (was: [Qemu-devel] Using virtio for inter-VM communication)
Henning Schild <henning.schild at siemens.com> writes:
> On Thu, 12 Jun 2014 08:48:04 +0200
> Markus Armbruster <armbru at redhat.com> wrote:
>
>> Vincent JARDIN <vincent.jardin at 6wind.com> writes:
>>
>> > On 10/06/2014 18:48, Henning Schild wrote:> Hi,
>> >> In a first prototype i implemented a ivshmem[2] device for the
>>
2014 Jun 13
0
[Qemu-devel] Why I advise against using ivshmem
...ons:
>> http://patchwork.ozlabs.org/patch/358750/
>
> We're grateful for David's patch for qemu-char.c, but this isn't ivshmem
> maintenance, yet.
others can come (doc), see below.
>>> 2. There is no libvirt support
>>
>> One can use qemu without libvivrt.
>
> You asked me for my reasons for disliking ivshmem. This is one.
>
> Sure, I can drink my water through a straw while standing on one foot,
> but that doesn't mean I have to like it. And me not liking it doesn't
> mean the next guy shouldn't like it. To each the...