Markus Armbruster <arm...@redhat.com> writes: > Marc-André Lureau <mlur...@redhat.com> writes: [...] >>> * shm appears to be the same as memdev, just less flexible. Why does it >>> exist? >> >> It was there before. > > Not only is memdev more flexible, it also provides the clean split > between frontend and backend we generally want.
In my tests, shm=foo can indeed be replaced by -object memory-backend=file,mem-path=/dev/shm/foo. However, /dev/shm is Linux-specific. For portability, we might need a memory-backend-shm. [...]
