On 06/09/11 - 02:23:29PM, Francesco Vollero wrote:
On Thu, Jun 09, 2011 at 08:18:17AM -0400, Chris Lalancette wrote:
> On 06/08/11 - 09:25:48PM, Steven Dake wrote:
> > The default 300 second timer is insufficient to install RHEL6.1 on a W510
> > laptop. When the installation terminates with the 300 second default, the
> > install.img file is only 70% read from disk on this system.
> Hm, can you be a bit more clear here? Is this still during the initial
> anaconda stage where it is reading the install.img from the CD-ROM? If that is
> the case, I might suggest that instead of increasing the timeout, we also
> monitor the CD device for activity. That is, if either the diskimage or the
> CD-ROM has activity, we continue waiting.
but i was thinking if is not a bit smarter instead of monitor the CDROM or such stuff, to
have an Observer of the installation progress somehow. In that way, you should not be
worried to change the timeout, since it is auto driven.
Yes, but that is unfortunately very difficult to do. For instance, prior to
Fedora-14, there is really no good way to get logs out of the virtual machine
anaconda to watch it. Even if you *do* get the logs out of the virtual
machine, the output is not really machine parseable, so you have to resort to
And even if you do all of that, you still need a timeout. How do you know that
stage 12 of the anaconda install process has frozen, or is just taking a long
time to complete?