- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
I have Core i7-6700K. Specification says this processors support Virtualization (VT-x, VT-d), but Intel(R) Processor Identification Utility says me, that my processor doesn't support it.
How it possible?
Configuration - Core i7-6700K and ASRock Z170 Pro4S motherboard.
Thank you.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Rebelion ,
Please make sure that the mainboard has enabled in bios the virtualization options.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, these options are enabled in BIOS, I've already checked it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All I can do is giving you this screenshot:
I have and Asrock z170 extreme 7 mainboard.
You have updated to the latest bios ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You have to enable in bios:
Intel Virtualization Technology
and
VT-d
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did this. Both options in bios are enabled (I can't do screenshot now, I'll do this at evening). I have latest 3.50 version of bios. Maybe this connected with bios developer mistake, maybe with another reason.
Thank you for your help - so, it's not a problem of intel, it's a ASRock motherboard bios problem, I suppose.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It maybe a software utility that is blocking the access to virtualization. I read some threads regarding this issue and it seems that even the antivirus can block the access. Check if you have any program that is messing with bios access, or do a clean windows install and check if its working after that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Lol. My problem was connected with enabled Microsoft Hyper-V. Now it's okay after MS Hyper-V disabling!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, I was sure that your system is ok .
Good that you found the problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, Rebelion:
Thank you for sharing your solution, l am glad to hear that you were able to track this down.
If you need further assistance let us know.
Regards,
Amy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you!
I have VT-x and VT-d both are supported in Identifiction Utility, but CPU-Z says me that only VT-x is avaiable. Also I have problems in boinc ATLAS and Virtual LHC projects - both of them use Virtual Box and say me that virtualization doesn't support.
7.6.22
<![CDATA[
(unknown error) - exit code -148 (0xffffff6c)
2016-09-24 18:23:36 (1512): vboxwrapper (7.7.26196): starting
2016-09-24 18:23:37 (1512): Feature: Checkpoint interval offset (500 seconds)
2016-09-24 18:23:37 (1512): Detected: VirtualBox COM Interface (Version: 5.1.6)
2016-09-24 18:23:37 (1512): Detected: Minimum checkpoint interval (900.000000 seconds)
2016-09-24 18:23:37 (1512): Successfully copied 'init_data.xml' to the shared directory.
2016-09-24 18:23:37 (1512): Create VM. (boinc_c9d7c17500abcdc3, slot# 33)
2016-09-24 18:23:37 (1512): Setting Memory Size for VM. (2241MB)
2016-09-24 18:23:37 (1512): Setting CPU Count for VM. (1)
2016-09-24 18:23:37 (1512): Setting Chipset Options for VM.
2016-09-24 18:23:37 (1512): Setting Boot Options for VM.
2016-09-24 18:23:37 (1512): Enabling VM Network Access.
2016-09-24 18:23:37 (1512): Setting Network Configuration for NAT.
2016-09-24 18:23:37 (1512): Disabling USB Support for VM.
2016-09-24 18:23:37 (1512): Disabling COM Port Support for VM.
2016-09-24 18:23:37 (1512): Disabling LPT Port Support for VM.
2016-09-24 18:23:37 (1512): Disabling Audio Support for VM.
2016-09-24 18:23:37 (1512): Disabling Clipboard Support for VM.
2016-09-24 18:23:37 (1512): Disabling Drag and Drop Support for VM.
2016-09-24 18:23:37 (1512): Hardware acceleration failed with previous execution. Disabling VirtualBox hardware acceleration support.
2016-09-24 18:23:37 (1512): ERROR: Invalid configuration. VM type requires acceleration but the current configuration cannot support it.
2016-09-24 18:23:37 (1512):
NOTE: VirtualBox has reported an improperly configured virtual machine. It was configured to require
hardware acceleration for virtual machines, but your processor does not support the required feature.
Please report this issue to the project so that it can be addresssed.
Error Code: ERR_CPU_VM_EXTENSIONS_DISABLED
18:23:37 (1512): called boinc_finish(-148)
This is an output of VM box. I don't know why, but I've enabled Virtualization in the bios anywhere it possible. Is this my bios/motherboard problem? (((
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What device you need to virtualize ?
You want all CPU to be virualized ? You need to go to the system settings in that virtual machine and at acceleration to enable VT-x and Nested paging.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Virtual box is not so good at virtualization especially if you are running windows. I mean at physically giving hardware access to devices.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, Virtual Box is used by boinc projects. ATLAS and Virtual LHC, for example. CPU-Z (and identification utility too, my mistake) also says that only VT-x is supported, not VT-d (see in attach). Does 6700K really supports VT-d or not?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes it does, I know someone on the forum who virtualized his video an nvidia card but in linux and running windows 10 in a virtual machine.
CPU: http://ark.intel.com/products/88195/Intel-Core-i7-6700K-Processor-8M-Cache-up-to-4_20-GHz Intel® Core™ i7-6700K Processor (8M Cache, up to 4.20 GHz) Specifications
Chipset: http://ark.intel.com/products/90591/Intel-GL82Z170-PCH (Intel® GL82Z170 PCH) Specifications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It seems that you have a configuration/software problem there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have a discrete video card ? If you don't that application will not run.
You need a discrete video card and activate igpu also and give access to the discrete card to virtualbox machine that will run. Also that virtual machine that it creates needs a video driver that is compatible to the video card you have. When you run the virtual machine it will take over your discrete video card.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I have. nVidia GeForce970. I'll check today igpu state too, maybe it's disabled in bios... Virtual box has standard configuration, I didn't change anything. There was no problem on my old Core i5+GeForce 555M...
Thank you for your help! Maybe igpu is a problem reason...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is more to that. The driver also may be the problem. GeForce 555M is a mobility card which has different driver then the gtx 970.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem was also connected with BOINC software and configuration. Thank you for advices (also boinc was needed igpu turned on)!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, everything is connected, one wrong thing and nothing works.
It's good that you managed to find and fix the problems.
I hope that everything will work well now.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page