<br><br><div class="gmail_quote">On Sat, Sep 29, 2012 at 2:10 PM, Joop <span dir="ltr"><<a href="mailto:jvdwege@xs4all.nl" target="_blank">jvdwege@xs4all.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Dave Neary wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 09/29/2012 01:37 PM, Hans Lellelid wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I apologize in advance that this email is less about a specific<br>
problem and more a general inquiry as to the most recommended /<br>
likely-to-be-successful way path.<br>
</blockquote></blockquote></div>
Having been there I know the difficulty of setting up oVirt but with the release of 3.1 things have improved immensely. One problem remains and you have found it already and that is the NFS problem with kernel 3.5.x<br>
I have installed several Fed17 nodes and have had no problems sofar.<br>
I install from the LiveCD Fed17 KDE 64bits and then add the ovirt repo and install vdsm and its dependancies. After that I add the node through engine and after the installation is ready and the node has rebooted it functions as one would expect.<br>
If you want I can paste my bash history.<br>
One thing to look out for is to switch off NetworkManager before hand and configure and activate 'network'<span class="HOEnZb"><font color="#888888"><br><br></font></span></blockquote><div><br></div><div>Yeah, I did have success with network configuration when I did it manually. However, I did not switch off NetworkManager when I was doing the installation from the engine ... so maybe that is something to try next. Thanks for the tips! I'll report back.</div>
<div><br></div><div>Hans</div></div><br>