Re: LDOM commands return Device not configured
Jamie Luck <[email protected]> Sat, 01 Aug 2020 03:33:27 +0000
| Newsgroups | gmane.os.openbsd.sparc |
|---|---|
| Message-ID | <s4DgoKMpGvsiEU_4GQi-s6vBUIgolXagKcXHh20bOp-WVCEF8a0zeAa4vdEgNQJutm_QfETgYAWFprX7acCfjFXQtmcL8GjW8t_3Jgk0aP8=@jamieluck.com> |
Hey Andrew, thanks for the reply. > I found it was necessary to use OBSD 6.3 or earlier to create LDOM config= s on my T1000 > You will need to restore to the factory-default config first if this is t= he case. I gave OpenBSD 6.3 a try, but I got the same results as with 6.7: # ldomctl dump ldomctl: cannot open /dev/hvctl: Device not configured # ldomctl list ldomctl: cannot open /dev/hvctl: Device not configured # uname -a OpenBSD terminator.local 6.3 GENERIC.MP#486 sparc64 Do you know of a more low-level way to read the contents of the NVRAM? I've tried to reset it a few times but it doesn't seem to have have an effect. I'm also curious about how to probe the device for the presence of the sun4v hypervisor hardware- it doesn't report any faults from extended POST so I'm sure it's there, just not being recognized.