Mike Larkin <[email protected]> wrote: > On Sat, Sep 22, 2018 at 09:39:18AM -0400, [email protected] wrote: > > >Synopsis: vmd fails to run vms on ThinkPad 25 > > >Category: system > > >Environment: > > System : OpenBSD 6.3 > > Details : OpenBSD 6.3 (GENERIC.MP) #11: Thu Sep 20 16:05:37 CEST > > 2018 > > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > On my ThinkPad 25, trying to start a virtual machine with vmctl fails, > > (where debian.img is an image prepared in QEMU): > > thinkpad-25:~$ doas vmctl start "Debian" -Lc -m 512m -d debian.img > > vmctl: start vm command failed: No such file or directory > > > > The following is logged to /dev/console: > > cpu2: failed to enter VMM mode > > > > And these lines in /var/log/daemon: > > Sep 21 16:32:33 thinkpad-25 vmd[10504]: Debian: create vmm ioctl failed - > > exiting: Input/output error > > Sep 21 16:32:33 thinkpad-25 vmd[80021]: Debian: failed to start vm: No such > > file or directory > > > > I have verified that VMX is enabled in the firmware, and updated it to > > the latest version available from Lenovo. I've dual booted the computer to > > Windows 10 and confirmed that Hyper-V works there, so it's definitely > > working > > on the hardware side. > > > > >How-To-Repeat: > > $ doas rcctl enable vmd > > $ doas rcctl start vmd > > $ doas vmctl start <anything> > > >Fix: > > Unknown > > > > See below. > > -ml > > > > > dmesg: > > OpenBSD 6.3 (GENERIC.MP) #11: Thu Sep 20 16:05:37 CEST 2018 > > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 16918003712 (16134MB) > > avail mem = 16398188544 (15638MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6f070000 (62 entries) > > bios0: vendor LENOVO version "N1QET77W (1.52 )" date 07/04/2018 > > bios0: LENOVO 20K70004US > > acpi0 at bios0: rev 2 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT BOOT > > BATB SLIC SSDT SSDT SSDT WSMT SSDT SSDT DBGP DBG2 MSDM SSDT SSDT DMAR ASF! > > FPDT UEFI > > acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4) > > RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP08(S4) RP09(S4) RP10(S4) RP11(S4) > > RP12(S4) RP13(S4) [...] > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpihpet0 at acpi0: 23999999 Hz > > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, 1297.47 MHz > > cpu0: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > > cpu0: 256KB 64b/line 8-way L2 cache > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > > cpu0: apic clock running at 24MHz > > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, 1086.37 MHz > > cpu1: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > > cpu1: 256KB 64b/line 8-way L2 cache > > cpu1: failed to identify > > Try booting with the power cord attached or selecting high performance mode > in the BIOS. You have CPUs that are in slow mode and failing to hatch > properly.
Actually, this could also be related to the slow-scroll problem.... Shrug.
