registry team mailing list archive

[Dylan Redding <dredding@xxxxxxxxxxxxx>]

Exact instructions on how we are running the FIO tests:

<cut>
http://freshmeat.net/projects/fio/ - testing utility

# yum install libaio-devel
# wget http://freshmeat.net/urls/3aa21b8c106cab742bf1f20d60629e3f
# tar xvfz fio-1.38.tar.gz
# cd fio-1.38
# make
# make install
# cd ..
# mkdir -p /tmp/fio-testing/data
# vi four-threads-randio.fio
[global]
rw=randread
size=256m
directory=/tmp/fio-testing/data
ioengine=libaio
iodepth=4
invalidate=1
direct=1

[bgwriter]
rw=randwrite
iodepth=32

;[queryA]
;iodepth=1
;ioengine=mmap
;direct=0
;thinktime=3

;[queryB]
;iodepth=1
;ioengine=mmap
;direct=0
;thinktime=5

[bgupdater]
rw=randrw
iodepth=16
thinktime=40
size=32m

# fio four-threads-randio.fio
</cut>

The RedHat bug is indeed private, but checking
http://store.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.5/html-
single/Technical_Notes/ seems to indicate that this is related. An
excerpt from the technical notes:

<cut>
KVM and virtualized guests would become unresponsive due to waiting infinitely for an aio threads to return. The updated packages resolve this issue by correctly timing out threads which do not return. (BZ#525114)
</cut>


** Bug watch added: Red Hat Bugzilla #525114
   https://bugzilla.redhat.com/show_bug.cgi?id=525114

** Also affects: qemu-kvm (CentOS) via
   https://bugzilla.redhat.com/show_bug.cgi?id=525114
   Importance: Unknown
       Status: Unknown

-- 
KVM becomes unresponsive due to waiting for aio threads
https://bugs.launchpad.net/bugs/592327
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for CentOS.