:: Re: [DNG] dmesg printout when start…
Góra strony
Delete this message
Reply to this message
Autor: Arnt Karlsen
Data:  
Dla: dng
Temat: Re: [DNG] dmesg printout when starting VirtualBox VM
On Sat, 25 Nov 2023 13:00:16 -0300, altoid wrote in message
<65621A10.21310.51F081@???>:

> Hello:
>
> Caveat:
> Don't kow if this is the *right* place to post this question.
> Please advise / suggest.
>
> ---
>
> After some problems with my XPSP3


...meaning Microsoft Wintendo XP with Service Pack 3?

> 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.


..did it work with earlier versions of VirtualBox?

> 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 but I could not say for sure.


..does it work with the latest version of Debian Sid,
or Red Hat etc systemd based vm guests? Systemd "is
avare of vm hosts" and might be set up to e.g. refuse
booting on non-systemd hosts, but that shouldn't kill
Wintendo XP SP3 boots?

..I'm guessing a new bug in VirtualBox 7.0.12 r159484,
I only found 2 versions of this post:
https://forum.macrium.com/75031/viboot-cant-find-and-Virtualbox-Version-7012-r159484-Qt5152
https://forum.macrium.com/PrintTopic75031.aspx and
your https://dev1galaxy.org/viewtopic.php?id=6170

..wild ass guessing here, my last Wintendo boot-up was
to use Microsoft Internet Exploder to install Debian
Etch (or Lenny?) off http://goodbye-microsoft.com/ on
a 2'nd hand laptop in 2009, AFAIR.

> [code]
> ------------[ cut here ]------------
> [  +0.000012] WARNING: CPU: 1 PID: 15685 at 
> arch/x86/kernel/fpu/core.c:129 kernel_fpu_begin_mask+0xc9/0xe0
> [  +0.000002] Modules linked in: 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 coretemp 
> snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg 
> soundwire_intel uvcvideo soundwire_generic_allocation 
> videobuf2_vmalloc snd_soc_core videobuf2_memops videobuf2_v4l2 
> snd_usb_audio videobuf2_common kvm_intel snd_compress kvm 
> soundwire_cadence snd_usbmidi_lib snd_hda_codec videodev snd_rawmidi 
> irqbypass snd_hda_core snd_seq_device pcspkr nvidia(POE) snd_hwdep mc 
> serio_raw soundwire_bus at24 joydev 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 
> sd_mod t10_pi crc_t10dif crct10dif_generic crct10dif_common 
> hid_generic usbhid hid mptsas ahci xhci_pci libahci mptscsih e1000e 
> i2c_i801 xhci_hcd aic7xxx mptbase ehci_pci scsi_transport_sas 
> uhci_hcd ptp libata
> [  +0.000072]  ehci_hcd scsi_transport_spi i2c_smbus scsi_mod usbcore 
> pps_core usb_common button
> [  +0.000011] CPU: 1 PID: 15685 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.000003] RIP: 0010:kernel_fpu_begin_mask+0xc9/0xe0
> [  +0.000003] Code: c4 10 5b c3 65 8a 05 7e 5f 5e 5d 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:ffffafe80ac87b30 EFLAGS: 00010002
> [  +0.000002] RAX: 0000000080000001 RBX: 0000000000000003 RCX: 
> ffffafe80ac91000
> [  +0.000002] RDX: 0000000000000009 RSI: ffffafe80adb5000 RDI: 
> 0000000000000003
> [  +0.000002] RBP: ffffafe80ac87b50 R08: 0000000000000000 R09: 
> 0000000000000010
> [  +0.000001] R10: ffffafe803ffa000 R11: 0000000000000000 R12: 
> ffffafe80adb5000
> [  +0.000002] R13: ffffafe801b26a28 R14: 0000000000000001 R15: 
> ffffafe80adb5000
> [  +0.000002] FS:  00007f1a874fc700(0000) GS:ffff9c2af3c80000(0000) 
> knlGS:0000000000000000
> [  +0.000002] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [  +0.000002] CR2: 0000000000f00000 CR3: 000000017690c000 CR4: 
> 00000000000426e0
> [  +0.000001] Call Trace:
> [  +0.000037]  SUPR0FpuBegin+0x13/0x20 [vboxdrv]
> [  +0.000006]  ? up+0x12/0x50
> [  +0.000014]  ? VBoxHost_RTThreadCtxHookEnable+0x32/0x40 [vboxdrv]
> [  +0.000002]  ? update_load_avg+0x7e/0x5c0
> [  +0.000013]  ? supdrvIOCtlFast+0x58/0xb0 [vboxdrv]
> [  +0.000011]  ? VBoxDrvLinuxIOCtl_7_0_12+0x57/0x230 [vboxdrv]
> [  +0.000003]  ? __schedule+0x2c6/0x770
> [  +0.000004]  ? __x64_sys_ioctl+0x84/0xc0
> [  +0.000003]  ? do_syscall_64+0x33/0x80
> [  +0.000003]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [  +0.000002] ---[ end trace 23fe43ea240a07e2 ]---
> [/code]

>
> The line "WARNING: CPU:" can vary from *0* to *3*, probably because I
> the CPU is an Intel Q9550.


..try lock down the guest vm to only use 1 or 2 cpus.

> But the rest of the lines are seem to be the same, have not checked
> thoroughly yet.
>
> The affected VM (obviously with *no* web access)


..does it have _any_other_ net access?
Microsoft started to require call-home reporting to
enforce their EULAs sometime in the last 2 decades,
and has gradually gotten more anal about it,
according to people complaining abou Microsoft.

..possible ideas would be try an older version guest
OS that doesn't try to call home on boot-up, or do
vm boot-ups on single use throw-away copies from a
known working backup.

> is only used once
> every so often for the Blackberry sync software and the odd testing
> of hardware such as HDDs and USB sticks with Windows only utilities.
>
> Save for the dmesg printout, seems to be working properly.
>
> I'd appreciate any ideas from the members of the forum.
>
> Thanks in advance.
>
> A.
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>



--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.