Description of problem:
Virt-launcher pods are slow to terminate in some cases which are not yet well known. This is what is observed:
1. Launcher is notified to gracefully shut down. (Note it seems we are not trying to forcefully shut down the domain after graceful shut down)
2. "gracefully closed notify pipe connection for vmi" is observed after the domain shut down
3. Lot of loops follows with "detected unresponsive virt-launcher command socket"
<- This is the main issue why we don't clean up
4. Final clean-up is performed and Pod is terminated shortly

The most notable change in this area was safepath handling which might be a cause of different paths of clean up.

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info: