Re: [Qemu-devel] ivshmem migration restrictions and bugs

2016-02-25 Thread Markus Armbruster
"Dr. David Alan Gilbert" writes: > * Markus Armbruster (arm...@redhat.com) wrote: >> TL;DR: I recommend to stay away from migration when using chardev=... >> >> ivshmem migration is messed up in several entertaining ways. >> >> = General lossage = >> >> G1. Migrating more than one peer doesn't

Re: [Qemu-devel] ivshmem migration restrictions and bugs

2016-02-25 Thread Dr. David Alan Gilbert
* Markus Armbruster (arm...@redhat.com) wrote: > TL;DR: I recommend to stay away from migration when using chardev=... > > ivshmem migration is messed up in several entertaining ways. > > = General lossage = > > G1. Migrating more than one peer doesn't work, but that's a (badly) > documented

[Qemu-devel] ivshmem migration restrictions and bugs

2016-02-24 Thread Markus Armbruster
TL;DR: I recommend to stay away from migration when using chardev=... ivshmem migration is messed up in several entertaining ways. = General lossage = G1. Migrating more than one peer doesn't work, but that's a (badly) documented restriction, not a bug (see documentation of property "rol