Hi, i don't know why my Ubuntu doesn't work.
I see others post at the forum and i have tried with up my VirtualMachine CPU to 2 core
and the RAM but doesn´t work.
Will be very grateful for any advises. Logs and screen attached.
[Solved] Kernel Panic - not syncing: Attempted to kill init!
[Solved] Kernel Panic - not syncing: Attempted to kill init!
- Attachments
-
- screenshot_and_logs.zip
- the logs
- (122.74 KiB) Downloaded 427 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Kernel Panic - not syncing: Attempted to kill init!
Try a more current version of VirtualBox (i.e. 6.1.34). Linux kernels get updated, your VirtualBox software needs to be updated too.
You also have Hyper-v enabled on the host, which is known to cause conflicts.
You also have Hyper-v enabled on the host, which is known to cause conflicts.
See HMR3Init: Attempting fall back to NEM (Hyper-V is active).00:00:03.226396 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.278596 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
Re: Kernel Panic - not syncing: Attempted to kill init!
Thank you so much, this has solved the issue.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: [Solved] Kernel Panic - not syncing: Attempted to kill init!
Thanks for reporting back. Thanks also for providing a zipped log in your first post.
Re: [Solved] Kernel Panic - not syncing: Attempted to kill init!
Hola,
Para este problema al instalar algunas distribuciones de Linux el cual nos arroja el error "Kernel Panic - not syncing: Attempted to kill init!" lo que debemos hacer es desactivar en Caracteristicas de windows las opciones "Hyper-V" y tambien "Plataforma de maquina virtual", en mi caso me faltaba desactivar esta ultima opción. Espero les sea de gran ayuda.
Para este problema al instalar algunas distribuciones de Linux el cual nos arroja el error "Kernel Panic - not syncing: Attempted to kill init!" lo que debemos hacer es desactivar en Caracteristicas de windows las opciones "Hyper-V" y tambien "Plataforma de maquina virtual", en mi caso me faltaba desactivar esta ultima opción. Espero les sea de gran ayuda.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: [Solved] Kernel Panic - not syncing: Attempted to kill init!
This sometimes does not work, since there are many Windows services that can use Hyper-V, not only these two. Please see the link in Mpack's post above.AndresJC wrote:hacer es desactivar en Caracteristicas de windows las opciones "Hyper-V" y tambien "Plataforma de maquina virtual"
Re: [Solved] Kernel Panic - not syncing: Attempted to kill init!
The settings that worked for me with Cinnamon version 21 was 2048 mb memory, and 2 cores (this seemed to be required because when I toggled it to 1, I got the error again).
Also, I maxed video memory to 128mb.
Acceleration was set to "default" with Enable Nested Paging checked.
But the machine loaded with Acceleration set to "none" after installing (but I did not test the installation under that setting).
I used virtual box portable version 5.1.22 for windows from vbox.me
I hope this helps others.
It worked for me.
Also, I maxed video memory to 128mb.
Acceleration was set to "default" with Enable Nested Paging checked.
But the machine loaded with Acceleration set to "none" after installing (but I did not test the installation under that setting).
I used virtual box portable version 5.1.22 for windows from vbox.me
I hope this helps others.
It worked for me.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: [Solved] Kernel Panic - not syncing: Attempted to kill init!
Thanks, aHuman, for relating your experience!
To let all know, portable Virtualbox is not supported here, and 5.1 is rrrreeeeaaallllllllyyyy old.
Recent months have seen Virtualbox VMs running under Windows hosts with active Hyper-V require 2 processors. More or less may not work well or at all.
Paravirtualization is not the "Hyper-V" that causes trouble. It's a language name for the communication between Virtualbox and a virtualization-aware VM OS. Windows VMs use Hyper-V paravirtualization, Linux uses KVM paravirtualization, etc, regardless of the host OS or services being used.
To let all know, portable Virtualbox is not supported here, and 5.1 is rrrreeeeaaallllllllyyyy old.
Recent months have seen Virtualbox VMs running under Windows hosts with active Hyper-V require 2 processors. More or less may not work well or at all.
Paravirtualization is not the "Hyper-V" that causes trouble. It's a language name for the communication between Virtualbox and a virtualization-aware VM OS. Windows VMs use Hyper-V paravirtualization, Linux uses KVM paravirtualization, etc, regardless of the host OS or services being used.