logical domains on Netra T5220

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

logical domains on Netra T5220

Matthias Bauer-3

Hi,
on a Netra T5220 (OBP 4.30.2.b, Sun System Firmware 7.2.2.e, Hypervisor 1.7.2.a. ILOM Version 3.0.3.20.e),
with OpenBSD 66-snapshot, I went through the steps as suggested in ldomctl(8).

The ldomctl list showed factory-default as [current] and one of the guest systems as [next].
After 'halt' I got the OBP 'ok' prompt, after '#.' the ILOM 'sc>'.

Following 'reset -c' only the factory-default started, (the [next] flag disappeared from the
list output), and 'cu -l /dev/ttyV0' returned
 Device not configured

ldomctl list              shows guest systems,
ldomctl start $aguest     returns "unknown guest".

What went wrong here?

Best regards

Matthias

Reply | Threaded
Open this post in threaded view
|

Re: logical domains on Netra T5220

Mark Kettenis
> Date: Thu, 5 Sep 2019 11:50:42 +0200
> From: Matthias Bauer <[hidden email]>
>
> Hi,
> on a Netra T5220 (OBP 4.30.2.b, Sun System Firmware 7.2.2.e,
> Hypervisor 1.7.2.a. ILOM Version 3.0.3.20.e), with OpenBSD
> 66-snapshot, I went through the steps as suggested in ldomctl(8).
>
> The ldomctl list showed factory-default as [current] and one of the
> guest systems as [next].  After 'halt' I got the OBP 'ok' prompt,
> after '#.' the ILOM 'sc>'.
>
> Following 'reset -c' only the factory-default started, (the [next]
> flag disappeared from the list output), and 'cu -l /dev/ttyV0'
> returned Device not configured
>
> ldomctl list              shows guest systems,
> ldomctl start $aguest     returns "unknown guest".
>
> What went wrong here?

That means the Hypervisor didn't really like the configuration
generated by ldomctl(8) and booted with the factory-defeault
configuration.  There might have been some messages on the console
about this during the reset of the machine.

The ldomctl(8) code isn't very good at checking various constraints.
The most common problem is that there isn't actually enough memory for
the domains.  The Hypervisor needs some memory too so you can't
actually use all the memory in the system.  But how much memory is
needed by the Hypervisor isn't always obvious.  I recommend testing a
configuration where you explicitly assign memory to each domain and
leave at least 512MB of memory unassigned.

Cheers,

Mark