TinyCore Linux Error - VERR_PATM_IPE_TRAP_IN_PATCH_CODE

[Squirrelish]

I am having trouble booting TinyCore Linux (8.0) on VirtualBox 5.1.28; I get a fatal error when it starts the kerrnel (VERR_PATM_IPE_TRAP_IN_PATCH_CODE), log is attached.

A brief set of notes on the VM configuration, where the TinyCore ISO image was retrieved here:

http://tinycorelinux.net/downloads.html

Code: Select all

System
-> Motherboard
---> Base Memory: 64MB
---> Boot Order: Optical
---> Chipset: PIIX3
---> Pointing Device: PS/2 Mouse
---> Extended Features: Hardware Clock in UTC Time
-> Processor
---> Processor(s): 1
---> Execution Cap: 100%
---> Extended Features: None
-> Acceleration
---> Paravirtualization Interface: None
---> Enable VT-d/AMD-V: Unchecked
Display
-> Screen
---> Video Memory: 4MB
---> Monitor Count: 1
---> Scale Factor: 100%
---> Acceleration: None checked
-> Remote Display: None checked
-> Video Capture: None checked
Storage
-> Controller: IDE
---> Type: PIIX3
---> Use Host I/O Cache: Unchecked
---> IDE Primary Master
------> TinyCore-current.iso
------> Live CD/DVD: Unchecked
Audio
-> Enable Audio: Unchecked
Network
-> Adapter 1
---> Enable Network Adapter: Checked
---> Attached to: NAT
---> Adapter type: PCnet-FAST III
USB
-> Enable USB Controller: Unchecked

I searched the forum and found this, although it was never answerd:
viewtopic.php?f=7&t=83729

Any help is appreciated! Thanks!

[socratis]

00:00:06.357885 Guest OS type: 'Linux'

Please change the template to "Linux 2.6/3.x/4.x (32-bit)".

---> Video Memory: 4MB

I get a warning in the settings when I set 4 MB of VRAM on my system.

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.

Then you have a series of similar messages, just before the Guru meditation:

Code: Select all

00:00:22.293930 PATM: Disabling IDT 80 patch handler c058e490
00:00:22.297803 PATM: Disabling IDT fd patch handler c058ec00
00:00:22.299835 PATM: Disabling IDT fc patch handler c058ec40
00:00:22.301260 PATM: Disabling IDT fb patch handler c058ec80
00:00:22.302339 PATM: Disabling IDT 20 patch handler c058ecc0
00:00:22.306225 PATM: Disabling IDT f8 patch handler c058ecf0
00:00:22.307865 PATM: Disabling IDT f7 patch handler c058ed30
00:00:22.309063 PATM: Disabling IDT f2 patch handler c058ed70
00:00:22.310560 PATM: Disabling IDT f1 patch handler c058edb0
00:00:22.311738 PATM: Disabling IDT ef patch handler c058edf0
00:00:22.312896 PATM: Disabling IDT fe patch handler c058ee30
00:00:22.314327 PATM: Disabling IDT f0 patch handler c058ee70
00:00:22.315470 PATM: Disabling IDT f6 patch handler c058eeb0
00:00:22.316552 PATM: Disabling IDT fa patch handler c058eef0
00:00:22.317969 PATM: Disabling IDT f9 patch handler c058ef30
00:00:22.319021 PATM: Disabling IDT f4 patch handler c058ef70
00:00:22.319837 PATM: Disabling IDT 10 patch handler c058efb0
00:00:22.320901 PATM: Disabling IDT 13 patch handler c058efc0
00:00:22.322223 PATM: Disabling IDT 7 patch handler c058efd0
00:00:22.323250 PATM: Disabling IDT 4 patch handler c058eff0
00:00:22.324290 PATM: Disabling IDT 5 patch handler c058f000
00:00:22.324442 PATM: Disabling IDT 6 patch handler c058f010
00:00:22.324574 PATM: Disabling IDT 9 patch handler c058f020
00:00:22.324707 PATM: Disabling IDT a patch handler c058f030
00:00:22.324830 PATM: Disabling IDT b patch handler c058f040
00:00:22.324947 PATM: Disabling IDT c patch handler c058f050
00:00:22.325064 PATM: Disabling IDT 11 patch handler c058f060
00:00:22.325171 PATM: Disabling IDT 0 patch handler c058f070
00:00:22.325286 PATM: Disabling IDT 12 patch handler c058f080
00:00:22.325406 PATM: Disabling IDT f patch handler c058f090
00:00:22.325563 PATM: Disabling IDT e patch handler c058f0e0
00:00:22.325666 PATM: Disabling IDT 1 patch handler c058f150
00:00:22.325763 PATM: Disabling IDT 2 patch handler c058f1b0
00:00:22.325874 PATM: Disabling IDT 3 patch handler c058f280
00:00:23.246575 PATM: Disabling IDT 30 patch handler c058e5a0

