Hey, thanks again for taking the time to answer my questions. I really appreciate it! You are right about first running ovirt in its native distribution (RHEL/Fedora/Centos) so I can familiarize myself with its proper functioning state. Even though I did not mention it, I am doing just that -- I have a CentOS VM with ovirt-engine running and another one with ovirt-node. However, sometimes I still run into issues I am uncertain the root cause of. I will do some more testing and reading of READMEs and the code and check how ovirt works on CentOS. Perhaps I'll start another thread, titled Porting oVirt to LFS where I will post my questions as I run into issues I can't resolve on my own, instead of starting a new thread for each one? One thing I would like to raise now is that various packages or even different scripts within the same package depend on either python2 or python3 and some use the very ambiguous #!/usr/bin/python. Trouble is, I recently switched to python3 by default, so /usr/bin/python is actually python3, not as the script assumes, python2. So I'm patching those to #!/usr/bin/python2. But it would be very useful, now that I read somewhere that Fedora is about to default to python3, to not assume python2 is default and explicitly specify the interpreter #!/usr/bin/env python2 or #!/usr/bin/env python3. Thanks, IvanK.