Thanks much for suggestions. And please accept my apologies for not replying sooner. Your reply got buried in lots of other list-serve messages.
You asked: "Ensure xend is *not* running and then restart libvirtd. The libvirt libxl driver will only load when xend is not running."
I'm a bit new at this, but I was under the impression that setting setting toolstack=xl in /etc/default/xen would prevent xend from starting. That is, I thought that xend wouldn't start when xl was running. Am I totally wrong about that?
In any case, xl is running and if I try to send an xm command, I get the following: "A different toolstack (xl) has been selected!" Is there something else that I should try to insure that xend isn't running?
(As a reminder, if I set toolstack=xm in /etc/default/xen, virt-manager works great. But I'm hoping to use the xl toolstack.)
You asked: "Did the libxl driver even load? There should be some evidence of that in libvirtd.log."
My libvirtd.log doesn't seem provide any evidence of that the libxl driver is loaded. (See log copied below.) But libvirtd.log does mention an "internal error failed to connect with xend." So honestly, I'm not quite sure whether libxl loaded. What's the best way to confirm?
You asked: "Has your libvirt package been built with the libxl driver enabled?"
I'm using the libvirt package that is available from the Ubuntu 13.04 (and now 13.10) repository. How would I go about checking whether that package was built with the libxl driver enabled?