[Re: Re: Generic LDOM Configuration not working on Sunfire T2000]

Hi! thanks, that seemed to do the trick as far as the initial config
is concerned.

Sadly, I ran into a bunch of errors and warnings at the openboot prompt:

EROR: /pci@780: Invalid hypervisor argument(s), function: b4

EROR: /pci@780: Invalid hypervisor argument(s), function: b4

EROR: /pci@780: Invalid hypervisor argument(s), function: b5

WARNING: /pci@7c0/pci@0/pci@1/network: Missing network-vpd MD node

WARNING: /pci@7c0/pci@0/pci@1/network: Missing network-vpd MD node

...

ERROR: boot-read fail

Evaluating:

Can't locate boot device


I thought I had messed up the ldom configuration big time, so I set
the bootmode in the SC to the factory default, then rebooted to the
primary domain, checked the configuration which is totally valid,
did the whole procedure described in man ldomctl again, and rebooted
to find the exact same errors at the openboot prompt.

This is getting nasty and tricky. My config is really, really nothing
complicated. This system has 32 GB memory and 32 cores:

domain primary {
        vcpu 8
        memory 6G
}

domain pink {
        vcpu 6
        memory 6G
        vdisk "/home/pink/vdisk0"
        vnet
}

domain floyd {
        vcpu 6
        memory 6G
        vdisk "/home/floyd/vdisk0"
        vnet
}

Does this look familiar in any way?

Any hint appreciated

----- Forwarded message from Mark Kettenis <[email protected]> -----

Date: Mon, 4 Apr 2022 21:08:50 +0200 (CEST)
From: Mark Kettenis <[email protected]>
To: Abu Hussain Al Mukhtar <[email protected]>
Subject: Re: Generic LDOM Configuration not working on Sunfire T2000
Message-ID: <[email protected]>

> Date: Fri, 1 Apr 2022 21:43:16 +0000
> From: Abu Hussain Al Mukhtar <[email protected]>
> 
> Hi,
> 
> I am on the above mentioned hardware running OpenBSD 70 -stable.
> Someone mentioned in another thread that LDOM problems on a T1000 were
> solved by upgrading the firmware to 6.7.13. My firmware version is
> close enough - 6.7.12, so I doubt that this has to do with firmware.
> 
> Anyway, while trying to follow the ldom man pages, tedu's LDOM guide
> and/or the ldom guide in undeadly.org, the setup fails: after
> reaching the point where I see the new logical domain marked as 'next'
> after running #ldomctl list, I halt the system and reset the ALOM as
> instructed. It seems until that point that the new configuration has
> worked and was indeed dumped to non-volatile storage of the SP.
> 
> However, the only thing that happens is that the machine does not
> reboot to my primary domain. Stuck in the openboot prompt, I load
> the generic kernel for the primary domain, which then boots...but
> then #ldomctl status only shows the primary domain, nothing more.
> 
> What might I be missing here? As stated before and I reiterate, I
> am really following instructions step by step - I even went so far
> as to name my additional domains 'puffy' and 'salmah' just in case.
> 
> Thanks in advance for any useful hints.

Try to explicitly assign memory to the primary domain.  The code that
tries to calculate the remaining amount of memory doesn't always get
it correct.  When assigning memory, make sure you leave some meory
unuassigned such that it is available to the hypervisor.  I believe
something like 512MB should be sufficient.

----- End forwarded message -----