I have the suspicion that it has to do with a couple of factors, but mainly it's the "Enable VT-x/AMD-V" that's causing your Guru meditation.

The problem arose because you chose the wrong template, "Linux Other 32-bit" and the wrong defaults were applied. I'm going to copy/paste your settings as you posted them, but with the correct values for a "Linux 2.6/3.x/4.x (32-bit)" template. Please change the settings in your VM to match those below. The bold ones need to change:

• System
  -> Motherboard
  ---> Base Memory: 512 MB
  ---> Boot Order: Optical
  ---> Chipset: PIIX3
  ---> Pointing Device: USB Tablet   (That was acting weird. You might want to leave it to PS/2 mouse.)
  ---> Extended Features: Hardware Clock in UTC Time
  -> Processor
  ---> Processor(s): 1
  ---> Execution Cap: 100%
  ---> Extended Features: None
  -> Acceleration
  ---> Paravirtualization Interface: Default
  ---> Enable VT-d/AMD-V: Checked
  ---> Enable Nested Paging: Checked
  Display
  -> Screen
  ---> Video Memory:  16 MB
  ---> Monitor Count: 1
  ---> Scale Factor: 100%
  ---> Acceleration: None checked
  -> Remote Display: None checked
  -> Video Capture: None checked
  Storage
  -> Controller: IDE
  ---> Type: PIIX4
  ---> Use Host I/O Cache: Checked
  ---> IDE Primary Master
  ------> TinyCore-current.iso
  ------> Live CD/DVD: Unchecked
  Audio
  -> Enable Audio: Checked
  ---> Audio Controller: ICH AC97
  Network
  -> Adapter 1
  ---> Enable Network Adapter: Checked
  ---> Attached to: NAT
  ---> Adapter type: Intel PRO/1000 MT Desktop
  USB
  -> Enable USB Controller: Checked
  ---> USB 2.0: Checked

[Squirrelish]

socratis, thanks for the reply!

I indeed got it working using the following two changes you suggested:
Template: "Linux 2.6/3.x/4.x (32-bit)"
Enable VT-d/AMD-V: Checked

The rest I kept as I had them because I am emulating an old environment.

A couple questions, if you don't mind...
What is the generic Linux template for?
Any idea why Guru meditation would occur without virtualization support in the hardware? I figured without it, the emulation would occur without acceleration but still work functionally the same way?

Thanks again!

[socratis]

Enable VT-d/AMD-V: Checked

That's what did it. That's why I had that in red-bold, because it was the key parameter that needed to be enabled. The rest will make the VM perform better, but if you want to mimic an older system, that's fine...

What is the generic Linux template for?

Anything that's not covered by more specific templates. It's a way more "conservative" template, mainly for unknown, older OSes. Linux 1.x and early 2.x comes to mind.

Any idea why Guru meditation would occur without virtualization support in the hardware? I figured without it, the emulation would occur without acceleration but still work functionally the same way?

Not since the 5.x series came out. Hardware is moving forward, so it's rather difficult these days to come across a computer that doesn't support VT-x/AMD-V. The software emulation has been gradually phased out and moving forward will be more and more so.