virtualbox.org

I can tell you this: if I see another post without a log then I'll be locking the thread. We're now onto a second page for what is a trivial matter if the OP would have read the FAQ and not go off at irrelevant tangents.

Martin wrote:You could start with providing us the Virtualbox logfile as asked above. Then we could see what is detected by Vbox.

I did say that I have no VM , but I will download Ubuntu create a new VM and the send the log.

But according to the about INTEL diagnostic says that the TZD-X is not activated which - if I have understood the messages - forces VM to display 32 Bit systems only.

Please wait a bit for a small while, I am off to hospital on Monday. I'll apply there for internet access and try from there

Martin wrote:You could start with providing us the Virtualbox logfile as asked above. Then we could see what is detected by Vbox.

I loaded a pre-defined VM that I had sent to me for my OPENCV work.

I enclose a log files and if it helps I could send my CPU info . In the VMBOX logs clearly it shows that the TD-X is not active.

This is huge disappointment, since I assumed a modern Intel IT would accomodate this function.
So I assume I can only use 32 Bit OS's....or perhaps change my CPU - a rather expensive correction.

I have learned that in future I must check my HW and look at the the log before I request help. But I only learned what
TD-x meant here.

Many thanks.

Thanks for the log, that does indeed allow us to get the straight facts.

Btw, the feature is called VT-x and your i7-4790K CPU definitely supports it.

I see a few other serious problems.

1. You are using version v5.0.0 of VirualBox. By definition that is the buggiest release in the v5.x branch. You should be using the current release, which is 5.0.14 at the time of writing.
2. You have a Windows 10 host, which was not supported by v5.0.0, i.e. it probably won't work properly.
3. The log actually says that your Win10 host is unrecognized (new build), but that may just be a symptom of being on 5.0.0.
4. No doubt there are other problems with the VM itself, but since the VM will likely be deleted anyway I won't pursue this.

If you are using Windows 8 or later (and this was mentioned in the FAQ btw, and Windows 10 qualifies), then the probability exists that you have Hyper-v enabled on the host. That would prevent VirtualBox from accessing VT-x, hence no 64bit VMs, and no Win8 or Win10 VMs.

mpack wrote:Thanks for the log, that does indeed allow us to get the straight facts.

Btw, the feature is called VT-x and your i7-4790K CPU definitely supports it.

I see a few other serious problems.

1. You are using version v5.0.0 of VirualBox. By definition that is the buggiest release in the v5.x branch. You should be using the current release, which is 5.0.14 at the time of writing.
   
   According to the Help in VMBox I have 5.0.14
2. You have a Windows 10 host, which was not supported by v5.0.0, i.e. it probably won't work properly.
3. The log actually says that your Win10 host is unrecognized (new build), but that may just be a symptom of being on 5.0.0.
4. No doubt there are other problems with the VM itself, but since the VM will likely be deleted anyway I won't pursue this.

If you are using Windows 8 or later (and this was mentioned in the FAQ btw, and Windows 10 qualifies), then the probability exists that you have Hyper-v enabled on the host. That would prevent VirtualBox from accessing VT-x, hence no 64bit VMs, and no Win8 or Win10 VMs.

I am using Win 10.2 Pro
Yes, the Hyper-V is enabled so I'll look at that. But you finding the VM 5.0.0. does worry me a bit, since help shows 5.0.14
I an busy packing for my hospital stay but will try later to switch off Hyper-V and see what happens.

Thank you for your asistance.

Upgrading from 5.0.0 is not optional. You should do that first. I can't address what help file you are looking at, but the log is clear and dates from 3 days ago, so I assume is current.

mpack wrote:Upgrading from 5.0.0 is not optional. You should do that first. I can't address what help file you are looking at, but the log is clear and dates from 3 days ago, so I assume is current.

But according to help in the VM Icon I have 5.0.14 and not 5.0.0 - The VM for opencv was imported,though.

Looking at the VMBOX icons details , it start the programme from C:\Program Files\Oracle\VirtualBox\virtualbox.exe
Opening the properties and the detail on this exe file shows 15.0.14
I then used the programme everthing to see if there was another virtualbox.exe , but this proved to be negative.

I wanted to send the screen shops as proof, but the file are too large, and if I pruned then with paint they were barely readable.

So I am in position that the log shows one thing but the details show a different version.

Perhaps I ought to delete VM , re-download and install

The latest is that I removed the old VMBox and re-downloaded and installed.

I cannot install a Ubuntu 32bit I get an error VT-x is not available and
enclose the log. This time version 5.0.14 is display on the log header. I have appended the new log.

I had previously switch hyber-v off and rebooted but I still only get 32 Bit

The VM Userguide document 5.0.14 Page 222 had a puzzling entry:
As opposed to other virtualization software, for many usage scenarios, VirtualBox does not
require hardware virtualization features to be present. Through sophisticated techniques,
VirtualBox virtualizes many guest operating systems entirely in software. This means that
you can run virtual machines even on older processors which do not support hardware
virtualization.

Many thanks for your help!