Good, perhaps VB team can consider making it a checkbox option on the GUI...loyukfai wrote:This customization:Code: Select all
<ExtraDataItem name="VBoxInternal/NEM/UseRing0Runloop" value="0"/>
Cheers.
Good, perhaps VB team can consider making it a checkbox option on the GUI...loyukfai wrote:This customization:Code: Select all
<ExtraDataItem name="VBoxInternal/NEM/UseRing0Runloop" value="0"/>
If you can't turn Hyper-V off completely you won't get good or any performance with Virtualbox. And if you can't turn Credential Guard off, then you can't turn Hyper-V off. Thanks to Microsoft for their high-handed use of VT-x. They never got taught as a child to share their toys, I guess...RWS's log wrote:00:00:01.763785 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:01.792383 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
That's not your problem, the use of a Hyper-V component is. From the looks of it, you must disable "Credential Guard", just like 'scottgus1" rightly said so.RWS wrote:VirtualBox is detecting the processor as a Gen 6 Intel i7-6700K, when in fact it is a Gen 8 i7-8850H processor
Plus, we won't be able to easily replicate your setup, QNX is commercial software, not readily available for testing...RWS's log wrote:00:00:01.731590 Guest OS type: 'QNX' 00:00:01.735594 File system of 'C:\Temp\QNX630SP3Runtime.iso' (DVD) is ntfs
I'm not a developer, just a forum moderator.FirstVoid wrote:I appreciate one of the developers weighing in on this
Sure... the guest option doesn't change the state of the host. Hyper-V is going to be activated independently of your guest choice.FirstVoid wrote:Just to confirm first of all it's not limited to QNX, any guest OS chosen shows this behavior
Again, the "family" identification doesn't have an effect on the capability of VirtualBox to identify what your host's CPU can or can't do. You isolated a single line which is pretty generic, while VirtualBox does a really thorough analysis of your CPU's capabilities later on. I'll give you an example, this is your complete CPU capabilities:FirstVoid wrote:I suspect a possible miss-identification of the CPU due to the fact it can't detect one of the features required and then takes a guess
and here are some selective differences between your CPU and mine. Your is the first two columns, mine are the 3rd and 4th, with the last one being your problem:Code: Select all
00:00:02.177047 Features 00:00:02.177048 Mnemonic - Description = guest (host) 00:00:02.177048 FPU - x87 FPU on Chip = 1 (1) 00:00:02.177049 VME - Virtual 8086 Mode Enhancements = 1 (1) 00:00:02.177050 DE - Debugging extensions = 1 (1) 00:00:02.177051 PSE - Page Size Extension = 1 (1) 00:00:02.177051 TSC - Time Stamp Counter = 1 (1) 00:00:02.177052 MSR - Model Specific Registers = 1 (1) 00:00:02.177052 PAE - Physical Address Extension = 0 (1) 00:00:02.177053 MCE - Machine Check Exception = 1 (1) 00:00:02.177054 CX8 - CMPXCHG8B instruction = 1 (1) 00:00:02.177054 APIC - APIC On-Chip = 1 (1) 00:00:02.177055 SEP - SYSENTER and SYSEXIT Present = 0 (1) 00:00:02.177055 MTRR - Memory Type Range Registers = 1 (1) 00:00:02.177056 PGE - PTE Global Bit = 1 (1) 00:00:02.177057 MCA - Machine Check Architecture = 1 (1) 00:00:02.177057 CMOV - Conditional Move instructions = 1 (1) 00:00:02.177058 PAT - Page Attribute Table = 1 (1) 00:00:02.177060 PSE-36 - 36-bit Page Size Extension = 1 (1) 00:00:02.177060 PSN - Processor Serial Number = 0 (0) 00:00:02.177061 CLFSH - CLFLUSH instruction = 1 (1) 00:00:02.177061 DS - Debug Store = 0 (1) 00:00:02.177062 ACPI - Thermal Mon. & Soft. Clock Ctrl. = 0 (1) 00:00:02.177062 MMX - Intel MMX Technology = 1 (1) 00:00:02.177063 FXSR - FXSAVE and FXRSTOR instructions = 1 (1) 00:00:02.177064 SSE - SSE support = 1 (1) 00:00:02.177064 SSE2 - SSE2 support = 1 (1) 00:00:02.177065 SS - Self Snoop = 0 (1) 00:00:02.177065 HTT - Hyper-Threading Technology = 1 (1) 00:00:02.177066 TM - Therm. Monitor = 0 (1) 00:00:02.177067 PBE - Pending Break Enabled = 0 (1) 00:00:02.177067 SSE3 - SSE3 support = 1 (1) 00:00:02.177068 PCLMUL - PCLMULQDQ support (for AES-GCM) = 0 (1) 00:00:02.177068 DTES64 - DS Area 64-bit Layout = 0 (1) 00:00:02.177069 MONITOR - MONITOR/MWAIT instructions = 0 (0) 00:00:02.177069 CPL-DS - CPL Qualified Debug Store = 0 (0) 00:00:02.177070 VMX - Virtual Machine Extensions = 0 (0) 00:00:02.177070 SMX - Safer Mode Extensions = 0 (0) 00:00:02.177071 EST - Enhanced SpeedStep Technology = 0 (1) 00:00:02.177072 TM2 - Terminal Monitor 2 = 0 (1) 00:00:02.177072 SSSE3 - Supplemental Streaming SIMD Extensions 3 = 1 (1) 00:00:02.177073 CNTX-ID - L1 Context ID = 0 (0) 00:00:02.177073 SDBG - Silicon Debug interface = 0 (0) 00:00:02.177074 FMA - Fused Multiply Add extensions = 0 (1) 00:00:02.177074 CX16 - CMPXCHG16B instruction = 0 (1) 00:00:02.177075 TPRUPDATE - xTPR Update Control = 0 (1) 00:00:02.177075 PDCM - Perf/Debug Capability MSR = 0 (1) 00:00:02.177076 PCID - Process Context Identifiers = 1 (1) 00:00:02.177077 DCA - Direct Cache Access = 0 (0) 00:00:02.177077 SSE4_1 - SSE4_1 support = 1 (1) 00:00:02.177078 SSE4_2 - SSE4_2 support = 1 (1) 00:00:02.177078 X2APIC - x2APIC support = 0 (1) 00:00:02.177079 MOVBE - MOVBE instruction = 0 (1) 00:00:02.177079 POPCNT - POPCNT instruction = 0 (1) 00:00:02.177080 TSCDEADL - Time Stamp Counter Deadline = 0 (0) 00:00:02.177081 AES - AES instructions = 0 (1) 00:00:02.177081 XSAVE - XSAVE instruction = 0 (1) 00:00:02.177082 OSXSAVE - OSXSAVE instruction = 0 (1) 00:00:02.177082 AVX - AVX support = 0 (1) 00:00:02.177083 F16C - 16-bit floating point conversion instructions = 0 (1) 00:00:02.177083 RDRAND - RDRAND instruction = 0 (1) 00:00:02.177084 HVP - Hypervisor Present (we're a guest) = 0 (1) 00:00:02.177085 Structured Extended Feature Flags Enumeration (leaf 7): 00:00:02.177086 Mnemonic - Description = guest (host) 00:00:02.177086 FSGSBASE - RDFSBASE/RDGSBASE/WRFSBASE/WRGSBASE instr. = 1 (1) 00:00:02.177086 TSCADJUST - Supports MSR_IA32_TSC_ADJUST = 0 (1) 00:00:02.177087 SGX - Supports Software Guard Extensions = 0 (1) 00:00:02.177088 BMI1 - Advanced Bit Manipulation extension 1 = 0 (1) 00:00:02.177088 HLE - Hardware Lock Elision = 0 (1) 00:00:02.177089 AVX2 - Advanced Vector Extensions 2 = 0 (1) 00:00:02.177089 FDP_EXCPTN_ONLY - FPU DP only updated on exceptions = 0 (0) 00:00:02.177090 SMEP - Supervisor Mode Execution Prevention = 0 (1) 00:00:02.177090 BMI2 - Advanced Bit Manipulation extension 2 = 0 (1) 00:00:02.177091 ERMS - Enhanced REP MOVSB/STOSB instructions = 0 (1) 00:00:02.177091 INVPCID - INVPCID instruction = 1 (1) 00:00:02.177092 RTM - Restricted Transactional Memory = 0 (1) 00:00:02.177092 PQM - Platform Quality of Service Monitoring = 0 (0) 00:00:02.177093 DEPFPU_CS_DS - Deprecates FPU CS, FPU DS values if set = 1 (1) 00:00:02.177093 MPE - Intel Memory Protection Extensions = 0 (1) 00:00:02.177094 PQE - Platform Quality of Service Enforcement = 0 (0) 00:00:02.177094 AVX512F - AVX512 Foundation instructions = 0 (0) 00:00:02.177095 RDSEED - RDSEED instruction = 0 (1) 00:00:02.177095 ADX - ADCX/ADOX instructions = 0 (1) 00:00:02.177096 SMAP - Supervisor Mode Access Prevention = 0 (1) 00:00:02.177096 CLFLUSHOPT - CLFLUSHOPT (Cache Line Flush) instruction = 0 (1) 00:00:02.177097 INTEL_PT - Intel Processor Trace = 0 (0) 00:00:02.177097 AVX512PF - AVX512 Prefetch instructions = 0 (0) 00:00:02.177098 AVX512ER - AVX512 Exponential & Reciprocal instructions = 0 (0) 00:00:02.177098 AVX512CD - AVX512 Conflict Detection instructions = 0 (0) 00:00:02.177099 SHA - Secure Hash Algorithm extensions = 0 (0) 00:00:02.177099 PREFETCHWT1 - PREFETCHWT1 instruction = 0 (0) 00:00:02.177100 UMIP - User mode insturction prevention = 0 (0) 00:00:02.177100 PKU - Protection Key for Usermode pages = 0 (0) 00:00:02.177102 OSPKE - CR4.PKU mirror = 0 (0) 00:00:02.177103 MAWAU - Value used by BNDLDX & BNDSTX = 0x0 (0x0) 00:00:02.177103 RDPID - Read processor ID support = 0 (0) 00:00:02.177104 SGX_LC - Supports SGX Launch Configuration = 0 (1) 00:00:02.177105 MD_CLEAR - Supports MDS related buffer clearing = 1 (1) 00:00:02.177105 IBRS_IBPB - IA32_SPEC_CTRL.IBRS and IA32_PRED_CMD.IBPB = 0 (1) 00:00:02.177106 STIBP - Supports IA32_SPEC_CTRL.STIBP = 0 (1) 00:00:02.177106 FLUSH_CMD - Supports IA32_FLUSH_CMD = 1 (1) 00:00:02.177107 ARCHCAP - Supports IA32_ARCH_CAP = 1 (1) 00:00:02.177107 31 - Reserved = 0 (1)
Features Mnemonic - Description = guest (host) PAE - Physical Address Extension = 0 (1) = 1 (1) SEP - SYSENTER and SYSEXIT Present = 0 (1) = 1 (1) PCLMUL - PCLMULQDQ support (for AES-GCM) = 0 (1) = 1 (1) MONITOR - MONITOR/MWAIT instructions = 0 (0) = 1 (1) CPL-DS - CPL Qualified Debug Store = 0 (0) = 0 (1) VMX - Virtual Machine Extensions = 0 (0) = 0 (1) SMX - Safer Mode Extensions = 0 (0) = 0 (1) SDBG - Silicon Debug interface = 0 (0) = 0 (1) CX16 - CMPXCHG16B instruction = 0 (1) = 1 (1) X2APIC - x2APIC support = 0 (1) = 1 (1) MOVBE - MOVBE instruction = 0 (1) = 1 (1) POPCNT - POPCNT instruction = 0 (1) = 1 (1) TSCDEADL - Time Stamp Counter Deadline = 0 (0) = 0 (1) AES - AES instructions = 0 (1) = 1 (1) XSAVE - XSAVE instruction = 0 (1) = 1 (1) AVX - AVX support = 0 (1) = 1 (1) RDRAND - RDRAND instruction = 0 (1) = 1 (1) HVP - Hypervisor Present (we're a guest) = 0 (1) = 1 (0)
Absolutely! This coexistence of Hyper-V and VirtualBox is a really new feature, and we're not sure (actually we don't have a clue) what makes it work or not. A comparative analysis is most welcome!FirstVoid wrote: I will produce the same log from the working machine and attach so you can compare if required?
Correct, you're right...FirstVoid wrote:Disabling Credential guard is just like turning hyper-v off, so I guess that's not the aim of this thread anymore?
For what? For something that the developers already know? It's going to be a waste of resources developers and users alike IMHO. The developers already know the situation, they state it (emphasis on the "might"):FirstVoid wrote:should we open a bug with the comparative logs and hardware types?
Not the definitive answer someone might look for...00:00:06.074744 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available 00:00:06.138105 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
What's a Filter driver?FirstVoid wrote:I can replicate the issues with an Filter driver
This works but the performance is not good, any thing I can tweak to make it run faster?loyukfai wrote:Good, perhaps VB team can consider making it a checkbox option on the GUI...loyukfai wrote:This customization:Code: Select all
<ExtraDataItem name="VBoxInternal/NEM/UseRing0Runloop" value="0"/>
Cheers.