Ldomctl/ldomd related system hang on T5240?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Ldomctl/ldomd related system hang on T5240?

Trevis
Hi all,

I have been trying to setup ldoms on a Sun T5240. Every ldom.conf seems
to lead to a system hang at "OpenBoot initializing"(as reported in the
ILOM).
The T2000 that I have hasn't provided any issue. So I'm guessing there
is some difference with ILOM instead of ALOM configuration that I've
missed, or maybe
something different about the hypervisor version?

An example of ldom.conf that causes the hang:
domain primary {
        vcpu 16
        memory 8G
}

Versions from "->show /HOST" on the T5420's ILOM
hypervisor_version = Hypervisor 1.7.4.a 2009/09/21 08:25
obp_version = OBP 4.30.4 2009/08/19 07:25
post_version = POST 4.30.4 2009/08/19 07:50
sysfw_version = Sun System Firmware 7.2.4.e 2009/09/21 09:50

Running showhost on the T2000's ALOM
Sun-Fire-T2000 System Firmware 6.7.11  2010/10/12 12:33

Host flash versions:
OBP 4.30.4.b 2010/07/09 13:48
Hypervisor 1.7.3.c 2010/07/09 15:14
POST 4.30.4.b 2010/07/09 14:24


Resetting the system on the T5240 with the the ldom.conf from above
results
in just the | spinner and no other output.

Does anyone have some insight here?

Thanks!

Trevis

PS: Looking through the archives, I've found reference to a bug, that I
have
encountered as well, where the memory left for the primary domain is not
correctly calculated. Should anyone be interested in being somewhat of I
would be more than happy to attempt to tackle that issue.

Reply | Threaded
Open this post in threaded view
|

Re: Ldomctl/ldomd related system hang on T5240?

rodent
On Sat, Dec 10, 2016 at 09:19:30PM -0500, Trevis wrote:

> Hi all,
>
> I have been trying to setup ldoms on a Sun T5240. Every ldom.conf seems
> to lead to a system hang at "OpenBoot initializing"(as reported in the
> ILOM).
> The T2000 that I have hasn't provided any issue. So I'm guessing there
> is some difference with ILOM instead of ALOM configuration that I've
> missed, or maybe
> something different about the hypervisor version?
>
> An example of ldom.conf that causes the hang:
> domain primary {
>        vcpu 16
>        memory 8G
> }
>
> Versions from "->show /HOST" on the T5420's ILOM
> hypervisor_version = Hypervisor 1.7.4.a 2009/09/21 08:25
> obp_version = OBP 4.30.4 2009/08/19 07:25
> post_version = POST 4.30.4 2009/08/19 07:50
> sysfw_version = Sun System Firmware 7.2.4.e 2009/09/21 09:50
>
> Running showhost on the T2000's ALOM
> Sun-Fire-T2000 System Firmware 6.7.11  2010/10/12 12:33
>
> Host flash versions:
> OBP 4.30.4.b 2010/07/09 13:48
> Hypervisor 1.7.3.c 2010/07/09 15:14
> POST 4.30.4.b 2010/07/09 14:24
>
>
> Resetting the system on the T5240 with the the ldom.conf from above
> results
> in just the | spinner and no other output.
>
> Does anyone have some insight here?
>
> Thanks!
>
> Trevis
>
> PS: Looking through the archives, I've found reference to a bug, that I
> have
> encountered as well, where the memory left for the primary domain is not
> correctly calculated. Should anyone be interested in being somewhat of I
> would be more than happy to attempt to tackle that issue.

Have the same issue on both of my T5120s after updating the firmware to
Version 3.0.12.8.a r108523. ldomd is disabled at the moment because of it.
Actually, on my setup, the boot makes it to where it starts ldomd. Then, the
system hangs completely and needs reset /SYS. This wasn't an issue with the
previous firmware version.

Reply | Threaded
Open this post in threaded view
|

Re: Ldomctl/ldomd related system hang on T5240?

Trevis
On 2016-12-11 07:12, [hidden email] wrote:
>
> Have the same issue on both of my T5120s after updating the firmware to
> Version 3.0.12.8.a r108523. ldomd is disabled at the moment because of
> it.
> Actually, on my setup, the boot makes it to where it starts ldomd.
> Then, the
> system hangs completely and needs reset /SYS. This wasn't an issue with
> the
> previous firmware version.

Interesting, what you've described isn't exactly what I'm getting, since
I don't
even make it to OpenBSD booting. Issues with the firmware leads me to
think maybe
there is something that has changed. Unfortunately I don't have access
to different
firmware versions to test with. Unless there is a way to get those
without a
presumably expensive Oracle support contract?