Fusion

Background:

I'm running Fusion Professional Version 13.6.4 (24832108) under Tahoe 26.0.1 on a  MacBookPro16,1 with an 8-Core Intel Core i9 processor.  I have ESXi 9.0.1 #1 SMP Release build-24957456 running as a VM under Fusion.

When I attempt to boot a Linux guest under this ESX instance, I get the following question: "Virtualized Intel VT-x/EPT is not supported on this platform. Continue without virtualized Intel VT-x/EPT?"

But this question is inappropriate: in the Linux guest's .vmx file I have hv.capable = "0x1" set and I've checked "Enable hypervisor applications in this virtual machine" in the advanced section of the 9.0.1 VM's Processor and Memory settings.

Answering the question either way leads to the same result: the Linux guest doesn't boot.

That leads to the following questions:

1. Why does this boot-time question appear?  As my macOS host's CPU supports these virtualization instructions and they've been enabled for both the ESXi VM and its Linux guest, there's no apparent reason for it to be issued. (This problem also doesn't occur with ESXi 8.0.x VMs.)
2. Is this a bug in Fusion, in ESXi 9.0.1, their interaction, or something else?
3. Could it be that ESXi 9.0.1 no longer supports my Mac Pro's CPU?  (If so, the boot-time question is horribly misleading and should be rephrased.)

Thanks for your attention.

Have you tried Fusion 25H2? Fusion 13.6.4 isn't qualified for Tahoe.

Background:

I'm running Fusion Professional Version 13.6.4 (24832108) under Tahoe 26.0.1 on a  MacBookPro16,1 with an 8-Core Intel Core i9 processor.  I have ESXi 9.0.1 #1 SMP Release build-24957456 running as a VM under Fusion.

When I attempt to boot a Linux guest under this ESX instance, I get the following question: "Virtualized Intel VT-x/EPT is not supported on this platform. Continue without virtualized Intel VT-x/EPT?"

But this question is inappropriate: in the Linux guest's .vmx file I have hv.capable = "0x1" set and I've checked "Enable hypervisor applications in this virtual machine" in the advanced section of the 9.0.1 VM's Processor and Memory settings.

Answering the question either way leads to the same result: the Linux guest doesn't boot.

That leads to the following questions:

1. Why does this boot-time question appear?  As my macOS host's CPU supports these virtualization instructions and they've been enabled for both the ESXi VM and its Linux guest, there's no apparent reason for it to be issued. (This problem also doesn't occur with ESXi 8.0.x VMs.)
2. Is this a bug in Fusion, in ESXi 9.0.1, their interaction, or something else?
3. Could it be that ESXi 9.0.1 no longer supports my Mac Pro's CPU?  (If so, the boot-time question is horribly misleading and should be rephrased.)

Thanks for your attention.

Have you tried Fusion 25H2? Fusion 13.6.4 isn't qualified for Tahoe.

Background:

I'm running Fusion Professional Version 13.6.4 (24832108) under Tahoe 26.0.1 on a  MacBookPro16,1 with an 8-Core Intel Core i9 processor.  I have ESXi 9.0.1 #1 SMP Release build-24957456 running as a VM under Fusion.

When I attempt to boot a Linux guest under this ESX instance, I get the following question: "Virtualized Intel VT-x/EPT is not supported on this platform. Continue without virtualized Intel VT-x/EPT?"

But this question is inappropriate: in the Linux guest's .vmx file I have hv.capable = "0x1" set and I've checked "Enable hypervisor applications in this virtual machine" in the advanced section of the 9.0.1 VM's Processor and Memory settings.

Answering the question either way leads to the same result: the Linux guest doesn't boot.

That leads to the following questions:

1. Why does this boot-time question appear?  As my macOS host's CPU supports these virtualization instructions and they've been enabled for both the ESXi VM and its Linux guest, there's no apparent reason for it to be issued. (This problem also doesn't occur with ESXi 8.0.x VMs.)
2. Is this a bug in Fusion, in ESXi 9.0.1, their interaction, or something else?
3. Could it be that ESXi 9.0.1 no longer supports my Mac Pro's CPU?  (If so, the boot-time question is horribly misleading and should be rephrased.)

Thanks for your attention.