7:11 p.m.
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'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?
what is the best procedure to follow to try and get to the bottom of
issues like this? might i be better off installing a regular os and
then installing the vdsm package?
6:49 a.m.
-----Original Message-----
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On
Behalf Of ext Joe Pruett
Sent: Sunday, March 04, 2012 2:11 AM
To: users(a)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.
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.
what is the best procedure to follow to try and get to the bottom of
issues like this? might i be better off installing a regular os and
then installing the vdsm package?
Installing Fedora 16 on the same kind of blade
worked for me without any
problems. Therefore the "regular os + vdsm rpms" approach could help
you to sidestep the failing ovirt-node installation, but it will probably
not help you in analyzing and fixing ovirt-node related installation issues.
Best regards,
Hermann Huy
St.-Martin-Str. 76
81541 München
Tel: +49 89 5159 35744
Mob: +49 170 5630316
Email: hermann.huy(a)nsn.com
http://www.nokiasiemensnetworks.com/global/
Nokia Siemens Networks GmbH & Co. KG
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRA 88537
WEEE-Reg.-Nr.: DE 52984304
Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management
GmbH
Geschäftsleitung / Board of Directors: Hermann Rodler, Olaf Horsthemke
Vorsitzender des Aufsichtsrats / Chairman of supervisory board: Herbert Merz
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRB 163416
9 a.m.
This is a multi-part message in MIME format.
--------------050903050303010609070402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote:
> -----Original Message-----
> From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On
> Behalf Of ext Joe Pruett
> Sent: Sunday, March 04, 2012 2:11 AM
> To: users(a)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'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.
> what is the best procedure to follow to try and get to the bottom
of
> issues like this? might i be better off installing a regular os and
> then installing the vdsm package?
Installing Fedora 16 on the same kind of blade worked for me without any
problems. Therefore the "regular os + vdsm rpms" approach could help
you to sidestep the failing ovirt-node installation, but it will probably
not help you in analyzing and fixing ovirt-node related installation issues.
Best regards,
Hermann Huy
St.-Martin-Str. 76
81541 München
Tel: +49 89 5159 35744
Mob: +49 170 5630316
Email: hermann.huy(a)nsn.com
http://www.nokiasiemensnetworks.com/global/
Nokia Siemens Networks GmbH& Co. KG
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRA 88537
WEEE-Reg.-Nr.: DE 52984304
Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management
GmbH
Geschäftsleitung / Board of Directors: Hermann Rodler, Olaf Horsthemke
Vorsitzender des Aufsichtsrats / Chairman of supervisory board: Herbert Merz
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRB 163416
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--------------050903050303010609070402
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 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote:
<blockquote
cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated"
href="mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a>
[<a 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 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
href="http://ovirt.org/wiki/Working_with_gerrit.ovirt.org">h...
<blockquote
cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net"
type="cite">
<pre wrap="">
</pre>
<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
cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">
what is the best procedure to follow to try and get to the bottom of
issues like this? might i be better off installing a regular os and
then installing the vdsm package?
</pre>
</blockquote>
<pre wrap="">Installing Fedora 16 on the same kind of blade worked
for me without any
problems. Therefore the "regular os + vdsm rpms" approach could help
you to sidestep the failing ovirt-node installation, but it will probably
not help you in analyzing and fixing ovirt-node related installation issues.
Best regards,
Hermann Huy
St.-Martin-Str. 76
81541 München
Tel: +49 89 5159 35744
Mob: +49 170 5630316
Email: <a class="moz-txt-link-abbreviated"
href="mailto:hermann.huy@nsn.com">hermann.huy@nsn.com</a>
<a class="moz-txt-link-freetext"
href="http://www.nokiasiemensnetworks.com/global/">http://ww...
Nokia Siemens Networks GmbH & Co. KG
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRA 88537
WEEE-Reg.-Nr.: DE 52984304
Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks
Management GmbH
Geschäftsleitung / Board of Directors: Hermann Rodler, Olaf Horsthemke
Vorsitzender des Aufsichtsrats / Chairman of supervisory board: Herbert Merz
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRB 163416
</pre>
<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>
</body>
</html>
--------------050903050303010609070402--
10:04 a.m.
This is a multi-part message in MIME format.
--------------060303000202010500040804
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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(a)ovirt.org [mailto:users-bounces@ovirt.org] On
>> Behalf Of ext Joe Pruett
>> Sent: Sunday, March 04, 2012 2:11 AM
>> To: users(a)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?
--------------060303000202010500040804
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 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>
<br>
</body>
</html>
--------------060303000202010500040804--
12:34 p.m.
This is a multi-part message in MIME format.
--------------050209010500090303070404
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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(a)ovirt.org [mailto:users-bounces@ovirt.org] On
>>> Behalf Of ext Joe Pruett
>>> Sent: Sunday, March 04, 2012 2:11 AM
>>> To: users(a)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.
--------------050209010500090303070404
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 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>
</body>
</html>
--------------050209010500090303070404--
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--
6:14 p.m.
sumary: i am trying to install the ovirt-node image onto a hp dl360 g5
with radi6 controller (cciss driver). one raid6 array exported to one
virtual disk. official iso fails with python bug "global variable
'disk' not known", so i've downloaded a recent 2.3.0 stable image from
jenkins (ovirt-node-image-2.3.0-0.111.fc16.git5e8d287.iso) and get
generic failure. below is the /tmp/ovirt.log with only the backspace
noise from mkfs removed.
i've poked around the code a bit, and i don't see how this works
anywhere. it creates 4 partitions and makes the first one for efi and
makes it bootable, which grub then chokes over.
here's the log:
/sbin/restorecon set context
/var/cache/yum->unconfined_u:object_r:rpm_var_cache_t:s0
failed:'Read-only file system'
/sbin/restorecon set context /data2->unconfined_u:object_r:default_t:s0
failed:'Read-only file system'
/sbin/restorecon reset /boot-kdump context
system_u:object_r:boot_t:s0->system_u:object_r:default_t:s0
/sbin/restorecon reset /var/log/iscsiuio.log context
system_u:object_r:iscsi_log_t:s0->system_u:object_r:var_log_t:s0
/sbin/restorecon reset /var/cache/yum context
unconfined_u:object_r:file_t:s0->unconfined_u:object_r:rpm_var_cache_t:s0
/sbin/restorecon reset /etc/sysctl.conf context
system_u:object_r:etc_runtime_t:s0->system_u:object_r:system_conf_t:s0
/sbin/restorecon reset /data2 context
unconfined_u:object_r:root_t:s0->unconfined_u:object_r:default_t:s0
2012-03-05 23:33:57,065 - INFO - ovirt-config-installer - ::::live
device::::
/dev/sr
2012-03-05 23:33:57,636 - INFO - ovirtfunctions - Hardware
virtualization detected
2012-03-05 23:35:33,907 - DEBUG - ovirtfunctions - Translating:
2012-03-05 23:35:33,919 - DEBUG - ovirtfunctions - Translating:
2012-03-05 23:35:33,950 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0
2012-03-05 23:35:33,974 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:33,985 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p1
2012-03-05 23:35:34,011 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,021 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p2
2012-03-05 23:35:34,046 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,056 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p3
2012-03-05 23:35:34,078 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,087 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p4
2012-03-05 23:35:34,111 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,556 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p1
2012-03-05 23:35:34,579 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,580 - DEBUG - ovirtfunctions - Translating:
2012-03-05 23:35:34,590 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p2
2012-03-05 23:35:34,613 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,614 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p3
2012-03-05 23:35:34,638 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,638 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p4
2012-03-05 23:35:34,663 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,664 - DEBUG - ovirtfunctions - Translating:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:35:34,664 - DEBUG - ovirtfunctions - Translating: /dev/sr0
2012-03-05 23:36:31,763 - DEBUG - ovirtfunctions - Translating:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:31,763 - DEBUG - ovirtfunctions - Translating:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:32,064 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p1
2012-03-05 23:36:32,087 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:32,088 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p2
2012-03-05 23:36:32,112 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:32,112 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p3
2012-03-05 23:36:32,137 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:32,138 - DEBUG - ovirtfunctions - Translating:
/dev/cciss/c0d0p4
2012-03-05 23:36:32,161 - DEBUG - ovirtfunctions - Translated to:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:32,161 - DEBUG - ovirtfunctions - Translating:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:32,162 - DEBUG - ovirtfunctions - Translating: /dev/sr0
2012-03-05 23:36:55,025 - INFO - storage - Saving parameters
2012-03-05 23:36:55,025 - INFO - storage - Removing old LVM partitions
2012-03-05 23:36:55,026 - INFO - storage - Wiping LVM on HOSTVGDRIVE
/dev/mapper/3600508b1001031343520202020200004,
2012-03-05 23:36:55,101 - INFO - storage - Wiping LVM on ROOTDRIVE
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:55,200 - INFO - storage - Partitioning root drive:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:55,200 - INFO - ovirtfunctions - Wiping old boot sector
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00183747 s, 571 MB/s
2012-03-05 23:36:55,212 - INFO - ovirtfunctions - Wiping secondary gpt
header
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 3.592e-05 s, 28.5 MB/s
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
2012-03-05 23:36:55,791 - INFO - storage - Labeling Drive:
/dev/mapper/3600508b1001031343520202020200004
2012-03-05 23:36:55,792 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "mklabel gpt"
2012-03-05 23:36:55,882 - DEBUG - storage - Creating Root and RootBackup
Partitions
2012-03-05 23:36:55,883 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "mkpart EFI 1M
256M"
2012-03-05 23:36:55,928 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "mkpart primary ext2
256M 512M"
2012-03-05 23:36:55,971 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "mkpart primary ext2
512M 768M"
device-mapper: remove ioctl failed: Device or resource busy
device-mapper: create ioctl failed: Device or resource busy
Warning: parted was unable to re-read the partition table on
/dev/mapper/3600508b1001031343520202020200004 (Device or resource
busy). This means Linux won't know anything about the modifications you
made.
2012-03-05 23:36:56,009 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "set 1 boot on"
device-mapper: remove ioctl failed: Device or resource busy
device-mapper: create ioctl failed: Device or resource busy
Warning: parted was unable to re-read the partition table on
/dev/mapper/3600508b1001031343520202020200004 (Device or resource
busy). This means Linux won't know anything about the modifications you
made.
reload: 3600508b1001031343520202020200004 undef HP,LOGICAL VOLUME
size=447G features='0' hwhandler='0' wp=undef
`-+- policy='round-robin 0' prio=1 status=undef
`- 0:0:0:0 cciss!c0d0 104:0 active ready running
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
mkfs.vfat 3.0.12 (29 Oct 2011)
unable to get drive geometry, using default 255/63
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=Root
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
62496 inodes, 249856 blocks
12492 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
31 block groups
8192 blocks per group, 8192 fragments per group
2016 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=RootBackup
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
62496 inodes, 249856 blocks
12492 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
31 block groups
8192 blocks per group, 8192 fragments per group
2016 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
2012-03-05 23:37:02,862 - INFO - storage - Creating LVM partition
2012-03-05 23:37:02,862 - INFO - storage -
/dev/mapper/3600508b1001031343520202020200004,
2012-03-05 23:37:02,862 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "mkpart primary ext2
768M -1"
2012-03-05 23:37:02,904 - INFO - storage - Toggling LVM on
2012-03-05 23:37:02,904 - DEBUG - storage - parted
"/dev/mapper/3600508b1001031343520202020200004" -s "set 4 lvm on"
device-mapper: remove ioctl failed: Device or resource busy
device-mapper: remove ioctl failed: Device or resource busy
device-mapper: remove ioctl failed: Device or resource busy
device-mapper: create ioctl failed: Device or resource busy
device-mapper: create ioctl failed: Device or resource busy
device-mapper: remove ioctl failed: Device or resource busy
device-mapper: create ioctl failed: Device or resource busy
Warning: parted was unable to re-read the partition table on
/dev/mapper/3600508b1001031343520202020200004 (Device or resource
busy). This means Linux won't know anything about the modifications you
made.
Model: Linux device-mapper (multipath) (dm)
Disk /dev/mapper/3600508b1001031343520202020200004: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 256MB 255MB fat32 EFI boot
2 256MB 512MB 256MB ext2 primary
3 512MB 768MB 256MB ext2 primary
4 768MB 480GB 479GB primary lvm
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
2012-03-05 23:37:03,246 - DEBUG - storage -
['/dev/mapper/3600508b1001031343520202020200004p4']
2012-03-05 23:37:03,246 - INFO - storage - Creating physical volume on
/dev/mapper/3600508b1001031343520202020200004p4
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.0058987 s, 178 MB/s
Writing physical volume data to disk
"/dev/mapper/3600508b1001031343520202020200004p4"
Physical volume "/dev/mapper/3600508b1001031343520202020200004p4"
successfully created
2012-03-05 23:37:03,344 - INFO - storage - Creating volume group on
/dev/mapper/3600508b1001031343520202020200004p4
Volume group "HostVG" successfully created
2012-03-05 23:37:03,451 - INFO - storage - Creating swap partition
Logical volume "Swap" created
mkswap: /dev/HostVG/Swap: warning: don't erase bootbits sectors
on whole disk. Use -f to force.
Setting up swapspace version 1, size = 8216572 KiB
LABEL=SWAP, UUID=4dff7b5d-1714-4f3b-8d4a-8d288e7f5920
2012-03-05 23:37:03,837 - INFO - storage - Creating config partition
Rounding up size to full physical extent 8.00 MiB
Logical volume "Config" created
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=CONFIG
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
2048 inodes, 8192 blocks
409 blocks (4.99%) reserved for the super user
First data block=1
Maximum filesystem blocks=8388608
1 block group
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
2012-03-05 23:37:04,077 - INFO - storage - Creating log partition
Logical volume "Logging" created
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=LOGGING
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
131072 inodes, 524288 blocks
26214 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=536870912
16 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 30 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
2012-03-05 23:37:04,671 - INFO - storage - Creating data partition with
remaining free space
Logical volume "Data" created
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=DATA
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
28606464 inodes, 114418688 blocks
5720934 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
3492 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
2012-03-05 23:37:06,659 - INFO - storage - Mounting config partition
2012-03-05 23:37:06,874 - INFO - ovirtfunctions - File: /etc/fstab persisted
2012-03-05 23:37:06,886 - INFO - ovirtfunctions - Successfully
persisted: /etc/fstab
2012-03-05 23:37:06,887 - INFO - ovirtfunctions - Unmounting log partition
2012-03-05 23:37:07,340 - INFO - storage - Mounting data partition
2012-03-05 23:37:07,534 - INFO - storage - Completed HostVG Setup!
2012-03-05 23:37:07,694 - INFO - ovirtfunctions - File: /etc/shadow
persisted
2012-03-05 23:37:07,705 - INFO - ovirtfunctions - Successfully
persisted: /etc/shadow
2012-03-05 23:37:07,748 - INFO - install - Installing the image.
device-mapper: remove ioctl failed: Device or resource busy
Warning: parted was unable to re-read the partition table on
/dev/mapper/3600508b1001031343520202020200004 (No such file or
directory). This means Linux won't know anything about the
modifications you made.
device-mapper: create ioctl failed: Device or resource busy
device-mapper: remove ioctl failed: Device or resource busy
Error: Could not stat device
/dev/mapper/3600508b1001031343520202020200004p1 - No such file or directory.
Error: The device /dev/mapper/control is so small that it cannot
possibly store a file system or partition table. Perhaps you selected
the wrong device?
Warning: Error fsyncing/closing /dev/mapper/control: Invalid argument
device-mapper: remove ioctl failed: Device or resource busy
Warning: parted was unable to re-read the partition table on
/dev/mapper/3600508b1001031343520202020200004 (Device or resource
busy). This means Linux won't know anything about the modifications you
made.
device-mapper: create ioctl failed: Device or resource busy
device-mapper: remove ioctl failed: Device or resource busy
Error: The device /dev/mapper/control is so small that it cannot
possibly store a file system or partition table. Perhaps you selected
the wrong device?
Warning: Error fsyncing/closing /dev/mapper/control: Invalid argument
2012-03-05 23:37:08,683 - DEBUG - install - candidate: RootBackup
device-mapper: remove ioctl failed: Device or resource busy
Warning: parted was unable to re-read the partition table on
/dev/mapper/3600508b1001031343520202020200004 (Device or resource
busy). This means Linux won't know anything about the modifications you
made.
device-mapper: create ioctl failed: Device or resource busy
device-mapper: remove ioctl failed: Device or resource busy
Error: The device /dev/mapper/control is so small that it cannot
possibly store a file system or partition table. Perhaps you selected
the wrong device?
Warning: Error fsyncing/closing /dev/mapper/control: Invalid argument
2012-03-05 23:37:08,798 - INFO - install -
/dev/mapper/3600508b1001031343520202020200004p3
2012-03-05 23:37:08,798 - INFO - install -
/dev/mapper/3600508b1001031343520202020200004p3
2012-03-05 23:37:08,798 - DEBUG - install - e2label
"/dev/mapper/3600508b1001031343520202020200004p3" RootNew
2012-03-05 23:37:51,279 - DEBUG - install - multipath -l
"3600508b1001031343520202020200004" | awk '/ active / {print $3}' | head
-n1
2012-03-05 23:37:51,525 - DEBUG - install - partprobe "/dev/cciss/c0d0"
2012-03-05 23:38:00,844 - INFO - install - efi not detected, installing
grub2 configuraton
2012-03-05 23:38:00,845 - INFO - install - /sbin/grub2-install
/dev/cciss/c0d0 --boot-directory=/liveos --force
2012-03-05 23:38:18,367 - INFO - install - /sbin/grub2-setup: warn: This
GPT partition label has no BIOS Boot Partition; embedding won't be
possible!.
/sbin/grub2-setup: error: embedding is not possible, but this is
required for cross-disk install.
2012-03-05 23:38:18,367 - ERROR - install - GRUB efi setup failed
2012-03-05 23:38:18,367 - ERROR - install - Grub2 Installation Failed
12:39 p.m.
well, i couldn't find anything so i have gone with fc16 and vdsm for
now. i have found a doc/ui mismatch that i'll send separately.
On 03/05/2012 04:14 PM, Joe Pruett wrote:
sumary: i am trying to install the ovirt-node image onto a hp dl360
g5
with radi6 controller (cciss driver). one raid6 array exported to one
virtual disk. official iso fails with python bug "global variable
'disk' not known", so i've downloaded a recent 2.3.0 stable image from
jenkins (ovirt-node-image-2.3.0-0.111.fc16.git5e8d287.iso) and get
generic failure. below is the /tmp/ovirt.log with only the backspace
noise from mkfs removed.
i've poked around the code a bit, and i don't see how this works
anywhere. it creates 4 partitions and makes the first one for efi and
makes it bootable, which grub then chokes over.
12:48 p.m.
On 03/07/2012 01:39 PM, Joe Pruett wrote:
well, i couldn't find anything so i have gone with fc16 and vdsm
for
now. i have found a doc/ui mismatch that i'll send separately.
On 03/05/2012 04:14 PM, Joe Pruett wrote:
> sumary: i am trying to install the ovirt-node image onto a hp dl360 g5
> with radi6 controller (cciss driver). one raid6 array exported to one
> virtual disk. official iso fails with python bug "global variable
> 'disk' not known", so i've downloaded a recent 2.3.0 stable image
from
> jenkins (ovirt-node-image-2.3.0-0.111.fc16.git5e8d287.iso) and get
> generic failure. below is the /tmp/ovirt.log with only the backspace
> noise from mkfs removed.
>
> i've poked around the code a bit, and i don't see how this works
> anywhere. it creates 4 partitions and makes the first one for efi and
> makes it bootable, which grub then chokes over.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Sorry for the delay. I've
attempted testing with the patch provided
earlier by Huy, but couldn't install properly on a normal scsi setup.
I'll see what else can can do to narrow it down for both types of machines.
Joey
12:53 p.m.
On 03/07/2012 10:48 AM, Joey Boggs wrote:
On 03/07/2012 01:39 PM, Joe Pruett wrote:
> well, i couldn't find anything so i have gone with fc16 and vdsm for
> now. i have found a doc/ui mismatch that i'll send separately.
>
> On 03/05/2012 04:14 PM, Joe Pruett wrote:
>> sumary: i am trying to install the ovirt-node image onto a hp dl360 g5
>> with radi6 controller (cciss driver). one raid6 array exported to one
>> virtual disk. official iso fails with python bug "global variable
>> 'disk' not known", so i've downloaded a recent 2.3.0 stable
image from
>> jenkins (ovirt-node-image-2.3.0-0.111.fc16.git5e8d287.iso) and get
>> generic failure. below is the /tmp/ovirt.log with only the backspace
>> noise from mkfs removed.
>>
>> i've poked around the code a bit, and i don't see how this works
>> anywhere. it creates 4 partitions and makes the first one for efi and
>> makes it bootable, which grub then chokes over.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
Sorry for the delay. I've attempted testing with the patch provided
earlier by Huy, but couldn't install properly on a normal scsi setup.
I'll see what else can can do to narrow it down for both types of
machines.
i can certainly be a test subject when you're ready.
is there any significant difference between fc16+vdsm and straight
ovirt-node? since ovirt-node is based on fc16, it seems like they're
going to be almost identical in function. maybe a bit more cruft laying
around the disk, but anything of substance i should be aware of?
12:59 p.m.
is there any significant difference between fc16+vdsm and straight
ovirt-node? since ovirt-node is based on fc16, it seems like they're
going to be almost identical in function. maybe a bit more cruft laying
around the disk, but anything of substance i should be aware of?
Functionally they are equivalent. oVirt Node is for those who want to
limit the OS needed to install for large deployments of hypervisors. Or
for those who have security considerations who want to enforce a more
locked down environment.
4432
days inactive
4435
days old
10 comments
4 participants
participants (4)
-
Huy, Hermann (NSN - DE/Munich) -
Joe Pruett -
Joey Boggs -
Perry Myers