Bug 223428 - sysutils/vm-bhyve: ERROR: it doesn't look like your cpu supports bhyve (missing EPT)
Summary: sysutils/vm-bhyve: ERROR: it doesn't look like your cpu supports bhyve (missi...
Status: Closed DUPLICATE of bug 222496
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-04 16:03 UTC by bergerkos
Modified: 2017-12-18 14:09 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bergerkos 2017-11-04 16:03:15 UTC
vm refuses to work with the error message above. Here is one example:
#vm switch list

/usr/local/sbin/vm: ERROR: it doesn't look like your cpu supports bhyve (missing EPT)

Here is my CPU information from dmesg:
#dmesg | less

CPU: Intel(R) Pentium(R) CPU G2030 @ 3.00GHz (3003.02-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xd9ae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,TSCDLT,XSAVE,OSXSAVE>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  Structured Extended Features=0x281<FSGSBASE,SMEP,ERMS>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: Basic Features=0xda0400<SMM,INS/OUTS,TRUE>
        Pin-Based Controls=0x7f<ExtINT,NMI,VNMI,PreTmr>
        Primary Processor Controls=0xfff9fffe<INTWIN,TSCOff,HLT,INVLPG,MWAIT,RDPMC,RDTSC,CR3-LD,CR3-ST,CR8-LD,CR8-ST,TPR,NMIWIN,MOV-DR,IO,IOmap,MTF,MSRmap,MONITOR,PAUSE>
        Secondary Processor Controls=0xff<APIC,EPT,DT,RDTSCP,x2APIC,VPID,WBINVD,UG>
        Exit Controls=0xda0400<PAT-LD,EFER-SV,PTMR-SV>
        Entry Controls=0xda0400
        EPT Features=0x6114141<XO,PW4,UC,WB,2M,INVEPT,single,all>
        VPID Features=0xf01<INVVPID,individual,single,all,single-globals>

And finally, bhyve itself does work from cli, I was able to install windows 10 and boot it etc.
Comment 1 bergerkos 2017-11-04 18:57:37 UTC
Ok, this problem was caused by the kernel boot command line (kernel -v) producing verbose boot message. That's how the needed part about the kernel VT support was not in the format expected by the vm-util script, which was looking for EPT on the same line with VT-x.

Don't know, though, if the possibility of the verbose boot message should not be taken into account...

That's not for me to decide.
Thank you for the great job, other than that the port is working all right.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2017-11-04 21:12:59 UTC
To which port does this PR apply?
Comment 3 bergerkos 2017-11-05 09:19:16 UTC
vm-bhyve
Comment 4 bergerkos 2017-11-05 14:42:48 UTC
Sorry, didn't find where to mention this: the PR applies to the port sysutils/vm-bhyve.
Comment 5 Dmitry Morozovsky freebsd_committer freebsd_triage 2017-12-18 14:09:25 UTC
It seems to be duplicate of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222496

*** This bug has been marked as a duplicate of bug 222496 ***