Description of problem: In F18 the dependencies of some components changed so that now all qemu-system-* arches are pulled in, which increases the image by (guessed) 50 megs. The question is, which qemu architectures/emulators are required on Node and which can be dropped? Version-Release number of selected component (if applicable): F18 builds
Richard, have you got a feeling how dropping all non-x86 qemu-system-* arches would effect libguestfs functionality?
Oh, libguestfs is (indirectly via libvirt-daemon-qemu) pulling in all the qemu-system- packages ...
libguestfs doesn't need any non-x86 architectures, unless you're planning on supporting those in oVirt.
Based on that, I think we're fine with blacklisting the other qemu-system-* components (not x86). My concern was what would happen if these were not available since this is the current dependency: libguestfs --> libvirt-daemon-qemu --> qemu --> qemu-system-* If libguestfs isn't going to need these and libvirt-daemon-qemu isn't going to blow up, then let's blacklist the non-supported architectures.
Fabian posted this patch already: http://gerrit.ovirt.org/#/c/11264/
Okay, further investigation shows that qemu-user (pulled in by qemu) is also using much space (~50mb inside the image, dunno how it affects the outside size). I believe it can be removed safely.
This (draft patch) removes qemu-user: http://gerrit.ovirt.org/11529
Removing qemu-user reduces the final image by 6M.
Patches acked and merged, available in next release