Bug 902384

Summary: [F18] All qemu architectures are pulled in and increase the size of the image / What arches are required?
Product: [Retired] oVirt Reporter: Fabian Deutsch <fdeutsch>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2CC: acathrow, dyasny, jboggs, mburns, mgoldboi, ovirt-bugs, ovirt-maint, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-06 13:58:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 894059    

Description Fabian Deutsch 2013-01-21 14:42:18 UTC 
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
Comment 1 Fabian Deutsch 2013-01-21 16:48:23 UTC 
Richard,

have you got a feeling how dropping all non-x86 qemu-system-* arches would effect libguestfs functionality?
Comment 2 Fabian Deutsch 2013-01-21 16:49:59 UTC 
Oh, libguestfs is (indirectly via libvirt-daemon-qemu) pulling in all the qemu-system- packages ...
Comment 3 Richard W.M. Jones 2013-01-21 16:51:08 UTC 
libguestfs doesn't need any non-x86 architectures, unless
you're planning on supporting those in oVirt.
Comment 4 Mike Burns 2013-01-21 17:07:05 UTC 
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.
Comment 5 Mike Burns 2013-01-21 17:08:04 UTC 
Fabian posted this patch already:

http://gerrit.ovirt.org/#/c/11264/
Comment 6 Fabian Deutsch 2013-01-30 08:27:25 UTC 
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.
Comment 7 Fabian Deutsch 2013-01-30 09:03:08 UTC 
This (draft patch) removes qemu-user:

http://gerrit.ovirt.org/11529
Comment 8 Fabian Deutsch 2013-01-30 10:46:36 UTC 
Removing qemu-user reduces the final image by 6M.
Comment 9 Mike Burns 2013-02-06 13:58:36 UTC 
Patches acked and merged, available in next release