Can anyone explain to me why tap:aio sucks so badly?
We''ve got numerous CentOS 5 dom0s running file-backed domUs with
tap:aio.
The moment any one of them starts doing something disk-intensive, idle CPU
in dom0 decreases, iowait increases, and disk IO for every other domU on the
system suffers. Where lies the problem, and what to do about it?
Sincerely,
Ray Barnes
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
