I'm trying to track down a bug (563103) which only occurs in Koji. We
think it may be because the Rawhide qemu binary, when it runs on the
Koji RHEL 5 kernel, makes some system call that returns -EINVAL.
Unfortunately qemu turns -EINVAL from a host system call into an
emulated disk error. If qemu was issuing some syscall with a new
parameter which the RHEL 5 kernel didn't understand that could cause
the syscall to return -EINVAL.
To test this theory, I'm trying to run mock in RHEL 5.4, but using the
Rawhide mock config, ie:
$ mock -r fedora-rawhide-x86_64 --rebuild /tmp/libguestfs-1.0.83-6.fc13.src.rpm
This does not work because the yum version in RHEL 5.4
(yum-3.2.22-20.el5) cannot parse the SHA256 checksums in the Rawhide
repos (see: https://bugzilla.redhat.com/show_bug.cgi?id=500069#c7
But how does this work in Koji? Does Koji have a newer version of yum
specially installed to deal with this case? Or does Koji/mock somehow
run the Rawhide version of yum (and can I get my mock to do the same)?
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.