On Mon, Dec 18, 2017 at 11:11:00AM +0100, Markus Armbruster wrote: > Max Reitz <mre...@redhat.com> writes:
[...] Thanks, Max, for the detailed notes. > > Image creation in qemu-system-* vs. qemu-img: > > In order to get proper introspection for qemu-img create, we need a > > QAPI schema. If we have a QAPI schema, we might as well add > > blockdev-create to QMP. > > As long as we do not have a really-none (null, void, ...) machine type > > for qemu-system-*, launching such a process just for creating an image > > will bring quite a bit of overhead (e.g. with -M none -accel qtest). > > However, as for libvirt, this is not exactly a regression since > > libvirt currently cannot create images at all (apart from implicitly > > through drive-mirror etc.). Further work on voidifying qemu-system-* > > will improve performance. > > Another thought: do we want to give qemu-system-* the necessary > privileges for creating images? Two cases: running with and without a > guest. Related: Just curious -- was it an explicit design decision to not give `qemu-system-*` permissions to create disk images? [...] -- /kashyap
