Description of problem:
While doing some live migration testing, my PV guest crashed (which is a
completely separate bug).  Once xend finished dumping core on the domain,
however, it got itself into a start where nothing works anymore.  That is, doing
"xm list" after this yields:

[root@localhost xen]# xm list
Error: Had a bootloader specified, but can't find disk
Usage: xm list [options] [Domain, ...]

List information about all/some domains.
  -l, --long                     Output all VM details in SXP               
  --label                        Include security labels                    


And that persists until I restart xend.  The xen version is 3.0.3-53.el5.  I'll
attach xend.log and xend-debug.log