Again no ota updates in system panel in Monterey beta 10 --> RC

[82ghost82]

Hi! It seems apple changed again something with the ota updates?
Running Monterey in qemu as a test system, vmm flag enabled.

smbios: imacpro1,1
csr-active-config: 7w8AAA== (0xef0f0000) --> I have an unsealed volume, this value shouldn't prevent ota updates to show (Apple internal disabled)
securebootmodel: disabled

From beta 9 to 10, beta 8 to 9, beta 7 to 8 (with oc updated accordingly) all ok, ota updates showed in system preference panel (full installer).

RC isn't showing up.

[khronokernel]

Apple removed VMM from the Pallas Catalog temporarily, should be restored in the coming days. Either use a non-T2 SMBIOS or set SecureBootModel with a T2 ID and ensure VMM is not exposed

Nothing to be done on our end, wait for Apple to fix this

[82ghost82]

Sorry to reopen this, but something doesn't seem to work.
Two machines: one production with big sur, one test for monterey.

In big sur 11.6 the ota updates showed today: both big sur 11.6.1 and monterey 12.0.1
In Monterey beta 10 no update is shown.

VMM flag is in both machines (both run on qemu), imacpro1,1, so VMM should have been added again to the catalog, or am I wrong?

The differences in configurations:

Big Sur
Sealed volume
csr-active-config: AAAAAA==
SecureBootModel: x86legacy

Monterey
Unsealed volume, due to lack of kepler drivers
csr-active-config: 7w8AAA==
SecureBootModel: Disabled

[ofawx]

Just to add my experience as in a similar situation to @82ghost82:

QEMU -> VMM flag
MacPro7,1
Monterey b10
Sealed volume
csr-active-config: AAAAAA==
SecureBootModel: x86legacy

So a similar config to 82ghost82's Big Sur above EXCEPT mine is Monterey b10, yet Monterey 12.0.1 did NOT show for me.
CLI softwareupdate did show the full installer however:

zsh % sudo softwareupdate --list-full-installers --force       
Finding available software
Software Update found the following full installers:
* Title: macOS Monterey, Version: 12.0.1, Size: 12128428704K, Build: 21A559

In the end I downloaded the release .pkg and installed it without issues; I was having too many beta related issues to wait.

Could it be something specific to Monterey b10 (or all Montereys going forwards)?

[82ghost82]

@ofawx
I'm installing 12.0.1, I propose to wait for the next 12.1 release and see what happens.
khronokernel suggests to patch VMM and use T2 id.

Since SecureBootModel=x86legacy with ApECID=0 sets the T2 id to the first 8 bytes of the system id we should be ok.
On macOS 11 and newer the dedicated x86legacy model always uses ApECID. When this configuration setting is left as 0 first 8 bytes of system-id variable are used instead.

I propose also to apply your patches (VMM-->XXX and kern.hv_vmm_present-->kern.hv_xxx_present).

I will not unseal the volume and so I wont install any nvidia driver, so to be able to have csr-active-config: AAAAAA==, just to see what happens.

If nothing comes up in software update I think this will need to be reopened, and or discussed again.