WFM on a Fedora Xen Dom0 & DomU (Xeon E5). I am doing CPU-heavy computations on the DomU and I am not seeing any performance penalty with this workload.

with Xen, 4.3.3-4 seem to have broken support for more than 8 Domains, which completely hoses a moderate or large-sized Fedora Xen server. 4.3.5-200, from testing, fixes the problem. Assuming 9c17d96500f78d7ecdb71ca6942830158bc75a2b got in, but haven't chased it down myself. Definitely +1.

I've got OTR 1.9.1 showing up on mine (a couple weeks after previous comments).

The big one for me is that this fixes XHTML, so images now work from Gajim to Conversations.

confirming vanitygen works now without modification (built on f22).

verify logrotate fixed in 1.0.5-2 package currently in -testing.

This update works for me, it's necessary for EPEL because of the SSL fixes, and it caused me some personal pain getting the update to work. There doesn't appear to be a way to specify a chain certificate separately in ssl_multicert like the old directive in records.config. The old directive does still work, if you're OK with one chain certificate (but I'm upgrading to do an SNI rollout). The solution is to add the chain certificate to the ca certificate in a text file, and point to that as the ca certificate in ssl_multicert. Of note, 3.2 still needs more SSL fixes (secure renegotiation, DHE, ECDHE all don't work) to be up to snuff for today's reality. I'm going to see about getting those backported to 3.2 also over on their bugtracker, so that's not an issue here for this update, but I hope we can see an update in EPEL when those get rolled in - so we need 3.2 to happen in EPEL for the good of the Internet. What we need also is a way for EPEL to notify admins of this kind of thing in-system. I'm partly hesitant to give karma because it will break some systems in the field, but that's not the problem of this update, it's a Fedora problem and holding back this update won't fix that problem. Not getting EPEL up to 3.2 will cause more overall harm than those systems breaking, so I'm going for it.

updated with yum from testing, ran the network update (MU) and all appears well.