Local stuck on Host Machine install

I’m having a heck of a time reinstalling Local and getting the VM to work.

Local stuck on Host Machine install
Version: 2.3.0 Windows
Also tried 2.2.4 and had issues as well

VM: “This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU.”
Version: Oracle VM VirtualBox 5.2.4
Operating System: Ubuntu (32-bit)
Base Memory: 1024 MB
Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX, KVM Paravirtualization
Video Memory: (264.9 KB)
37 MB
Remote Desktop Server: Disabled
Video Capture: Disabled
Host Driver: Windows DirectSound
Controller: ICH AC97
Adapter 1: Intel PRO/1000 MT Desktop (NAT)
Adapter 2: Intel PRO/1000 MT Desktop (Host-only Adapter, ‘VirtualBox Host-Only Ethernet Adapter #2’)
USB: Disabled
Shared Folders: 1

Computer: HP Spectre x360 Conv 15-bl012dx
Model Number: Z4Z35UA

Tried:

  • BIOS Virtualization Enabled
  • Change CHIP option in VM settings
  • Increased video memory
  • Nothing connected to computer (i.e. USB drive)
  • No Hyper-V on computer

local-by-flywheel.log

Any ideas of what to try next?

No ideas I take it, since I haven’t heard back from Support.

I tried the 2.3.1 Pre-release of Local with the 5.2.12 release of Oracle VM. Same thing.

Anyone know what this means?
“This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU.”
Oracle gives me this message when I start it up via Local.

I’m not certain but it could be that your computer’s CPU is only a 32 bit CPI and Local requires a 64 bit CPU.

I appreciate your thinking about this issue. Id think the same if Local didnt work on this same laptop last year. But perhaps some setting got changed along the way?

From Flywheel the requirements for Windows:

4GB RAM
1GB Disk Space
Windows 7, 8, 8.1, or 10
CPU with VT-x or AMD-v support

This may provide a bit more info.