1:52 p.m.
This is a multi-part message in MIME format.
--------------010804000705040607020304
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 03/05/2012 01:34 PM, Joe Pruett wrote:
On 03/05/2012 08:04 AM, Joe Pruett wrote:
> On 03/05/2012 07:00 AM, Joey Boggs wrote:
>> On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote:
>>>> -----Original Message-----
>>>> From:users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On
>>>> Behalf Of ext Joe Pruett
>>>> Sent: Sunday, March 04, 2012 2:11 AM
>>>> To:users@ovirt.org
>>>> Subject: [Users] proliant errors trying to install ovirt-node image
>>>>
>>>> i've already found the info on the list about the "global name
'disk'
>>>> not defined" error and i've tried both an iso from the jenkins
url
>>>> listed, as well as creating my own git area using the 2.2.3 tagged code
>>>> and making the one line change to fix that python error. but neither
>>>> of
>>>> those images work either. i get a generic "ovirt node hypervisor
>>>> installation failed" message. i've poked around the log viewers
and at
>>>> the end i see it complaining that the gpt partition label has no bios
>>>> bootable partition, but it isn't clear if that is really the issue.
>>> I ran into the same problems as you when trying to install on a
>>> HP ProLiant BL460c G1 blade.
>>>
>>> The Red Hat Bugzilla report #798030 "TUI Installation fails with
>>> Grub error" seems to address exactly this kind of problem.
>>>
>>> The grub2-setup complaining has got its reason: In file script/storage.py
>>> the disk partitioning is done using a GPT, but no partition with
>>> flag bios_grub is created.
>>>
>>> I modified the source (mis-)using the first partition (EFI partition)
>>> in case of a non-EFI boot as a bios_grub flagged partition. This
>>> partition is much bigger than necessary (grub2.info recommends one
>>> or two MB), thus leaving some room for optimization for the experts when
>>> fixing the problem.
>>>
>>> Please find the patch that allowed successful installation in the
>>> attachment.
>> Can you submit this through gerrit, its looks fine to me and I don't
>> see any problem merging it.
>> http://ovirt.org/wiki/Working_with_gerrit.ovirt.org
>
> i'll be testing this later and will give feedback.
>
>>>> i'm
>>>> wondering if there might be more cciss driver issues.
>>>>
>>>> i haven't dug into the source to figure out the root pw so i could
more
>>>> easily look at the log files or export them. can someone enlighten me
>>>> with that more quickly than i can find it?
>>> As I am stuck to reading log files online or exporting them via screen
shots,
>>> I am also interested in learning about better ways of exporting.
>> The root password isn't set by default, you can however press F2
>> inside the installer or the configuration menus to get to a shell
>> prompt and setup networking to get logs off there.
>
> i discovered that the root pw is explicitly locked. f2 does nothing
> at the error screen, alt-f2 shows a login prompt. does f2 stop
> working at some point during the process?
>
ok, i've dug into this more. my system does not have efi, but the
install process is creating an efi partition and making it bootable.
it looks like it always does this, all that efi presence seems to do
is change the starting sector for the efi partition. so i can't quite
see how this works for anyone else :-).
and i got f2 to work. it doesn't work while in a log viewer, but does
work at the final 'install failed' screen. so i can poke around now.
what logs or other info would be of use to look at this more? i may
also try installing a non cciss card into this box to see if that is
the real root of the problem.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Main install logs are: /tmp/ovirt.log and once the install finishes it
will switch over to /var/log/ovirt.log
--------------010804000705040607020304
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/05/2012 01:34 PM, Joe Pruett wrote:
<blockquote cite="mid:4F55072A.8090301@q7.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 03/05/2012 08:04 AM, Joe Pruett wrote:
<blockquote cite="mid:4F54E412.60400@q7.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 03/05/2012 07:00 AM, Joey Boggs wrote:
<blockquote cite="mid:4F54D526.1070404@redhat.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote:
<blockquote
cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net"
type="cite">
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a>
[<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="mailto:users-bounces@ovirt.org">mailto:users-bounces@ovirt.org</a>]
On
Behalf Of ext Joe Pruett
Sent: Sunday, March 04, 2012 2:11 AM
To: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:users@ovirt.org">users@ovirt.org</a>
Subject: [Users] proliant errors trying to install ovirt-node image
i've already found the info on the list about the "global name 'disk'
not defined" error and i've tried both an iso from the jenkins url
listed, as well as creating my own git area using the 2.2.3 tagged code
and making the one line change to fix that python error. but neither
of
those images work either. i get a generic "ovirt node hypervisor
installation failed" message. i've poked around the log viewers and at
the end i see it complaining that the gpt partition label has no bios
bootable partition, but it isn't clear if that is really the issue.
</pre>
</blockquote>
<pre wrap="">I ran into the same problems as you when trying
to install on a
HP ProLiant BL460c G1 blade.
The Red Hat Bugzilla report #798030 "TUI Installation fails with
Grub error" seems to address exactly this kind of problem.
The grub2-setup complaining has got its reason: In file script/storage.py
the disk partitioning is done using a GPT, but no partition with
flag bios_grub is created.
I modified the source (mis-)using the first partition (EFI partition)
in case of a non-EFI boot as a bios_grub flagged partition. This
partition is much bigger than necessary (grub2.info recommends one
or two MB), thus leaving some room for optimization for the experts when
fixing the problem.
Please find the patch that allowed successful installation in the
attachment.
</pre>
</blockquote>
Can you submit this through gerrit, its looks fine to me and I
don't see any problem merging it.<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="http://ovirt.org/wiki/Working_with_gerrit.ovirt.org">h...
</blockquote>
<br>
i'll be testing this later and will give feedback.<br>
<br>
<blockquote cite="mid:4F54D526.1070404@redhat.com"
type="cite">
<blockquote
cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net"
type="cite">
<blockquote type="cite">
<pre wrap="">i'm
wondering if there might be more cciss driver issues.
i haven't dug into the source to figure out the root pw so i could more
easily look at the log files or export them. can someone enlighten me
with that more quickly than i can find it?
</pre>
</blockquote>
<pre wrap="">As I am stuck to reading log files online or
exporting them via screen shots,
I am also interested in learning about better ways of exporting.
</pre>
</blockquote>
The root password isn't set by default, you can however press
F2 inside the installer or the configuration menus to get to
a shell prompt and setup networking to get logs off there.<br>
</blockquote>
<br>
i discovered that the root pw is explicitly locked. f2 does
nothing at the error screen, alt-f2 shows a login prompt. does
f2 stop working at some point during the process?<br>
<br>
</blockquote>
<br>
ok, i've dug into this more. my system does not have efi, but the
install process is creating an efi partition and making it
bootable. it looks like it always does this, all that efi
presence seems to do is change the starting sector for the efi
partition. so i can't quite see how this works for anyone else
:-).<br>
<br>
and i got f2 to work. it doesn't work while in a log viewer, but
does work at the final 'install failed' screen. so i can poke
around now. what logs or other info would be of use to look at
this more? i may also try installing a non cciss card into this
box to see if that is the real root of the problem.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
Main install logs are: /tmp/ovirt.log and once the install finishes
it will switch over to /var/log/ovirt.log<br>
</body>
</html>
--------------010804000705040607020304--