virtualbox.org

Host: Core i7-8750H CPU @ 2.20GHz
Host OS: Win 10
Host RAM: 16GB

VBox version: 6.0.10 r132072 (Qt5.6.2)
Guest OS: Android -x86 8.1-rc1 64bit
Guest Memory: 4 GB
Guest Video Memory: 9 MB

Can't boot Android -x86 8.1-rc1 64bit on Vbox.

Prompts:

Progress: This kernel requires an x86-64 CPU, but only detected an i686 CPU
Unable to boot - please use a kernel appropriate for you CPU.

1)so i have a similar issue and my android isn't booting up, first it showed kernel panic: acpi+timer does not work, uploaded vbox log file
2)after trying many things like noapic nolapic acpi=off its kernel panic: not syncing, attempted to kill idle task!
at one point(i don't remember WHAT i did), it boots till the homescreen then hangs and reboots.
P.S. HELP! i need to use whatsapp!

Please try a fresh new VM with Mpack's Android recipe here: viewtopic.php?f=3&t=92683&start=15#p464073 I ran an Android VM from that recipe with success getting the OS to install and boot correctly. I would suggest two processors in the VM.

If you have problems, please provide the log after the VM window has been fully closed.

joelsamueljohnson wrote:HELP! i need to use whatsapp!

That was the reason for my Android VM too, and the performance of WhatsApp was not good. I ended up getting a used Android phone for WhatsApp.

I note that your VM deviates from the known recipe significantly, e.g. not based on a Linux template, not 32bit, and what I consider to be too much RAM.

I suggest that you start again, and follow the recipe I describe here: viewtopic.php?f=3&t=92683&start=15#p464073.

Otherwise tell us what you did differently, and why.

I also note that you have Hyper-v enabled, this usually interferes with VirtualBox. See here for how to correctly disable it: HMR3Init: Attempting fall back to NEM (Hyper-V is active)

i had posted a comment here, it got deleted.
my android vm is not working, when it boots it says 'kernel panic: not syncing: io-acpi+timer does not work' and reboots.
log file attached

Cross posting is against the forum rules, and besides which you already received answers. Any future cross posts will be deleted, which is (I assume) why your last attempt was deleted.

its showing kernel panic: not syncing: attempted to kill idle task! rebooting in 5...

Joel, are you reading the posts other have written? The last posted log of your VM is not configured according to Mpack's recipe.

here it is. this is after trying mpack's recipe

You missed some things in your VM's setup.

From Mpack's recipe:

....
Network: bridged.
Intel HD Audio (not tested yet).
...
USB3 enabled.

From your log:

00:00:04.348287 [/Devices/e1000/0/LUN#0/] (level 4)
00:00:04.348288 Driver <string> = "NAT" (cb=4) <- should be Bridged
00:00:04.348321 [/Devices/ichac97/] (level 2) <- should be hda
00:00:04.348519 [/Devices/usb-ehci/] (level 2) <- should be xhci for USB3

However, the log is not anywhere near what a normal Virtualbox log should be. Several diagnostic lines are missing. Possibly because Hyper-V is enabled on the host:

00:00:04.348930 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

One other thing: if you're cutting lines from the log to get it under the forum size limit, please don't. Zipped logs fit.

it worked!!!! thanks man. thanks a lot.

Great! Glad you're up and running!