Comment 4 for bug 527875

Chuck Short, I hope to hear from you again, I can see you are a key participant in dealing with these bugs.
It's Saturday now so I suppose I can't expect you to reply before Monday, and you are busy I'm sure.
From what I've gleaned, you're not going to reproduce. The sockets are so fundamental that they surely would have been reported as a bug by someone else by now. So I suppose it follows that is is low priority at your end. But something has gone awry. I would hope for you to grant it some input so as to finally achieve a sane setup on my karmic.

I've pursued libvirt quite a bit, on lenny for extended periods, and gentoo. http://bugs.gentoo.org/show_bug.cgi?id=305401
This flaw leaves my completely puzzled, short of being fluent in python programming, there is nowhere to go with it. From what I've read, creating the sockets and assigning permissions is one of the first things executed by libvirtd. How can this sytem do anything without them? i.e. Why does virsh connect to xen in their absence?

The only link to xen I can trace that might bear some influence I've already mentioned. In xend-config.sxp, one of the fundamental choices to select is the type of server. The choice of

(xend-http-server yes)
(xend-port 8000)

finally allowed connectivity. The promoted selection is (xend-unix-server yes), which I have just tried. It is absent as a selection in the xend-config.sxp, so I had to manually add it. It also works, but leaves me wondering,
why is this selection absent?
what is a recommended standard setup for karmic with its standard packages?
It's too intricate for me.