kernel panic when installing TinyCore OS

[wuzamarine]

I have downloaded and tried every 32bit x86 OS from TinyCore and I recieve the same error every time.

VBox log load output:

Code: Select all

00:00:25.129502 Changing the VM state from 'RUNNING' to 'RESETTING'
00:00:25.130578 APIC: Re-activating Local APIC
00:00:25.130614 CPUM: SetGuestCpuIdFeature: Enabled APIC
00:00:25.130648 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:25.135696 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:25.135812 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:25.135883 AC97: Reset
00:00:25.135997 PDMR3Reset: after     6 ms, 1 loops: 1 async tasks - piix3ide/0
00:00:25.152355 Changing the VM state from 'RESETTING' to 'RUNNING'
00:00:25.157159 VMMDev: Guest Log: BIOS: VirtualBox 5.0.40
00:00:25.168189 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:25.210533 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:25.211041 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:25.211232 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:25.211256 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:25.211277 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:25.222161 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xec (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:00:25.222381 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:25.222980 VMMDev: Guest Log: BIOS: ata0-0: PCHS=16383/16/63 LCHS=1024/255/63
00:00:25.224043 PIIX3 ATA: Ctl#0: RESET, DevSel=1 AIOIf=0 CmdIf0=0xec (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:00:25.224219 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:25.225237 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa1 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:25.225366 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:25.236491 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:25.258043 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f6574f63000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0
00:00:25.258108 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=640x480, Sending to async-handler
00:00:25.258153 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=640x480
00:00:25.258168 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=640x480
00:00:25.258180 GUI: UIFrameBufferPrivate::performResize: Size=640x480, Directly using source bitmap content
00:00:27.714740 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:27.716124 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:27.716192 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:27.716207 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:27.716218 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:27.722875 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:27.723094 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0231
00:00:27.723267 VMMDev: Guest Log: BIOS: Boot from Floppy 0 failed
00:00:27.723461 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023
00:00:27.723796 VMMDev: Guest Log: BIOS: Booting from CD-ROM...


Boot following selection:
00:00:37.700079 VMMDev: Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:37.700302 VMMDev: Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
00:00:37.845030 PIT: mode=2 count=0xf89 (3977) - 300.02 Hz (ch=0)
00:00:37.995315 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:38.059961 OHCI: Software reset
00:00:38.149398 IEM: rdmsr(0x64e) -> #GP(0)
00:00:38.149606 IEM: wrmsr(0xe01,0x0`2000001f) -> #GP(0)

the screen I'm looking at:
pix.toile-libre(dot)org/upload/original/1509026637.png

I get this error just as soon as I select the boot method, just like a chipset error. Like I was trying to boot 64bit from a 32 bit, but its the other way around.

host machine specs bpaste(dot)net/show/9aa3ac2829c4

Note: I tried with and without PAE. Same results.

[socratis]

For future reference, please do not simply copy/paste huge chunks of text verbatim. Instead save the information in a simple, plain text file, ZIP that file and attach that.

Also, partial logs are not that helpful I'm afraid. Please ZIP and attach the full VBox.log. See the "Upload attachment" tab below the reply form.

And finally, please tell me the exact ISO that you used to boot your guest, so I can try it on mine host as well.

PS. I didn't replace your URLs with the actual URL because at this point they don't provide anything helpful. In the future, please attach images (cropped at the problem) and text (ZIPped if it's too big) here, locally. Not a lot of people go to 3rd party sites...

[wuzamarine]

I have tried all of these images that are x86
http://tinycorelinux.net/downloads.html

VirtualBox isn't spitting out any errors. I posted the logs to show that there was nothing there of use to report. I apologize for the mess.
I'm not sure where to look. I tried PAE
It's not like I can get to syslog-ng, to try an see what that panic is all about.

[socratis]

Yes, but you still haven't posted the VBox.log.zip. I need it to see your settings...

Please ZIP and attach the full VBox.log.

please tell me the exact ISO that you used to boot your guest, so I can try it on mine host as well.

[wuzamarine]

Here are the logs

These are the images I downloaded

Core-current.iso dCorePlus-xenial.iso tc-install-beta.iso
CorePlus-current.iso TinyCore-current.iso

The website still won't let me post urls

[socratis]

These are the images I downloaded: Core-current.iso dCorePlus-xenial.iso tc-install-beta.iso CorePlus-current.iso TinyCore-current.iso

This is not helpful at at all, because the "current" is going to look a lot different in a couple of months. So, for the sake of accuracy, as of today 2017-10-28, the "current" points to version 8.2. "Core x86 Release Files", points to http://tinycorelinux.net/8.x/x86/release/ with the "Core-current.iso" being exactly the same as http://tinycorelinux.net/8.x/x86/release/Core-8.2.iso. That's the one we're talking about. Let's try this, or even the graphical http://tinycorelinux.net/8.x/x86/releas ... us-8.2.iso.

VirtualBox VM 5.0.40_Ubuntu r115130 linux.amd64 (Apr 20 2017 06:58:05) release log

It looks like you're using the distro's fork version of VirtualBox. You can either ask in their forums for help, or completely remove/uninstall/delete/purge their version and install the official version from the Downloads section of VirtualBox (https://www.virtualbox.org/wiki/Downloads).

00:00:00.600086 Guest OS type: 'Linux24'

Any reason why you picked the "Linux 2.4 (32-bit)" template and not the more appropriate "Linux 2.6/3.x/4.x (64-bit)"? No kidding this thing won't boot!

00:00:00.647036 VRamSize <integer> = 0x0000000000600000 (6 291 456, 6 MB)

Did you notice the warning triangle icon to the left of the "OK"/"Cancel" in the VM settings? A warning you that your vRAM is too low? That warning is not there just to take some unused space, there's a reason for its existence...

Since a lot of the settings defaults are set from the template, I would suggest to delete your VM and create a new one. Select the "Linux 2.6/3.x/4.x (64-bit)" template. If you want to change something, like the memory, do it. But don't do it immediately. Do it only after you've done a successful boot. Then change one setting at a time, *if* you have to, *and* you know what you're doing. Boot it again and see if it boots.

So, in summary:

1. Remove the fork from the Ubuntu store and install the official VirtualBox.
2. Create a new VM withe the "Linux 2.6/3.x/4.x (64-bit)" template.
3. Don't change settings at random. The defaults have been chosen carefully for your sake.

[wuzamarine]

Current = current. If I respond to a post then that day I downloaded another copy and tried that, including today.

00:00:00.600086 Guest OS type: 'Linux24'

Any reason why you picked the "Linux 2.4 (32-bit)" template and not the more appropriate "Linux 2.6/3.x/4.x (64-bit)"? No kidding this thing won't boot!

Computer Science 101. 64bit x86 has the exact same eax, ebx, ecx, edx, esi, edi, ebp, esp registers as 32bit.
32bit is 100% compatible with 64bit UNLESS the designing engineer did something absolutely ignorant.
Any 32bit binary should install on a 64bit system with no issues at all. It is the other way around you cannot do, because 32bit does not have the same r8-15 registers
https://wiki.cdot.senecacollege.ca/wiki ... uick_Start
My target device is 32bit. The compiling host is 64bit.
FYI, I get the same panic when compiling on the 32 bit target client. Its just a phone and a pain to work with.

00:00:00.647036 VRamSize <integer> = 0x0000000000600000 (6 291 456, 6 MB)

Did you notice the warning triangle icon to the left of the "OK"/"Cancel" in the VM settings? A warning you that your vRAM is too low? That warning is not there just to take some unused space, there's a reason for its existence...

Interesting. The minimum requirements for tinycore is 48MB. I have 512 allocated.
Something doesn't seem right.
Thats why they call it TinyCore, it's very Tiny.
There is no 'low memory' icon anywhere.
https://en.wikipedia.org/wiki/Tiny_Core_Linux

VirtualBox VM 5.0.40_Ubuntu r115130 linux.amd64 (Apr 20 2017 06:58:05) release log

It looks like you're using the distro's fork version of VirtualBox. You can either ask in their forums for help, or completely remove/uninstall/delete/purge their version and install the official version from the Downloads section of VirtualBox (https://www.virtualbox.org/wiki/Downloads).

Trying this now...

[socratis]

Current = current.

Well, not exactly. In six months or in two years when someone is reading this thread, things will have changed, unless TinyCore freezes its development. When there is a version available, current is moot.

Computer Science 101. 64bit x86 has the exact same eax, ebx, ecx, edx, esi, edi, ebp, esp registers as 32bit.

I'll switch you CompSci 101 with ChemEng 101. You want to start comparing notes?
The reason I wrote this is because I had some issues with the 32-bit template getting it to work over here. Plus the default is 64-it, so that's it. But, I tried it again with the 32-bit template and it was working just fine this afternoon. Maybe a register was stuck or something...
You can have the 32-bit template, but at least choose something more ... recent for the kernel. From the looks of it, TinyCore 8.2 is running with a 4.8.17 kernel after all.

The minimum requirements for tinycore is 48MB. I have 512 allocated.

I didn't say RAM, I said vRAM, as in video-RAM or graphics RAM. Even the "Linux 2.4 (32-bit)" that you selected, has a default of 16 MB of vRAM, so that means that you took the amount of vRAM down. And that should have caused VirtualBox to draw a triangle which if you hover over it, it complains with a:

The virtual machine is currently assigned less than 10 MB of video memory which is the minimum amount required to switch to full-screen or seamless mode.

Not that you would, but it's complaining nonetheless.

My target device is 32bit. The compiling host is 64bit. FYI, I get the same panic when compiling on the 32 bit target client. Its just a phone and a pain to work with.

I wouldn't even know what that means. And since it's not VirtualBox related, I can't say that it's interesting, unless you tie them somehow

[wuzamarine]

SOLVE IT, not Solvent. This is a computer form, remember
Stuck register? You mean a broken chip? Nah, my chip is fine.
But what you post could be a major issue. This looks like a bug.
64bit installs on my system, 32bit fails.
Looks like somebody @ Tiny screwed up big time..

[mpack]

You don't seem to have addressed the fact that you aren't using VirtualBox. I'm afraid we need to call a halt to this discussion until you do.

This site exists to support Oracle VirtualBox, not someones fork of it modified in unknown ways. Either look for support on the forker's forums, or purge it and install VirtualBox from the downloads area of this site.

[wuzamarine]

Are you not reading the thread?
This thread is 100% about VirtualΒox.

[mpack]

VirtualBox VM 5.0.40_Ubuntu r115130 linux.amd64 (Apr 20 2017 06:58:05) release log

Ubuntu fork.

== Not VirtualBox.

and this is the last time of telling.

If the log is out of date then provide a new one.

[wuzamarine]

Thats still VirtualBox.
Its just been fixed for that distro.
Until they rename it Not-so-virtualbox or any other naming schema, it is and will remain VIRTUALBOX. it just a fork.
Stop trying to confuse people.

No, the logs are still the same. The error never went away.

[socratis]

Thats still VirtualBox. Its just been fixed for that distro.

Then I'm afraid that you'll have to ask the people that "fixed" it for the solution. In these forums we only deal with the official VirtualBox. If you are having this problem with the official VirtualBox, then we can continue this discussion. The rest of them are just forks. Period.

No, the logs are still the same. The error never went away.

You were supposed to implement a series of changes, based on my post. If you didn't do that (including getting the official VirtualBox), then there's no point in continuing this discussion I'm afraid...

[01-pp-com]

Having same problems as OP.

Originally I was using same ubuntu-based pkg as OP, but got rid of those and followed suggestion to use oracle's release.

Now I'm using vb 6.0.4 r128418 downloaded from oracle site today.

In either case it doesn't matter, gives same error regardless of oracle vs canoical (sic).

This is using tinycore linux 8.1.1 (core, tinycore or coreplus, all same) running as 32bit guest on 64bit ubuntu host.


SNIPPET (see attachment for full logs)

Code: Select all

00:00:14.976575       Press ENTER to boot, TAB to edit, or press F1 for more information.       
00:00:14.976591 Boot TinyCore with Embedded X/GUI extensions.                                   
00:00:14.976606 Boot media is removable. Use TAB to edit options for specific needs.            
00:00:14.976622                                                                                 
00:00:14.976638                                                                                 
00:00:14.976654 Loading /boot/vmlinuz......                                                     
00:00:14.976670 Loading /boot/core.gz..........ready.                                           
00:00:14.976686 early console in extract_kernel                                                 
00:00:14.976702 input_data: 0x005c5114                                                          
00:00:14.976719 input_len: 0x003a3c1d                                                           
00:00:14.976735 output: 0x00100000                                                              
00:00:14.976751 output_len: 0x0075e70c                                                          
00:00:14.976767 kernel_total_size: 0x00882000                                                   
00:00:14.976783                                                                                 
00:00:14.976799 Decompressing Linux... Parsing ELF... No relocation needed... done.             
00:00:14.976815 Booting the kernel.                                                             
00:00:14.976831                                                                                 
00:00:14.976847 --------------------------------------------------------------------------------
00:00:14.976861 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:14.976936 emR3Debug: rc=VERR_PATM_IPE_TRAP_IN_PATCH_CODE