Description of problem:
/var/lib/xen/xenbl can be left behind, leading to spurious
[root@xentest1 ~]# xm create -c guest1
Using config file "/etc/xen/guest1".
Error: [Errno 17] File exists
Version-Release number of selected component (if applicable):
xen/tools/python/xen/xend/XenBootloader.py creates the xenbl FIFO to communicate
to a subprocess but does not delete it for all errors; nor does it handle
multiple instances running at the same time.
Created attachment 124983 [details]
Always delete the /var/lib/xen/xenbl file on error.
Simple XenBootloader.py patch to add a try...finally: construct to make sure we
delete /var/lib/xen/xenbl on error.
We still need to handle the case where it exists on entry, by forming a new
filename (based on pid?) to avoid collisions.
I vaguely remember there being a reason why I was using a defined name instead
of actually doing a mktemp'd name. Let me look further
Can't tell what it was. Committed a fix to CVS and sent upstream