Entire case started with project for p2v migration of old SCO machines. One of the machines had entire directory tar'ed and then we had to deploy virtual one. OVF eventually was deployed, but after comparison of disk setup of Physical with Virtual I though that root partition should be extended, as physical one had 2GB of space more. That's why the question in that thread. Eventually I'v noticed that Physical one has only 4GB of space used so Virtual machine is fine, I just needed another partition, and that was easy task.

Then, having virtual machine deployed i started restoring backed up tar files and restoring them on virtual as it is. I was prepared for some configs to be modified (/etc/fstab, etc.). But it turned out that partition table got messed up, so I tried and tried. Eventually I'v got to the point I described, I've noticed that actually all important things are in /opt/{K,P}, so I've first tar'ed those directories on virtual machine, restored physical machine tars, and overwritten what I previously tared on virtual one. And that allowed me to boot the machine without one error during boot procedure. But I don't know if that's proper way to migrate (for sure not) and if all services that supposed to start started (I a assume no errors means something).

Maybe you already know better procedure for doing such migration in diy way, without use of enterprise software. If teams that will test it tell me that I doeasn't work as it should I'll start reading documentation for Backup/RestoreEDGE and other software that was posted here.

Still thanks for all help, and If you have more suggestions I will be glad to read them.