TBOOT: ERR: CPU does not support SMX

[myne something]

Hi all. 

Been playing around with this project on and off for a while. Great idea. 

Getting error: 

TBOOT: ERR: CPU does not support SMX

Depending on whether it's set to BIOS CSM or UEFI mode, it'll stop with that during the initial load from the iso (bios), or it'll actually install but error right at the end of installation with "install failed" and no other information. It'll then boot but throw CPU does not support SMX (uefi).

Have googled a lot about SMX and can't find too much on how to enable/check for it. 

Older versions like 7.00 Build 1340 used to work on this machine - even in virtualbox/vmware player.

9 never has does not.

CPU: Kaby Lake 7600k.

Chipset: Z170 VT-X enabled, TPM 2.0 enabled.

Apparently this CPU doesn't support V-Pro but I haven't been able to find out whether SMX is part of that or not.

I realise this may be by design that it should not work. 

Is Vpro now a required feature?

I realise you may not want to support versions for ordinary desktop users.

But if it IS supposed to work... 

What can I do to figure this out?

Thanks!

[Daniel Smith]

---- On Sat, 15 Jun 2019 08:09:20 -0400 myne something <myn...@gmail.com> wrote ----

Greetings Myne Something,

Apologies that no one else from the community has take the time to respond.

The focus of OpenXT is hardware rooted security which we use Intel's TXT capability to achieve this approach. The CPU mode for TXT is called Secure Mode Execution, i.e. SMX. Unfortunately in the infinite wisdom of Intel Marketing, TXT is typically only available on V-Pro platforms. With that said, you can install OpenXT without TXT support it is that you will not be able use the strong assurances TXT can provide. To install with TXT, during the installation select that you do not want to install "Measured Launch".

Speaking for myself, I want to see OpenXT be usable by any type of user. What would better enable that is for hardware vendors to start making strong security mechanism like TXT more prolific instead of reserving it only for business class devices.

V/r,

Daniel P. Smith

Apertus Solutions, LLC

[myne something]

Thanks for the reply!

I have tried without measured launch. 

It still doesn't work. 

In Vmware workstation it wont even boot from the iso to install it. It loops.

  TBOOT: IA32_FEATURE_CONTROL_MSR: 00000005

  TBOOT: ERR: CPU does not support SMX

On Virtualbox UEFI mode installs but won't boot with the error: 

  Failed to load image: not found

  start_image() returned not found

and cycles through the usual boot menu items "Boot Failed Open XT/Console/etc

And on actual bare metal it gets to the end and says "Installation failed" with no error at all!

But, Build 1340 works fine (obviously without Measured Launch).

I'll run through a bare metal install and take a few snaps to upload in a bit.

Cheers.

[myne something]

Here's the install error on bare metal.

On Monday, July 1, 2019 at 11:20:30 PM UTC+10, Daniel Smith wrote:

[Daniel Smith]

Thank you! Looks like you tripped over a bug in our installer. We have opened up a JIRA ticket if you want to track the issue.

https://openxt.atlassian.net/browse/OXT-1632

V/r,

Daniel P. Smith

Apertus Solutions, LLC

---- On Tue, 02 Jul 2019 06:32:29 -0400 myne something <myn...@gmail.com> wrote ----

Here's the install error on bare metal.

On Monday, July 1, 2019 at 11:20:30 PM UTC+10, Daniel Smith wrote:

--

You received this message because you are subscribed to the Google Groups "openxt" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openxt+un...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openxt/1bd111ee-1465-4430-b523-2e346bb28c13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason Andryuk]

On Tue, Jul 2, 2019 at 1:33 PM Daniel Smith
<dps...@apertussolutions.com> wrote:
>
> Thank you! Looks like you tripped over a bug in our installer. We have opened up a JIRA ticket if you want to track the issue.
>
> https://openxt.atlassian.net/browse/OXT-1632

Myne,

Installation fails since you have two drives with ESP partitions. If
you are trying to dual-boot, it will not work. You could either
remove one of the drives and install OpenXT on the other. Or wipe
both drives and let OpenXT install onto one of them. Obviously that's
only if you are willing to sacrifice the data.

Regards,
Jason

[myne something]

Ah.

That's a pain. M.2 on the back side of the board. Not easy to remove.

I'm not exactly ready to commit that much effort to something that doesn't definitely work.

Any idea why it no longer works in VMware workstation etc like the old builds?

[myne something]

Thanks!

I'll keep an eye on it.

On Wednesday, July 3, 2019 at 5:03:24 AM UTC+10, Jason Andryuk wrote:

[myne something]

does this reply work? They keep getting auto deleted..?

On Wednesday, July 3, 2019 at 5:03:24 AM UTC+10, Jason Andryuk wrote: