Bug 512680 - errors while altering RPM package database
errors while altering RPM package database
Status: CLOSED DUPLICATE of bug 502074
Product: Virtualization Tools
Classification: Community
Component: libguestfs (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Richard W.M. Jones
Depends On:
  Show dependency treegraph
Reported: 2009-07-20 07:28 EDT by Marek Goldmann
Modified: 2010-03-16 13:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-21 08:51:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marek Goldmann 2009-07-20 07:28:27 EDT
Description of problem:

When executing rpm --rebuilddb (or any other switch which alters package database), libguestfs is exitting with an error.

Version-Release number of selected component (if applicable):


[oddthesis@lolek-f11 ~]$ uname -a
Linux lolek-f11 #1 SMP Tue Jun 16 23:19:53 EDT 2009 i686 i686 i386 GNU/Linux


Same as host.

[oddthesis@lolek-f11 downloads]$ rpm -qa | grep guestfs

How reproducible:


Steps to Reproduce:
1. Grab disk image from: http://repo.oddthesis.org/dev/management-appliance.raw.gz
2. Launch guestfish: guestfish -iv management-appliance.raw
3. Remove old db lock files: sh "rm /var/lib/rpm/__db.*"
4. Try to rebuild database: command "rpm --rebuilddb"
Actual results:

Different errors:
- Error without information
- rpm segfault in different libs
- no vm86_info: BAD error

Expected results:

No error, RPM package database rebuild.

Additional info:

On 64 bit host (and guest), everything works great.
Comment 1 Marek Goldmann 2009-07-20 07:30:22 EDT
Output from guestfish: http://gist.github.com/150259
Comment 2 Richard W.M. Jones 2009-07-20 11:43:32 EDT
I can't reproduce this at all.  I tried:

 - 32 bit w/ HVM
 - 32 bit w/o HVM
 - 64 bit w/ HVM
 - 64 bit w/o HVM

and all worked perfectly.

I don't have any guests running on VMWare ESX.  Please try to
reproduce this on a baremetal host.  If it doesn't happen on
a baremetal host, then it's a bug in VMWare, so you should ask
VMWare to look at it.

> - rpm segfault in different libs
> - no vm86_info: BAD error

Both of these errors indicate serious, random corruption in
qemu's emulation (TCG in this case).  Maybe VMWare can't run
qemu correctly.

Since it seems you have general problems running binaries in this
configuration, I strongly suggest you use a binary such as
/bin/false or:

  main () { exit (0); }

and try to get that to fail, with a stacktrace, on a baremetal
host.  There are just too many variables when you're trying to
run some process as complex as 'rpm --rebuilddb' to know where
to begin.
Comment 3 Richard W.M. Jones 2009-07-21 08:51:15 EDT
I'm now convinced this is a dup of 502074.

*** This bug has been marked as a duplicate of bug 502074 ***

Note You need to log in before you can comment on or make changes to this bug.