Too bad I got around it by installed fedora 16 + vdsm (and the server went live now).<br>I'll try again on weekend and fire a bug then.<br><br><div class="gmail_quote">On Tue, Apr 10, 2012 at 6:57 PM, Mike Burns <span dir="ltr"><<a href="mailto:mburns@redhat.com">mburns@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sat, 2012-04-07 at 23:23 +0700, Quyet Nguyen Duc wrote:<br>
> Hi everybody,<br>
><br>
> I downloaded ovirt-node-iso-2.3.0-1.0.fc16.iso from ovirt site, use<br>
> livecd-iso-to-disk to create an usb installer, then boot from it.<br>
> The boot options are the same as a fedora live image.<br>
><br>
> No matter which option i chose: Start ovirt node, install in console,<br>
> reinstall, reinstall in console,<br>
> instead of an install wizard, I got a login screen with no clue to go<br>
> on.<br>
><br>
> The hardware is a typical supermicro server with 2x5620 xeon, 48GB<br>
> RAM.<br>
><br>
> Any idea what's going on ?<br>
<br>
</div></div>It sounds like a problem with the TUI failing to load correctly.<br>
<br>
Can you boot it and edit the kernel commandline to add:<br>
<br>
rootpw=<hashed_password><br>
<br>
To create a hashed password, you can run openssl passwd.<br>
<br>
i.e.:<br>
$ openssl passwd<br>
Password:<br>
Verifying - Password:<br>
ElxQsbGPoSSNw<br>
<br>
Then add:<br>
<br>
rootpw=ElxQsbGPoSSNw<br>
<br>
to the command line. When it boot,s you can then login as root. Once<br>
in as root, can you check the /tmp/ovirt.log and /var/log/ovirt.log file<br>
for any errors?<br>
<br>
Thanks<br>
<br>
Mike<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br>
<br>
</blockquote></div><br>