> Just a followup. The current git does not have this problem - connects to > 0.8.3 just fine. Apologies. Wasn't paying enough attention to which libvirtd I had running. The currrent git still has the problem as I originally reported. Whit