Page 1 of 1

Windows 8.1 64bit Guest on a Windows 8.1 64bit machine

Posted: 24. Mar 2014, 17:57
by ABCraine
My Host machine:
Windos 8.1
Processor: Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz 1.70GHz
RAM: 4.00 GB
System type: 64-bit Operating System, x64-ased processor

I downloaded:
VirtualBox-4.3.8-92456-Win.exe


I rt-clicked on the file to Run as Administrator
I clicked through the install wizard, taking all the defaults

When it opened up, I found all of my old XP VMs.
I tested one, and it logged in ok.

I would like to create a 64bit Windows 8.1 VM
So I clicked New
The only options were 32 bit os
I went back to the download and ran it again (without uninstalling
it), I did this by accident and found out that a repair comes up
that will bring forth the 64bit OS options.

First I get a window that tells me I need to restart my machine,
but I also get the opened VirtualBox which shows (under New)
the 64bit OS options.

So I restart my machine.
And the 64bit OS options are no longer there when I click New.

Mistakes I made last night when I was trying this:
Create the 64bit VM without restarting my machine
I took all of the default clicks in the wizard.
Went to settings->Storage-> Host Drive to read the CD (clicked on PassThrough)
I received an error:
After a bit of a wait a window that said -
Creating process for virtual machine "Name"
it has something to indicate the time left, it shows nothing
and 0% for quite awhile (> 20 min with no progress in the progress bar),
then I x'ed out.

Another window I've seen when trying this is:
Cannot access the kernel driver.

Mistakenly created the VM to be 32bit 8.1; in this case it
read the CD and told me that I was trying to load a 64bit
OS onto a 32bit machine. (At least it read the CD)

Please Help.
What do I need to do to
a) keep the 64bit OS option available after a reboot
b) successfully load my windows 8.1 64bit OS into a VM

Re: Windows 8.1 64bit Guest on a Windows 8.1 64bit machine

Posted: 24. Mar 2014, 18:13
by mpack
Please search for previous answers before asking a FAQ.

Hint: disable Hyper-v.