I can't instal any OS
Virtual Box 5.2.44 r139111 (Qt5.6.2)
Processor : Intel(R) i3
Hosts OS: Windows 7
Try install - debian-live-11.3.0-i386-cinnamon.iso
ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
Why? How to install any Linux 32-bit?
How to install any 64 bit OS on Win 7?
ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
thank you for reply !
I closed the Virtualbox window for the VM with the Power Off option set.
I closed the Virtualbox window for the VM with the Power Off option set.
- Attachments
-
- 111-2022-09-25-21-37-27.rar
- (20.78 KiB) Downloaded 170 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
According to https://www.intel.com/content/www/us/en ... tions.html your CPU has VT-x, and VT-x is off in your BIOS. See I have a 64bit host, but can't install 64bit guests.
00:00:02.496572 Console: Machine state changed to 'Restoring'
'Restoring' means the VM was save-stated. Therefore the VM log is missing important diagnostic info. Try again, please, after turning on VT-x.scottgus1 wrote:Start the VM from full normal shutdown, not save-state.
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
I turned on Virtualization in BIOS and everything works well. Thank you very much!
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
Great! Glad you're up and running.
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
Had the same error, was with a Debian Bullseye (11.4) guest
Strangely, had another Bullseye (11.6) guest that wasn't hit by that.
And that defective guest has previously been working for month without problem.
Also, VT support is enabled in BIOS, but it's grayed and not enabled in the guests parameters.
(i might be wrong, but IIRC i had those checked when installing those guests).
Eventually solved it following this advice to add a second CPU, to my surprise it worked:
viewtopic.php?t=106069
Removed the (now irrelevant) difference list from the two guests, because i can reproduce the error,
the working VM does the same error if i assign it 1 CPU only, definately this.
Will try some other tests and report soon after some reboots, of the host too, meanwhile some complementary info:
* Windows 11 host, but upgraded from Win10 (had some network bugs that don't happen on a "fresh" W11 install)
* Guests are Debian installed from the minimal ISO file, no X-windows/GUI or other fancy stuff
* Same version of the Guest additions on the two guests
(checked the log: Guest Additions information report: Version 6.0.0 r127566 '6.0.0'...
Looks like i'll have to upgrade them as i'm using VirtualBox 7.0, will report if that manages to solve working with 1 CPU only)
Strangely, had another Bullseye (11.6) guest that wasn't hit by that.
And that defective guest has previously been working for month without problem.
Also, VT support is enabled in BIOS, but it's grayed and not enabled in the guests parameters.
(i might be wrong, but IIRC i had those checked when installing those guests).
Eventually solved it following this advice to add a second CPU, to my surprise it worked:
viewtopic.php?t=106069
Removed the (now irrelevant) difference list from the two guests, because i can reproduce the error,
the working VM does the same error if i assign it 1 CPU only, definately this.
Will try some other tests and report soon after some reboots, of the host too, meanwhile some complementary info:
* Windows 11 host, but upgraded from Win10 (had some network bugs that don't happen on a "fresh" W11 install)
* Guests are Debian installed from the minimal ISO file, no X-windows/GUI or other fancy stuff
* Same version of the Guest additions on the two guests
(checked the log: Guest Additions information report: Version 6.0.0 r127566 '6.0.0'...
Looks like i'll have to upgrade them as i'm using VirtualBox 7.0, will report if that manages to solve working with 1 CPU only)
Re: ERROR: Kernel panic - not syncing: Attempted to kill the idle task!
Ok, did some more tests:
first on the Debian OS side: apt udate && apt upgrade && poweroff
then setting 1CPU => still same bug
Then used the "insert guest additions CD" menu,
ran the VBoxLinuxAdditions.run without problem, but still the same: boots ok with 2 CPU but not 1 CPU.
(BTW while running the VBoxLinuxAdditions.run noticed a line saying
"removing installed version 6.1.12", while the logs previously showed a "6.0.0 r127566" version, seems fixed now as i've in the log:
VMMDev: Guest Additions information report: Version 7.0.4 r154605 '7.0.4')
Tested it, this also happens with an old Debian 10 VM, and also with a Debian 12.
Update:
Seems to be fixed now, upgraded VirtualBox From 7.0.4 to 7.0.8 and now all my Debian guests starts correctly also with 1 CPU only.
first on the Debian OS side: apt udate && apt upgrade && poweroff
then setting 1CPU => still same bug
Then used the "insert guest additions CD" menu,
ran the VBoxLinuxAdditions.run without problem, but still the same: boots ok with 2 CPU but not 1 CPU.
(BTW while running the VBoxLinuxAdditions.run noticed a line saying
"removing installed version 6.1.12", while the logs previously showed a "6.0.0 r127566" version, seems fixed now as i've in the log:
VMMDev: Guest Additions information report: Version 7.0.4 r154605 '7.0.4')
Tested it, this also happens with an old Debian 10 VM, and also with a Debian 12.
Update:
Seems to be fixed now, upgraded VirtualBox From 7.0.4 to 7.0.8 and now all my Debian guests starts correctly also with 1 CPU only.