Bug 512672

Summary: Remove initrd warning message
Product: Red Hat Enterprise Linux 5 Reporter: Richard W.M. Jones <rjones>
Component: kvmAssignee: Eduardo Habkost <ehabkost>
Status: CLOSED ERRATA QA Contact: Lawrence Lim <llim>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: lihuang, mjenner, riek, tburke, tools-bugs, virt-maint, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kvm-83-110.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 07:55:32 UTC Type: ---
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: 512696    
Attachments:
Description Flags
kvm-remove-initrd-warning-message.patch none

Description Richard W.M. Jones 2009-07-20 10:35:03 UTC 
Created attachment 354325 [details]
kvm-remove-initrd-warning-message.patch

The attached very trivial patch removes an annoying
warning message which is printed by qemu whenever the
qemu -initrd option is used.  Since libguestfs uses
this option, the message is always printed for us.

Upstream since May 2009:

http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=42fa1c2e226bd62e8df145f3509b692b65a6170c

The attached patch is the same as upstream, just
rebased against our KVM package.

I tested it using libguestfs.  It suppresses the
message as expected.
Comment 1 Richard W.M. Jones 2009-07-20 10:56:00 UTC 
Here's a simple test you can use to see if this patch
has been applied:

$ guestfish alloc /tmp/test.img 10M : run

This command may print several other warning messages,
but the one the should *not* appear is:

  qemu: loading initrd (XXXX bytes) at XXXX
Comment 11 errata-xmlrpc 2010-03-30 07:55:32 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0271.html