Opened 6 years ago
Last modified 6 years ago
#18472 new defect
VirtualBox no longer working after latest set of Windows 10 security patches.
Reported by: | baseballbob | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 6.0.4 |
Keywords: | hanging and network errors | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description
I already submitted a Windows 10 feedback on this, as I'm not sure if it's a Windows 10 bug or a VirtualBox issue.
After last week's Windows 10 Pro security patches, I can no longer start a VirtualBox virtual machine. On version 5.26, it gives the error
verr_intnet_flt_if_not_found
when using a Windows 7 machine with a bridged wifi and Ethernet network. On VirtualBox version 6.04, it just hangs forever at the "Starting virtual machine" screen, and I have to kill the process to cancel it.
Even before this set of patches, it had run fine on 5.22 and 5.26, but
6.04 would always hang after getting almost all the way through the boot process, up to starting most of the commands in the startup folder. That would happen from Windows 10 to Windows 7 or 10 VMs, and from Linux Ubuntu 18 to Windows 10 VMs with a similar set of startups, but not from Mac OSX to Windows 10; that one ran fine.
Change History (3)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
I have the same problem and I think it might be because they recently enabled Retpoline by default.
00:00:05.503108 VM: fHMEnabled=true (configured) fRecompileUser=false fRecompileSupervisor=false 00:00:05.503110 VM: fRawRing1Enabled=false CSAM=true PATM=true 00:00:05.503494 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available 00:00:05.542048 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work... 00:00:05.542062 NEM: WHvCapabilityCodeExtendedVmExits = 0x0000000000000007 00:00:05.542070 NEM: fExtendedMsrExit: 1 00:00:05.542076 NEM: fExtendedCpuIdExit: 1 00:00:05.542082 NEM: fExtendedXcptExit: 1 00:00:05.542089 NEM: Warning! Unknown feature definitions: 0x1f 00:00:05.542100 NEM: Supported exception exit bitmap: 0x1 00:00:05.542112 NEM: WHvCapabilityCodeProcessorVendor = 1 - Intel 00:00:05.542125 NEM: WHvCapabilityCodeProcessorFeatures = 0x0081704041f7019f 00:00:05.542156 NEM: Sse3Support: 1 00:00:05.542165 NEM: LahfSahfSupport: 1 00:00:05.542172 NEM: Ssse3Support: 1 00:00:05.542178 NEM: Sse4_1Support: 1 00:00:05.542185 NEM: Sse4_2Support: 1 00:00:05.542192 NEM: Sse4aSupport: 0 00:00:05.542198 NEM: XopSupport: 0 00:00:05.542204 NEM: PopCntSupport: 1 00:00:05.542211 NEM: Cmpxchg16bSupport: 1 00:00:05.542217 NEM: Altmovcr8Support: 0 00:00:05.542223 NEM: LzcntSupport: 0 00:00:05.542229 NEM: MisAlignSseSupport: 0 00:00:05.542235 NEM: MmxExtSupport: 0 00:00:05.542241 NEM: Amd3DNowSupport: 0 00:00:05.542247 NEM: ExtendedAmd3DNowSupport: 0 00:00:05.542253 NEM: Page1GbSupport: 0 00:00:05.542259 NEM: AesSupport: 1 00:00:05.542265 NEM: PclmulqdqSupport: 1 00:00:05.542270 NEM: PcidSupport: 1 00:00:05.542277 NEM: Fma4Support: 0 00:00:05.542284 NEM: F16CSupport: 1 00:00:05.542290 NEM: RdRandSupport: 1 00:00:05.542296 NEM: RdWrFsGsSupport: 1 00:00:05.542302 NEM: SmepSupport: 1 00:00:05.542309 NEM: EnhancedFastStringSupport: 1 00:00:05.542316 NEM: Bmi1Support: 0 00:00:05.542322 NEM: Bmi2Support: 0 00:00:05.542328 NEM: MovbeSupport: 0 00:00:05.542334 NEM: Npiep1Support: 1 00:00:05.542341 NEM: DepX87FPUSaveSupport: 0 00:00:05.542346 NEM: RdSeedSupport: 0 00:00:05.542353 NEM: AdxSupport: 0 00:00:05.542415 NEM: IntelPrefetchSupport: 0 00:00:05.542427 NEM: SmapSupport: 0 00:00:05.542433 NEM: HleSupport: 0 00:00:05.542439 NEM: RtmSupport: 0 00:00:05.542444 NEM: RdtscpSupport: 1 00:00:05.542451 NEM: ClflushoptSupport: 0 00:00:05.542457 NEM: ClwbSupport: 0 00:00:05.542465 NEM: ShaSupport: 0 00:00:05.542473 NEM: X87PointersSavedSupport: 0 00:00:05.542482 NEM: Warning! Unknown CPU features: 0x81704041f7019f 00:00:05.542505 NEM: WHvCapabilityCodeProcessorClFlushSize = 2^8 00:00:05.543328 NEM: Warning! Unknown capability 0x1003 returning: 07 00 00 00 00 00 00 00 00:00:05.544912 NEM: VidGetHvPartitionId -> fun:0x2210a7 in:0x0 out:0x8 00:00:05.544935 NEM: VidStartVirtualProcessor -> fun:0x221174 in:0x4 out:0x0 00:00:05.544944 NEM: VidStopVirtualProcessor -> fun:0x221180 in:0x4 out:0x0 00:00:05.544967 NEM: VidMessageSlotHandleAndGetNext -> fun:0x2210df in:0x8 out:0x0 00:00:05.545370 NEM: Created partition 00000000011826a0. 00:00:05.545651 NEM: NEMR3Init: Active. 00:00:05.545816 MM: cbHyperHeap=0x140000 (1310720) 00:00:05.546964 CPUM: No hardware-virtualization capability detected 00:00:05.548281 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7 00:00:05.552217 CPUM: Matched host CPU INTEL 0x6/0x3a/0x9 Intel_Core7_IvyBridge with CPU DB entry 'Intel Core i5-3570' (INTEL 0x6/0x3a/0x9 Intel_Core7_IvyBridge) 00:00:05.552482 CPUM: MXCSR_MASK=0xffff (host: 0xffff) 00:00:05.552584 CPUM: Microcode revision 0x00000020 00:00:05.552663 CPUM: MSR/CPUID reconciliation insert: 0x0000010b IA32_FLUSH_CMD 00:00:05.552742 CPUM: SetGuestCpuIdFeature: Enabled PAE 00:00:05.552776 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT 00:00:05.552785 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET 00:00:05.552792 CPUM: SetGuestCpuIdFeature: Enabled PAE 00:00:05.552798 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE 00:00:05.552804 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF 00:00:05.552811 CPUM: SetGuestCpuIdFeature: Enabled NX 00:00:05.554463 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1463) int __cdecl nemR3NativeInitAfterCPUM(struct VM *); rc=VERR_NEM_VM_CREATE_FAILED 00:00:05.554818 VMSetError: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) 00:00:05.554898 NEM: Destroying partition 00000000011826a0 with its 0 VCpus... 00:00:05.710343 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805 00:00:05.711031 Console: Machine state changed to 'PoweredOff' 00:00:05.730884 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005)) 00:00:06.230907 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1400x1050 00:00:06.230961 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0 00:00:06.231185 GUI: Aborting startup due to power up progress issue detected...
comment:3 by , 6 years ago
@Stanzilla,
You posted in the "Windows Pre-releases" thread in the forums: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536). A thread which is pointing to a very specific ticket, ticket #18536. Can you explain to me why you posted on a different ticket? One that has absolutely nothing to do with your problem?
Please choose carefully where you post your information. I already replied to you in the forums, let's continue over there...
It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
Plus a discussion and analysis on the bug tracker is going to help you, me, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...
A technique that we've used in the forums that has solved a lot of headaches is:
PS. Indenting your sentences by a space or two, has a different meaning in WikiFormatting. Just look at how your message looks in it final rendering. You should always use the "Preview" before actually posting your message... ;)