Mmm... So you do not need any specific/unpackaged version of Xen, or you
don't need to modify Xen's code or apply any specific patch to it? If
no, why bothering with building from sources?
If you don't need anything particular, using what the distro provides is
almost always waaay easier than building from scratch, and that is
_especially_ true for Xen! :-O
> I am guessing there is a problem when it tries to connect to theCould be... Is the bridge working?
> internet to download packages.
>
No, I'm sorry, but now I feel like I'm loosing you. Are you saying that
> This was what I tried initially. Regular F17, then yum install Xen,
> and Virt-manager just worked out of the box for me, and I was able to
> create DomUs.
>
you installed Xen and virt-* with yum and you add it all working fine?
Well, if yes, why you abandoned that path?
Again, and sorry for repeating myself, if you do this, _do_ install an
F18 (actually, at this time, you may want to go for F19) and _do_
install both Xen, libvirt and the libvirt tools with *yum*. Don't build
anything if you don't need it. :-)
I said, and I confirm here, that on Fedora 18 (and the same applies to
F19 Beta, at least the few times I tired) I have virt-manager and
virt-install working well, either with xend running (i.e., using the old
toolstack and the xen libvirt driver) or without xend (i.e., using the
new toolstack and the libxl libvirt driver), at least for basic
create/start/pause/suspend/resume/reboot/shutdown workflow.