virtualbox.org

Is there a tutorial for installing VirtualBox on Win10 AMD-64 with GuestOS Ubuntu-64 that actually works?
[I had to remove the tags, and I had to remove the dots in the domains, etc.]

BASICS:
I'm new, frustrated, and need some pointers to instructions that actually work.
All I want to do is install Virtual Box on Windows 10 Pro and then use Ubuntu (32bit or 64 bit, I don't care).

What I'm doing has to be the most common installation on the planet.
And yet, it fails.

DETAILS:
Doing the "logical" (aka intuitive" thing nets me the extremely common error "This kernel requires an X86-64 CPU, but only detected an i686 CPU".

Googling for that error brings me here (e.g., { URI = h-t-t-p-s-:-/ / communities (dot)vmware (dot)com/thread/146242}here { / URI } , or { URI = h-t-t-p-s-:-/ / community (dot)hortonworks (dot)com/questions/49237/this-kernel-requires-an-x86-64-cpu-but-only-detect(dot)html}here { / URI } , or { URI = h-t-t-p:/ / jaredheinrichs (dot)com/ubuntu-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-windows-virtual-pc(dot)html}here { / URI } , or { URI = h-t-t-p-s-:-/ / www (dot)turnkeylinux (dot)org/forum/support/20130807/please-use-kernel-appropriate-your-cpu}here { / URI } , etc.) where NOTHING makes sense that is suggested.

I'm not a genius, so I'm sure I missed something super critical, so let me tell you EXACTLY what I did so far, where all I ask is information as to why something so seemingly simple isn't documented properly even when everyone on the planet is getting the same error.

1. My desktop is Windows 10 Pro, AMD Phenom II X4 810 2.60GHz, 16GB RAM, 64-bit OS, x64-based CPU
{ image } h-t-t-p-s-:-/ / s12(dot) postimage (dot)org/cuth20c71/windows10(dot)gif {/image }

2. I downloaded the latest VirtualBox 5.1.22 r115126 (Qt5.6.2) from:
{ URI = h-t-t-p:/ / download(dot)virtualbox (dot)org/virtualbox/5.1.22/VirtualBox-5.1.22-115126-Win(dot)exe}here { / URI } .
{ image } h-t-t-p-s-:-/ / s12 (dot)postimage (dot)org/l8a1uycp9/virtual_box(dot)gif {/image }

3. For the "Guest OS", I downloaded the latest { URI = h-t-t-p-s-:-/ / www(dot)ubuntu(dot)com/download/desktop/}Ubuntu 16.04.2 LTS (1.4GB) ISO { / URI } which doesn't seem to even exist in a 32-bit version (am I wrong about that?).
{ image } h-t-t-p-s-:-/ / s2 (dot)postimage (dot)org/407hlg81l/downloads(dot)gif{/image }

4. I run the VirtualBox installer taking all the defaults and then press the "New" button & type the Name=ubuntu which populates as below:
{ image } h-t-t-p-s-:-/ / s22 (dot)postimage (dot)org/4zq3n4n4x/ubuntu32(dot)gif{/image }

Notice there are no 64-bit versions in the pull-down menu:
{ image } h-t-t-p-s-:-/ / s13 (dot)postimage (dot)org/ry3dla2wn/pulldown(dot)gif{/image }

OK. I'm already stuck between a rock and a hard place:
A. I can't download a 32-bit Ubuntu ISO (it seems)
B. VirtualBox won't recognize the 64-bit Ubuntu ISO that I can download (it seems).

When I google, I find the aforementioned references which discuss setting the BIOS for (INTEL only?) "virtualization" (whatever that is) but I have an AMD CPU.

All I'm asking is direction for solving the dilemma.
I don't really care if I install a 32-bit guest OS or a 64-bit guest OS.

I just want a tutorial for installing VirtualBox on Win10 AMD-64 with Ubuntu 64 that actually works.
Is that too much to ask?

PS: I was forced to manually mangle the URLs because (just to increase the frustration) this site won't let them post URLs.

The message means that you are trying to install a 64bit guest using a 32bit VM template.

From that I can guess that you probably didn't see any 64bit templates.

From that I can further guess that you haven't read the faq: FAQ: I have a 64bit host, but can't install 64bit guests.

And, since your host is Win10, I can make the final guess you have Hyper-v enabled. See the faq.


Btw. I'm curious about how you expect the forum to know you're a seasoned poster? And assuming it could, I guess the assumption is that seasoned posters don't post spam? I'm not sure I accept that logic.

mpack wrote:The message means that you are trying to install a 64bit guest using a 32bit VM template.

Thanks for trying to help, even though all my URIs failed and had to be munged, which makes it difficult for you.

I did read the FAQ (but a different one as shown in my original post!) which did NOT discuss AMD but only INTEL setting of the virtuaualization in the BIOS.

BTW, nobody inherently knows what "virtualization" even means, so, whenever someone says to set it in documentation, they should explain WHAT it is.
It's OK if you don't say what it is, but for documentation to NOT say what it is, is criminal (from a documentation standpoint).

mpack wrote:From that I can guess that you probably didn't see any 64bit templates.

The word you used was "template" which is meaningless to me.
To me, I have three things:
1. I have a 64-bit AMD hardware host which is running a 64-bit Windows Operating System host.
2. I want to put on a Ubuntu guest OS, but I can only find 64-bit ISOs at the Ubuntu Downloads web site.
3. I installed 64-bit VMWare.

What's a "template' in that regard?
And then what's a "64-bit template"?

mpack wrote:From that I can further guess that you haven't read the faq forums (dot) virtualbox(dot)org/viewtopic.php?f=1&t=62339 FAQ: I have a 64bit host, but can't install 64bit guests.

I read a different FAQ than that one, which a similar thread pointed me to, which only talked about Intel virtualization (whatever that is).
It also suggested VMware software which is crazy to have to download since VirtualBox should have the same type of software somewhere.

As soon as I get past all the URI issues with this post, I will read that FAQ but I just wanted to reply to you asap that I thank you for pointing it out and I will respond about it when I read it in a moment.

mpack wrote:And, since your host is Win10, I can make the final guess you have Hyper-v enabled. See the faq.

If that FAQ has how to set the "virtualization" that is called "hyper-v" for AMD, then I will run those steps.
I was in a software company for decades. This shouldn't happen. The VirtualBox software should just CHECK for this.
There is no excuse for such sloppy GUI coding.
But then again, this is free software, so, a sloppy GUI is, I guess, to be expected, even in the most-used VirtualBox software for home use.
But that's another story.

mpack wrote:Btw. I'm curious about how you expect the system is supposed to know you're a seasoned poster? And assuming it could, I guess the assumption is that seasoned posters don't post spam? I'm not sure I accept that logic.

Your point is completely valid ... if....
I'm on plenty of web sites where you can post URIs in the first post.
That's what I had meant.

Most "moderate" the first post, where it simply "ghosts" until a moderator has a chance to approve it.
Anyway, I apologize for the frustration.

What is shocking, to me, is that this is the simplest setup anyone could want to have, and it has huge problems.
The SOFTWARE GUI should be walking me through this, not you.
Also the TUTORIALS should be covering this, not the FAQ.

Anyway, I will go read the FAQ you noted as the first FAQ I read only discussed Intel "virtualization" in the BIOS where I knew I have AMD.

OK. So I read the FAQ you pointed me to (which, I add, is DIFFERENT than the ones I listed in the original post).
That FAQ is MISSING a key description of what virtualization is.
All it needs is a single sentence to describe what it is.

Nonetheless, essentially that FAQ says (for my situation):
Q: "This kernel requires an X86-64 CPU, but only detected an i686 CPU"
A: You usually need to enable VT-x/AMD-v in the host PC BIOS
PS: I don't have any other 'host apps using AMD-v, at least not that I know of since I have absolutely no idea of what it is and the FAQ doesn't say what it is.

Q: What is a template?
A: The FAQ calls Ubuntu the "guest os template", so I am guessing that a "template" is a guest operating system.
IS that a correct guess of what a "template" is?

Then the FAQ, at the very bottom, introduces a brand new term, also undefined, when it says:
" To check the status of Hyper-v in Windows 10..."
What is "hyper-v"?
Is that the same as "VT-x/AMD-v"?

Who knows.
The FAQ just introduces terms as if I started talking about George and then suddenly switched to talking about Susan, without ever saying who George or Susan are. Are they the same people? Different people? Who knows? The FAQ gives no indication either way.

HINT: I used to run a documentation team, but that's another story.

The FAQ doesn't say a thing about what AMD-v is nor what Hyper-V is.
It just tells you what the name of that switch is in the BIOS (it's AMD-v).
And it just tells you to check for Hyper-V in Windows 10.

That's ENOUGH (I understand) to turn it (or both?) on, but the switch may as well be named "George" and the other named "Susan" for all the FAQ helps with.

Anyway ... checking in Windows in a sec for this thing called "Susan", or Hyper-V...
h t t p s : / / s1.postimg (dot)org/ai9fto7an/hyper-v.gif

As shown in the screenshot above, all the Hyper-V-related settings are unchecked.
[ ] Hyper-V
...[ ] Hyper-V Management Tools
......[ ]Hyper-V GUI Management Tools
......[ ]Hyper-V Module for Windows PowerShell
...[ ]Hyper-V Platform
......[ ]Hyper-V Hypervisor
......[ ]Hyper-V Services

My guess is that this thing called "hyper-v" is the same as this other thing called "AMD-v", so I will google for what they are.

OK. I guessed wrong. I think.
The wikipedia for "hyper-v" says it's a Microsoft thing.
h t t p s : / / en(dot)wikipedia(dot)org/wiki/Hyper-V

Microsoft Hyper-V, codenamed Viridian[1] and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems running Windows.[2]

Where a "hypervisor" is...

A hypervisor or virtual machine monitor (VMM) is computer software, firmware or hardware that creates and runs virtual machines.

So now it's time to figure out what AMD-v is, since that's not a Microsoft thing.
h t t p s : / / en(dot)wikipedia(dot)org/wiki/X86_virtualization#AMD_virtualization_.28AMD-V.29

In computing, x86 virtualization refers to hardware virtualization for the x86 architecture. It allows multiple operating systems to simultaneously share x86 processor resources in a safe and efficient manner.

Since my desktop has an AMD Phenom II X4 810 CPU, this next line in the wiki is apropos:

AMD Opteron CPUs beginning with the Family 0x10 Barcelona line, and Phenom II CPUs, support a second generation hardware virtualization technology called Rapid Virtualization Indexing (formerly known as Nested Page Tables during its development), later adopted by Intel as Extended Page Tables (EPT).

So at least I know my CPU is "AMD-v" capable.
Now to the BIOS to see if it's turned on or off.

Googling, apparently I can boot to the BIOS as explained here
h t t p s : / / support(dot)hp(dot)com/us-en/document/c00364979
1. Turn on or restart the computer.
2. While the display is blank, press the f10 key to enter the BIOS settings menu.
NOTE: The BIOS settings menu is accessible by pressing the f2 or the f6 key on some computers.

I'm gonna reboot and check out the BIOS now.
(But really, if there just was a 32-bit option, I'd be perfectly happy with a 32-bit guest Ubuntu. Sigh.)

OK. I'm back. For the HP machine I have an F10 is the boot-to-BIOS command.
At the BIOS, I arrowed over to the POWER tab and then arrowed down to the "Virtualization Technology" line item, which was set to [Disabled].

The GREAT NEWS is that the HP BIOS had the first decent description of what this is, by saying:

Virtualization Technology enables a CPU feature to run multiple simultaneous virtual machines allowing specialized software to run in full isolation of each other. HP recommends disabling this feature unless specialized applications are being used.

I set Virtualization Technology to [Enabled] and rebooted and doublechecked at the BIOS, and rebooted again.
Then I started the Oracle VirtualBox which loaded the Ubuntu (somehow) without me telling it to, but it hung forever saying:

ubuntu: Starting VM
Creating process for virtual machine "ubuntu" (GUI/Qt)...(1/2) 0%

Here is a screenshot of that error:
h t t p s : / / s8.postimg(dot)org/ucddn46sl/ubuntu_virt.gif

Something else is wrong, but there were so many wrong turns already, I think I'll uninstall virtual box and start over clean.

IMHO, the GUI during INSTALLATION should have warned us against this, since it can tell that the hardware doesn't have Virtualization Enabled. It should STOP the installation and ask the user to proceed only after turning on the necessary BIOS settings. I realize the user might not NEED this thing called "virtualization" turned on, but the INSTALLER should ask what they plan on doing, and if they plan on installing a 64-bit guest OS, then they apparently NEED to turn this thing called "virtualization" on in the BIOS, so, the INSTALLER should flag this at the time of installation.

Anyway, I uninstalled VirtualBox and rebooted, and cleaned the registry of the keys the uninstaller left lying around, and now will do the process all over again.

OK. So I re-installed the "Oracle VM VirtualBox Manager" and it still insists on only showing 32-bit Ubuntu.
I must have done something wrong.
Here is a screenshot:
h t t p s : / / s10.postimg(dot)org/8typgoy55/drat_ubuntu_32bit.gif

It says Ubuntu is "powered off", whatever that means.
h t t p s : / / s24.postimg(dot)org/yoe4spz0l/powered_off.gif

Luckily, there's a big green "Start" button, so I'm hitting that, and taking the defaults, except that I have an ISO on my hard drive so I won't choose the D: (optical) drive.

Darn. Still getting that same error.

"This kernel requires an X86-64 CPU, but only detected an i686 CPU.
Unable to boot - please use a kernel appropriate for your CPU."

The one key thing you haven't mentioned is starting with the VirtualBox Manual: https://www.virtualbox.org/manual/UserManual.html

The first few sections could really help to clarify your understanding as they begin with the basics, rather than jumping straight in at the deep end. Especially see Section "1.7 Creating your first virtual Machine" (and for 'Template' consider 'Type' & 'Version', as shown in the graphic). If you don't see any 64-bit versions then you are back to the advice already given above.

You sound like a fairly new user to VirtualBox. Since you are expected to know some basic terms before we engage in a meaningful discussion, I would suggest to start by reading three small chapters from the User Manual:

• 1.2. Some terminology,
• 1.7. Creating your first virtual machine and
• 1.8. Running your virtual machine.

woodrock wrote:nobody inherently knows what "virtualization" even means ... they should explain WHAT it is.

woodrock wrote:What is "hyper-v"?

Tried Wikipedia? You can't be attending a University class on geometry and not know Pythagoras' theorem, or expecting that you will be taught that in the University. The "documentation" would be huge.

woodrock wrote:I used to run a documentation team

woodrock wrote:I was in a software company for decades. This shouldn't happen.

woodrock wrote:The SOFTWARE GUI should be walking me through this, not you.
Also the TUTORIALS should be covering this, not the FAQ.

Since this is an open source project, donations in code and documentation are always acceptable suggestions. Please read the following: How to contribute. An excerpt:

How to contribute wrote:There are many ways how you can contribute to VirtualBox. Even if you're not a programmer, you can help us with the documentation, or work on the design, or you can help us by regularly trying out test builds- which are expected to be almost as reliable as normal releases - and telling us about any problems you encounter which were not present before.

woodrock wrote:for documentation to NOT say what it is, is criminal (from a documentation standpoint).

You may need to start even earlier in the User Manual:

• 1 First steps, and
• 1.1 Why is virtualization useful?.

And yes, documentation might not cover everything, or might not explain everything according to one's level of understanding, otherwise there wouldn't be FAQs and tutorials that try to explain it to the layman. The other thing that happens (we've seen it in a couple of occasions), is that people don't actually read the documentation, but they prefer FAQs, online tutorials, guides, etc. Unbelievable, I know, but it happens...

woodrock wrote:I'm new, frustrated, and need some pointers to instructions that actually work.

I'd say... But if you want to vent some steam, this is not the place. If you have clear, specific questions, then you're in the right place, we're here volunteering to help you and others.

If you come out punching, screaming and yelling, you're not going to score too many points. If you come out suggesting, helping, patching, you are going to get many points with other fellow users and the developers...

erdeslawe wrote:The one key thing you haven't mentioned is starting with the VirtualBox Manual: h t t p s www(dot)virtualbox(dot)org/manual/UserManual.html

Thanks for the suggestion to RTFM.
I guess I tremendously underestimated the amount of work that is involved to install VirtualBox with Ubuntu on Windows 10. I didn't think something so common would be so difficult, but, I'll hit up that manual next as it's STILL complaining:

"This kernel requires an X86-64 CPU, but only detected an i686 CPU.
Unable to boot - please use a kernel appropriate for your CPU."

Even though I uninstalled the VirtualBox software, rebooted, cleaned the registry, rebooted, and re-installed VirtualBox.
Of course I've posted detailed screenshots, but they won't show up for you unless you reassemble the URIs.

I'm going to have to see why VirtualBox only allows 32-bit Ubuntu even though the Ubuntu download is the one shown in my detailed screenshot, labeled:
- ubuntu-16.04.2-desktop-amd64.iso 1,517,760 KB

erdeslawe wrote: The first few sections could really help to clarify your understanding as they begin with the basics, rather than jumping straight in at the deep end. Especially see Section "1.7 Creating your first virtual Machine" (and for 'Template' consider 'Type' & 'Version', as shown in the graphic). If you don't see any 64-bit versions then you are back to the advice already given above.

Thanks for that suggestion.
I definitely turned on the hardware virtualization in the BIOS, and I definitely don't have the Windows settings for whatever it is that is "Hyper-V" checked, and I am pretty sure that the ISO I downloaded for Ubuntu is 64 bit (it never gave me a choice for anything else).

So I'm currently going to have to start all over again to figure out why I get that error.

socratis wrote:You sound like a fairly new user to VirtualBox.

I've always wanted to install a virtual machine, so I googled for tutorials, which made it seem so easy.
So I took the plunge. You are correct that this is my first virtual machine.

socratis wrote: Since you are expected to know some basic terms before we engage in a meaningful discussion, I would suggest to start by reading three small chapters from the User Manual

I'll read them. Thanks for those suggestions.
At the moment, I'm perplexed about why VirtualBox doesn't give me the 64-bit option, so, that's where I'm focused to start with.
(Can only do one thing at a time.)

socratis wrote:Tried Wikipedia?

Yes. I quoted it above but had to obfuscate the URIs since it won't let me post any URIs.
The BEST description of what Virtualization is was NOT in Wikipedia, by the way.
It was what the HP BIOS said:

Virtualization Technology enables a CPU feature to run multiple simultaneous virtual machines allowing specialized software to run in full isolation of each other. HP recommends disabling this feature unless specialized applications are being used.

socratis wrote:Since this is an open source project, donations in code and documentation are always acceptable suggestions.

That's a perfectly acceptable answer, which I appreciate.
You don't know me, but I write tutorials all the time.
Certainly you will see step-by-step tutorials from me in the near future.
I write them with a certain style which is unmistakable, in that I don't skip a step.
Expect a tutorial for "how to install VirtualBox on Win10 with Ubuntu and have it actually work".

socratis wrote: And yes, documentation might not cover everything, or might not explain everything according to one's level of understanding, otherwise there wouldn't be FAQs and tutorials that try to explain it to the layman. The other thing that happens (we've seen it in a couple of occasions), is that people don't actually read the documentation, but they prefer FAQs, online tutorials, guides, etc. Unbelievable, I know, but it happens...

For something so trivial, IMHO, nobody should have to read the documentation if the software GUI isn't too sloppy.
Remember, I'm using the most common operating systems on the planet.
My ultimate goal is other operating systems, but, for now, I purposefully chose the two most commonly installed operating systems just because I figured it would be trivial. I was wrong.

Anyway, you can expect a tutorial that actually works to come out of this.
But I'm not at that stage yet.

Right now, I have to figure out why VirtualBox insists on 32-bit-only (not that I care about 32 or 64-bit but that the only Ubuntu ISO I could find was 64-bit). So those are my two areas of concern right now, where the Ubuntu problem isn't something that you can help me with here.

socratis wrote:But if you want to vent some steam, this is not the place. If you have clear, specific questions, then you're in the right place, we're here volunteering to help you and others.

Right now, my main two fuzzy areas are:
1. Why does VirtualBox insist on only showing 32-bit versions of Ubuntu, and,
2. Why does the Ubuntu download only allow 64-bit (which isn't an issue to take up here).

socratis wrote:If you come out punching, screaming and yelling, you're not going to score too many points. If you come out suggesting, helping, patching, you are going to get many points with other fellow users and the developers...

You are correct. It's too bad I can't post URIs because the original post took about an hour to write with all the documentation in it and it's detailed with all the steps. But without the URIs, it's almost unreadable, I know. So maybe I should just wait a day until I can post a proper post with proper documentation in it.

Meanwhile, I'll read the stuff, but I insist on repeating that if documentation is mandatory to be read, then the software isn't well written, since I specifically chose the most common two operating systems just so that it would just work.

I understand that not everyone has the same opinion as I do about software working out of the box, so, take that with a grain of salt.
Right now, I will look at a few more tutorials, since, really, all I ever wanted was a tutorial that actually worked.

woodrock wrote:I'm going to have to see why VirtualBox only allows 32-bit Ubuntu even though the Ubuntu download is the one shown in my detailed screenshot, labeled: - ubuntu-16.04.2-desktop-amd64.iso 1,517,760 KB

You must have missed mpack's suggested reading:

mpack wrote:The message means that you are trying to install a 64bit guest using a 32bit VM template.

From that I can guess that you probably didn't see any 64bit templates.

From that I can further guess that you haven't read the faq: FAQ: I have a 64bit host, but can't install 64bit guests.

And no, we don't really need screenshots, you're doing fine without them...

socratis wrote:You must have missed mpack's suggested reading

I actually appreciate the humor, as it's obvious that I read that (since I ran all the steps and documented that I did that), but, of course, it didn't work, so, your point is REALLY that I MISSED something in that "suggested reading" .... which is a fair enough assessment.

So, I'm re-reading for the third or fourth time that suggested reading to see WHY VirtualBox still doesn't provide the choice of 64-bit Ubuntu.

Clearly, there are only two things that can be happening:
1. Either I missed something (or skipped something),
2. Or whomever it was who wrote the FAQ missed something (or skipped something).

Since I'm the noob, it's probably me who missed something, so I'll go down again, line by line, to see what I missed.
(Give me a few minutes to document...)

1. I have an AMD 64-bit CPU (AMD Phenom II X4 810 2.60GHz, 16GB RAM).
2. THerefore, I assume I need to have this thing called "AMD-v" virtualization enabled in the BIOS.
3. I documented that I definitely have this thing called "Virtualization Technology" enabled in the BIOS.
4. My assumption, from the suggested reading, is that this thing called "AMD-v" is the same as this thing called "Virtualization Technology".
5. Hence, I assume I have hardware support for virtualization, and that it is enabled.

Hence, this part, I assume, of the suggested reading is already taken care of:

To enable 64bit guests, run through the following checklist :-
Note your exact CPU model or part number, then go online and check its capabilities. The CPU must have 64bit capability and support either Intel or AMD virtualization technologies: VT-x or AMD-v.

Moving on (give me a moment to document)...
OK. I already covered the next step in the suggested reading...

You usually need to enable VT-x/AMD-v in the host PC BIOS. You need to check with your PC manual or support forum to find out how to boot into the BIOS screen. This is probably not something we here at the VirtualBox forums can help you with. Once you get there you need to look for something buried in a menu, perhaps in the security category. The option may be called something like "Enable Virtualization Technology". If you see "Virtual Directed I/O" (VT-d/AMD-Vi) then that is a different thing. Remember to reboot your host PC after making BIOS changes - in this case a full restart from power off is required, just resuming from a hibernated state may not do the job.

OK. I already did all that, as acknowledged a few posts up.
So we can assume that the "AMD-v" is the same thing as "Virtualization Technology", which is ENABLED in the BIOS.

I do note that you say not to reboot from "hibernation".
I rebooted but I didn't do a cold reboot (pull the plug and all that).
So, just in case, I'll do a cold reboot. And come back to go line by line through the next part of the suggested reading.

It's not humor I'm afraid, or there would be a smiley at the end of my comment. The FAQ has never failed so far. So, read it thoroughly. There is something that is "stealing" your AMD-V (or VT-x if you had an Intel, most people do) and prevents VirtualBox giving you those options. There's no way around it.

socratis wrote:The FAQ has never failed so far.

This is good to know.

socratis wrote:There is something that is "stealing" your AMD-V [that] prevents VirtualBox giving you those options. There's no way around it.

That's helpful advice as the problem for noobs is always where to focus the energy on.

I am rebooting from a "full" (cold) reboot in a moment, and will return after testing if that full reboot (power plug pulled first), has any effect.
Back in a few ...

OK. Did the full reboot. Shut it down. Pulled the power cord. Waited till all the LEDs inside the box (I have the side off) went out. Rebooted.
Triple checked the BIOS setting that "Virtualization Technology" is "ENABLED". Rebooted.
Started VirtualBox. Still it only sees 32-bit.

So back to #3 of the suggested reading ...

If (1) and (2) are already taken care of, then make sure that no other host apps are already using VT-x/AMD-v.

Hmmm... this isn't so easily checked since you're intimating it could be anything at this point.
(e.g., debuggers, other VMs, av programs, etc.).

So what we need here for a tutorial that actually works is some kind of COMMAND or PLACE TO LOOK to see what is "using the AMD-v", whatever that means. At the moment, the suggested reading doesn't even hint at HOW to figure that out, so I'll move on to the next step, keeping in mind that I skipped this step for lack of knowing what to do to accomplish this step.

When creating a VM, make sure you choose the 64-bit version of the guest OS template in <VM Settings> | General | Basic | Version, e.g. choose "Ubuntu (64 bit)" and not "Ubuntu" or "Ubuntu (32bit)".

The suggested reading doesn't say which software, so I assume "VirtualBox" software, so I'll go there now and check...
Heh heh ... as is extremely typical of very many documents, what they suggested doesn't actually exist.
So I have to guess. That's not a complaint. Just an observation that the documentation appears to be wrong above.

When I doubleclick on the desktop shortcut titled "Oracle VM VirtualBox", the "Settings" are grayed out.
(I'd post a screenshot, but it's too difficult given the site won't let me.)

So, I will try the "new" button again, taking all the defaults after typing a name of "ubuntu".
Now the "settings" gear is no longer grayed out, and is orange.
Clicking on that now-visible orange settings gear...
VirtualBox: [Settings] > General > Basic > Version (I only see 32-bit versions)

So, there's no way to actually do what the documentation says.
And the documentation doesn't say what to do when all you see is 32-bit versions.

Moving on to the rest of the suggested documentation ...we get to the two notes, the first of which I already covered in a prior post but we cover again here... to doublecheck ...

Notes:
1. To check the status of Hyper-v in Windows 10, <right click start> | Run | OptionalFeatures.exe, and look for the "Hyper-V" option. The box should be empty, not checked or shaded. Make sure to fully power down and reboot the host after changing this setting.

Double checking ... there are 7 "hyper-v" related items (as noted in a prior post), all of which are unchecked.

So now we're left only with the cryptic non-actionable suggestion in the second of the two notes, which I skipped prior because there's nothing actionable, and I repeat here for clarity:

2. On some Windows hosts with an EFI BIOS, DeviceGuard or CredentialGuard may be active by default, and interferes with OS level virtualization apps in the same way that Hyper-v does. These features need to be disabled.

Ok. Um. What does that mean? EFI Bios? What's that? DeviceGuard? CredentialGuard?
Time to google but maybe it would be nice if we can figure out how to extend this help so that the NEXT user has an idea how to check for these things?

Googing ...

Well, here's the hit for EFI bios in Wikipedia...
h t t p s : / / en(dot)wikipedia(dot)org/wiki/Unified_Extensible_Firmware_Interface

The Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an operating system and platform firmware.

The wikipedia article isn't actionable, and it only mentions AMD once anyway, so, my purely speculative guess is that I don't have this problem (but who knows because the help doesn't help figure it out). I guess you're just supposed to KNOW that you have this EFI Bios thing. By osmosis probably. Anyway, when troubleshooting, you have to skip cryptic stuff, where this EFI Bios is cryptic, so I'll move on to the second thing.

Device Guard ...
Googling ... I find this Microsoft Document titled "Introduction to DeviceGuard"... at
h t t p s : / / docs.microsoft()dot)com/en-us/windows/device-security/device-guard/introduction-to-device-guard-virtualization-based-security-and-code-integrity-policies
OMG. That's complicated. The only thing I want to know is HOW to tell if I even HAVE deviceguard.
Does the suggested document help with that? Nope.

While I can become an expert in DeviceGuard, I'll move on to the last of the suggested items, which is ... "CredentialGuard".
Does the document say HOW to tell if you even have CredentialGuard? Nope.
So, I'm back to googling ... (but the first person who googles should be able to add what they learn to the document so that the tribal knowledge grows over time with each attempt to debug)...

CredentialGuard
Here is a "deep dive into credentialguard" from Microsoft, which I guess should be on this help document as the best hit:
h t t p s : / / mva(dot) microsoft(dot)com/en-us/training-courses/deep-dive-into-credential-guard-16651#!

Actually, that wasn't all that good.
What we need for the next noob is simply a software tool that can TELL THE NOOB if they even HAVE this stuff on their machine!
Maybe something like this?
h t t p s : / / www (dot)microsoft (dot) com/en-us/download/details.aspx?id=53337
Device Guard and Credential Guard hardware readiness tool

Use this tool to see if your hardware is ready for Device Guard and Credential Guard. You can also use this to enable Device Guard or Credential Guard.

and

Use this tool to see if your hardware is ready for Device Guard and Credential Guard.
You can also use this to enable Device Guard or Credential Guard.
This tool is a Windows PowerShell script that needs to run with elevated permissions.
It will work with Windows 10 Enterprise edition (beginning with version 1607) and Windows Server 2016.
You can use this tool in the following ways:
Check if the device can run Device Guard or Credential Guard
Check if the device is compatible with the Hardware Lab Kit tests that are ran by partners <=== you gotta love their grammar!
Enable and disable Device Guard or Credential Guard
Check the status of Device Guard or Credential Guard on the device

Darn. There's no executable. It uses something called the PowerShell, but, worse, I'm on Win10 Pro, and it says it works with Enterprise.
So I'm gonna cut my losses.

OK. I made it to the bottom (again) of the suggested help.
I did all the actionable things.
And I skipped the two things that weren't actionable.

So, we're left assuming those two things are the problem.
1. Either I have a host app that is using AMD-v, or,
2. EFI BIOS, DeviceGuard or CredentialGuard is interfering with OS-level virtualization.

Go back and read my first post again. Thoroughly. Blinkers off.

mpack wrote:Go back and read my first post again. Thoroughly. Blinkers off.

Thanks for the repeated advice.

I'm pretty sure I did what you asked, but let's take it line by line since in the end, I'll write a tutorial that covers each step in sufficient detail for it to be actionable by a noob.

The first line talks about a "template", which, when I had read it, was the first time I'm hearing of this type of "object".
You'll notice that I asked "what is a template", so, that's really what you're trying to tell me, which is that I have this thing called a "template" and it's 32-bits instead of 64-bits.

But what is this thing called a "template"?

I only have four related "things", which are:
1. The 64-bit CPU which is an AMD Phenom II X4 810 2.60GHz, 16GB RAM (where AMD-v is enabled in the BIOS)
2. The 64-bit Windows 10 Pro host operating system (where Hyper-V is not checked in Windows OptionalFeatures.exe)
3. A downloaded Ubuntu 64-bit ISO file as the guest operating system
4. An installed Oracle VM VirtualBox Manager with the VirtualBox Graphical User Interface Version 5.1.22 r115126 (Qt5.6.2)

This is what the VirtualBox Wiki says a "template" is:

VirtualBox Wiki:Templates: What are templates?
Wiki templates provide a means to insert the same content over and over in different (or the same) pages. This saves editors the hassle of duplicating the same text again and again, and also helps ensure consistency.

Templates are generally shown with the format required to use the template (e.g. {{stub}}). Clicking the template name takes you to the template's page, where you can see what it looks like and how it is used.

h t t p : / / virtualbox(dot)wikia(dot)com/wiki/VirtualBox_Wiki:Templates

Are you calling the VM VirtualBox Manager sotftware, the "template"?

Line 1:

mpack wrote:The message means that you are trying to install a 64bit guest using a 32bit VM template.

I presume you're referring to the Ubuntu ISO that I downloaded as the "64-bit guest":
- ubuntu-16.04.2-desktop-amd64.iso 1,517,760 KB
So, yes, I'm trying to install that 64-bit Ubuntu "guest os".

What you mean by "32-bit VM template" is where I initially draw a blank, since that's not parlance that anyone brand new to this topic would know offhand. To my knowledge, I'm not even aware of any "template" in my possession.

But you know exactly what I have (since I've stated it many times), so if your first sentence implies I'm using a template, then, by God, I must be using this thing called a template.

So it behooves me to understand what the heck your first sentence is trying to convey, especially since it's clearly obvious to you EXACTLY what my setup includes, which is:
1. The 64-bit CPU which is an AMD Phenom II X4 810 2.60GHz, 16GB RAM (where AMD-v is enabled in the BIOS)
2. The 64-bit Windows 10 Pro host operating system (where Hyper-V is not checked in Windows OptionalFeatures.exe)
3. A downloaded Ubuntu 64-bit ISO file as the guest operating system
4. An installed Oracle VM VirtualBox Manager with the VirtualBox Graphical User Interface Version 5.1.22 r115126 (Qt5.6.2)

I don't have ANYTHING else, so the "template" you presume that exists must be one of those four things, is it not?

VMWare defines "template" as "A template is a master copy of a virtual machine that can be used to create many clones".
So now we need to define clones.
h t t p s : / / communities(dot)vmware(dot)com/thread/417400
- Templates are pre-configured VMs used for multiple deployments.
- Clone is exact copy of your existing VM.

Hmmmm... I still don't know what a template is on my machine.
All I have are the following four things, one of which must be the template:
1. The 64-bit CPU which is an AMD Phenom II X4 810 2.60GHz, 16GB RAM (where AMD-v is enabled in the BIOS)
2. The 64-bit Windows 10 Pro host operating system (where Hyper-V is not checked in Windows OptionalFeatures.exe)
3. A downloaded Ubuntu 64-bit ISO file as the guest operating system
4. An installed Oracle VM VirtualBox Manager with the VirtualBox Graphical User Interface Version 5.1.22 r115126 (Qt5.6.2)

Googling further for what you mean by "template", there is this article on "How to Use Oracle VM VirtualBox Templates":
h t t p : / / www(dot)oracle(dot)com/technetwork/articles/servers-storage-admin/howto-use-vb-templates-1695904.html

About Templates for Oracle VM VirtualBox
Prebuilt developer virtual machines (VMs) for Oracle VM VirtualBox offer a quick way to install and experience entire software stacks packaged into deployable appliances, providing a good way to test new software. Moreover, the ability to run multiple VMs, each in an isolated environment on a single physical server, allows you to utilize the available computer resources much more efficiently.

From that, I don't think I have a template. But you know EXACTLY what I have, since I stated it extremely clearly, so, since you assume I have a "template", then, I must have a "template". But where?

Occam's razor says that your use of the word "template" in your first sentence means you know I have this thing called a "template".
Since you clearly know I only have these four things, one of them MUST be the template.
1. The 64-bit CPU which is an AMD Phenom II X4 810 2.60GHz, 16GB RAM (where AMD-v is enabled in the BIOS)
2. The 64-bit Windows 10 Pro host operating system (where Hyper-V is not checked in Windows OptionalFeatures.exe)
3. A downloaded Ubuntu 64-bit ISO file as the guest operating system
4. An installed Oracle VM VirtualBox Manager with the VirtualBox Graphical User Interface Version 5.1.22 r115126 (Qt5.6.2)

Since Occam's razor says you know more than I do, and since you know that those four things are all I have, I have to presume the 32-bit "template" is what you're calling the VirtualBox software I downloaded from Oracle.

OK. Assuming that is a correct assumption, I will tell you that I have no idea whether the VirtualBox software I downloaded is 32-bit or 64-bit.
So what I'll do is uninstall it and delete what I had downloaded, and I'll start fresh, but I will ensure that I download a 64-bit "template" (which appears to be just a fancy name for the Oracle VirtualBox software located on my machine at "C:\apps\os\vbox\VirtualBox.exe".

You are obviously tying yourself in knots with the terminology. Put simply 'Template' is what you create by making the appropriate selections when using the VirtualBox Wizard to build your Virtual Machine. What you are finding with your Google searching is more about installing Pre-built Templates: Try this simple step-by-step: http://talesfromthedatacenter.com/archives/232