On Fri, Jan 08, 2010 at 10:08:25AM -0500, Tait Clarridge wrote: > On Fri, 2010-01-08 at 09:38 -0500, Tait Clarridge wrote: > > > I think 5.4 version of python-virtinst added some fixes aswell.. > > > so maybe you need to upgrade to that for F12 installation to work. > > > > > > Also please try running "xm console" for the guest and see what it does > > > and where it crashes.. > > > > If I do xm create -c f12domU.cfg it says "Starting Domain f12domU" and > > then brings me back to the command prompt on dom0. > > Just do add something, this led me to believe there was an incompatible > kernel, and have tried both i686 and x86_64 kernels. > Make sure your domU kernel has these kernel cmdline options: "console=hvc0 earlyprintk=xen" That makes the Xen console work with upstream pv_ops kernels. Also, if you think it crashes, you can add "on_crash=preserve" option to the Xen guest configfile, and when the guest has crashed you can do: /usr/lib/xen/bin/xenctx -s System.map-domUkernelversion <domid> That'll give you a stacktrace of the crashes guest to debug it. Note that if your dom0 is 64bit the xenctx binary is under lib64, not lib. Also, what hardware was this? There has been some fixes to the incorrect cpuid masking causing guest kernel crashes on new cpus, and some of those are fixed in upcoming EL 5.5 Xen. -- Pasi