Description of problem:
* The problem occurs only for running VM with Sysprep for cluster 3.0 and below. Running VM with Sysprep provided as a VM Payload works fine.

The file created by VDSM for sysprep is located under 
/var/run/vdsm/VM_GUID.vfd

It serves any running of that VM with sysprep. 

When the VM is brought down - the file is deleted.

However, if the VDSM is restarted, when the VM is running, the file will remain on the system after the VM is stopped. This will cause the next run with sysprep file to fail with the following messages from log:

Thread-509::DEBUG::2012-05-09 16:30:34,167::__init__::1164::Storage.Misc.excCmd::(_log) '/usr/bin/sudo -n /usr/share/vdsm/mk_sysprep_floppy /var/run/vdsm/0fde3df3-fe4f-4212-b3a1-d1485383594
8.vfd' (cwd None)
Thread-509::DEBUG::2012-05-09 16:30:34,185::__init__::1164::Storage.Misc.excCmd::(_log) FAILED: <err> = 'mkfs.msdos: unable to create /var/run/vdsm/0fde3df3-fe4f-4212-b3a1-d14853835948.vfd\
n'; <rc> = 1
Thread-509::DEBUG::2012-05-09 16:30:34,186::BindingXMLRPC::870::vds::(wrapper) return vmCreate with {'status': {'message': 'Failed to create sysprep floppy image. No space on /tmp?', 'code': 9}}

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: