The officially official Devuan Forum!

You are not logged in.

#1 2023-11-24 18:02:36

Altoid
Member
Registered: 2017-05-07
Posts: 1,366  

dmesg printout when starting VirtualBox VM

Hello:

After some problems with my XPSP3 VM crashing, I am now getting this printout every time I start the VM.
All this runs under VirtualBox Version 7.0.12 r159484 from the VirtualBox repository.

This happens (no surprise) with XPSP3, stopping and restarting a Chimaera headless VM does not have this problem, so it would seem to be limited to the Windows VM.

commands

~$ vboxmanage list vms
"groucho xp" {e2bdf021-b1a1-49b8-8ec9-3d4a5d194751}
"madmax chimaera" {9a65cf7c-2559-40de-a17e-8d1ab90871e6}
~$
~$ vboxmanage controlvm "madmax chimaera" poweroff
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
~$
~$ vboxmanage startvm "madmax chimaera" --type headless
Waiting for VM "madmax chimaera" to power on...
VM "madmax chimaera" has been successfully started.
~$ 

dmesg rolling printout

--- snip ---
[  +0.000002] ---[ end trace 1be0adc72d562557 ]---
[Nov24 14:49] device eth0 left promiscuous mode
[  +0.031478] vboxnetflt: 454 out of 45463 packets were not sent (directed to host)
[ +20.695654] vboxdrv: 000000001ad1bd93 VMMR0.r0
[  +0.123945] vboxdrv: 00000000d078db46 VBoxDDR0.r0
[  +0.040694] VBoxNetFlt: attached to 'eth0' / 00:14:4f:4a:a2:81
[  +0.041263] device eth0 entered promiscuous mode

This is the dmesg rolling printout when I start the XPSP3 VM:

[Nov24 14:40] ------------[ cut here ]------------
[  +0.000012] WARNING: CPU: 0 PID: 24553 at arch/x86/kernel/fpu/core.c:129 kernel_fpu_begin_mask+0xc9/0xe0
[  +0.000001] Modules linked in: nls_ascii nls_cp437 vfat fat uas usb_storage usblp fuse vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd grace nfs_ssc fscache sunrpc drivetemp snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation uvcvideo snd_soc_core snd_usb_audio coretemp videobuf2_vmalloc videobuf2_memops snd_compress snd_usbmidi_lib videobuf2_v4l2 soundwire_cadence videobuf2_common kvm_intel snd_rawmidi snd_hda_codec videodev kvm snd_hda_core snd_seq_device snd_hwdep irqbypass pcspkr nvidia(POE) serio_raw mc joydev soundwire_bus at24 snd_pcm_oss snd_mixer_oss snd_pcm drm snd_timer snd soundcore evdev x38_edac acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic hid_logitech_hidpp hid_logitech_dj sg hid_generic sd_mod usbhid t10_pi crc_t10dif crct10dif_generic hid crct10dif_common mptsas ahci mptscsih libahci xhci_pci aic7xxx libata mptbase uhci_hcd ehci_pci
[  +0.000069]  xhci_hcd scsi_transport_sas scsi_transport_spi e1000e ehci_hcd i2c_i801 i2c_smbus scsi_mod ptp usbcore usb_common pps_core button
[  +0.000015] CPU: 0 PID: 24553 Comm: EMT-0 Tainted: P           OE     5.10.0-0.deb10.16-amd64 #1 Debian 5.10.127-2~bpo10+1
[  +0.000002] Hardware name: Sun Microsystems Ultra 24/Ultra 24, BIOS 1.56    01/21/2011
[  +0.000002] RIP: 0010:kernel_fpu_begin_mask+0xc9/0xe0
[  +0.000003] Code: c4 10 5b c3 65 8a 05 7e 5f 9e 4d 84 c0 74 92 0f 0b eb 8e f0 80 4f 01 40 48 81 c7 40 14 00 00 e8 dd fb ff ff eb a5 db e3 eb c4 <0f> 0b e9 7b ff ff ff e8 bb 23 85 00 66 66 2e 0f 1f 84 00 00 00 00
[  +0.000002] RSP: 0018:ffffba77c3f9fb30 EFLAGS: 00010002
[  +0.000002] RAX: 0000000080000001 RBX: 0000000000000003 RCX: ffffba77c7819000
[  +0.000002] RDX: 0000000000000000 RSI: ffffba77c793d000 RDI: 0000000000000003
[  +0.000001] RBP: ffffba77c3f9fb50 R08: 0000000000000000 R09: 0000000000000010
[  +0.000002] R10: ffffba77c3ffc000 R11: 0000000000000000 R12: ffffba77c793d000
[  +0.000002] R13: ffffba77c1a969e0 R14: 0000000000000000 R15: ffffba77c793d000
[  +0.000002] FS:  00007f81c54f8700(0000) GS:ffff95f473c00000(0000) knlGS:0000000000000000
[  +0.000002] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  +0.000001] CR2: 00000000e1042000 CR3: 000000013f1c4000 CR4: 00000000000426f0
[  +0.000002] Call Trace:
[  +0.000030]  SUPR0FpuBegin+0x13/0x20 [vboxdrv]
[  +0.000006]  ? up+0x12/0x50
[  +0.000004]  ? irq_exit_rcu+0x3e/0xa0
[  +0.000002]  ? sysvec_apic_timer_interrupt+0x34/0x80
[  +0.000014]  ? VBoxHost_RTThreadCtxHookEnable+0x32/0x40 [vboxdrv]
[  +0.000003]  ? update_load_avg+0x7e/0x5c0
[  +0.000012]  ? supdrvIOCtlFast+0x58/0xb0 [vboxdrv]
[  +0.000011]  ? VBoxDrvLinuxIOCtl_7_0_12+0x57/0x230 [vboxdrv]
[  +0.000003]  ? __schedule+0x2c6/0x770
[  +0.000003]  ? __x64_sys_ioctl+0x84/0xc0
[  +0.000003]  ? do_syscall_64+0x33/0x80
[  +0.000002]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  +0.000003] ---[ end trace 1be0adc72d562556 ]---

Can anyone here give me some idea as to what could be causing this?
ie: what all this means.

Thanks in advance.

Best,

A.

Last edited by Altoid (2023-11-27 15:09:31)

Offline

#2 2023-11-27 15:44:32

Altoid
Member
Registered: 2017-05-07
Posts: 1,366  

Re: dmesg printout when starting VirtualBox VM

Hello:

Altoid wrote:

... anyone here give me some idea as to what could be causing this?
ie: what all this means.

Hmm ....
Maybe with some additional information?

For the sake of clarity/brevity I will skip the long story:

1.
Discovered the problem and rolled back to a VM snapshot from 30 days
ago, the oldest one I have.

Concurrently, rolled back to VBox (7.0.6) along with its
GuestAdditions 7.0.6. 

I thought that it would rule out (?) a VBox update or some corruption
in the XPSP3 VM as everything happened way after that date.   

At least I did not notice it as I do not use the XP VM often.

Problem did *not* go away.

2.
Removed VBox 7.0.6 / GuestAdditions 7.0.6, reinstalled the latest
available (7.0.12) along with GuestAdditions and the Extension Pack
which was missing.

Problem did *not* go away.

3.
Went back to the last snapshot and tried to fix things by mucking
around the XPSP3 installation but only managed to screw it up even
more.

The net result being that it is now on a 'black screen select how to
boot' and 'blue screen with whatever' loop.

4.
I attempted to add a new XP VM using three or four of the
downloadable XP isos I found on the web and was able to install one
of them as a VM.

Problem did *not* go away and shutdown does not work.
Not even shutting down X via ctrl+backspace.
Have to reboot my box.

TL;DR

The problem exists whether I use VirtualBox 7.06 or 7.0.12, with a
recovered version of the VM or the latest one.

Installing a new XPSP3 VM, whether in VirtualBox 7.0.6 or 7.0.12,
complete with GA+EP does not solve the problem.

In all cases, disconnecting the host from the web (cable and all)
does not solve the problem so phoning home does not seem to be a
posible cause.

This is (part of) what I get in a rolling dmesg screen:

------------[ cut here ]------------
--- snip ---

WARNING: CPU: 0 PID: 16511 at arch/x86/kernel/fpu/core.c:129 
kernel_fpu_begin_mask+0xc9/0xe0
--- snip ---
Call Trace:
[  +0.000031]  SUPR0FpuBegin+0x13/0x20 [vboxdrv]
[  +0.000006]  ? up+0x12/0x50
[  +0.000014]  ? VBoxHost_RTThreadCtxHookEnable+0x32/0x40 [vboxdrv]
[  +0.000012]  ? supdrvIOCtl+0xc5e/0x3650 [vboxdrv]
[  +0.000013]  ? rtR0MemAllocEx+0x57/0xd0 [vboxdrv]
[  +0.000012]  ? supdrvIOCtlFast+0x58/0xb0 [vboxdrv]
[  +0.000011]  ? VBoxDrvLinuxIOCtl_7_0_12+0x57/0x230 [vboxdrv]
[  +0.000003]  ? __x64_sys_ioctl+0x84/0xc0
[  +0.000004]  ? do_syscall_64+0x33/0x80
[  +0.000003]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  +0.000002] ---[ end trace 2d76295c57757cc8 ]---

The warning is always the same.
ie:
at arch/x86/kernel/fpu/core.c:129 kernel_fpu_begin_mask+0xc9/0xe0

The call trace starts with the same line.
ie:
SUPR0FpuBegin+0x13/0x20 [vboxdrv]

And it is all about the same module:
ie:

? VBoxHost_RTThreadCtxHookEnable+0x32/0x40 [vboxdrv]
? VBoxHost_RTThreadCtxHookEnable+0x32/0x40 [vboxdrv]
? supdrvIOCtlFast+0x58/0xb0 [vboxdrv]
? VBoxDrvLinuxIOCtl_7_0_12+0x57/0x230 [vboxdrv]
~$ lsmod | grep vbox
vboxnetadp             28672  0
vboxnetflt             32768  1
vboxdrv               589824  4 vboxnetadp,vboxnetflt   # <- this one
~$ 

One of the important packages updated lately was linux-kbuild.
ie: 5.10.179-5~deb10u1 to 5.10.197-1~deb10u1

I understand that it is closely related to module handling by the kernel.

If anyone has a clue as to what the trace in dmesg indicates, I'm
all ears.

Thanks in advance.

Best.

A.

Offline

Board footer