VirtualBox Issue after upgrade

t4z3v4r3d

Member


Messages: 79

After Upgrading process from 12.0 to 12.1 : build world and kernel, Vbox is crashing every time started.
No vboxnet0, No debug info, No logs.
Bash:
t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ id
uid=1001(t4z3v4r3d) gid=1001 groups=1001,0(wheel),5(operator),68(dialer),69(network),920(vboxusers)
t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ /usr/local/lib/virtualbox/VirtualBox --debug-command-line --comment ceph-admin-20-25-gui --startvm 44241989-0f2c-4c9d-b3ad-53b378106204 --no-startvm-errormsgbox
Segmentation fault
t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ ifconfig | grep -i vbox
t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ pkg info | grep virtualbox
virtualbox-ose-5.2.34_1        General-purpose full virtualizer for x86 hardware
virtualbox-ose-additions-5.2.34_2 VirtualBox additions for FreeBSD guests
virtualbox-ose-kmod-5.2.34 VirtualBox kernel module for FreeBSD
t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ freebsd-version -uk
12.1-STABLE
12.1-STABLE
Any suggestion ?
 

Paul Floyd

Member

Reaction score: 11
Messages: 70

Same problem here. The wiki does suggest checking that vbox is in your xorg config, which I haven't tried yet.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 8,488
Messages: 32,562

Do the virtualbox kernel modules load? I suspect they're still for 12.0 and will likely fail to load, try rebuilding/reinstalling those.
 
OP
OP
t4z3v4r3d

t4z3v4r3d

Member


Messages: 79

It will be ok with sudo virtualbox


But why ? I Have even no any simple change in my machine just i did mke buildworld and kernel as the regular upgrade.

Code:
t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ kldstat -v | grep -i vb
4    3 0xffffffff82499000    88520 vboxdrv.ko (/boot/modules/vboxdrv.ko)
                  3 vboxdrv
14    1 0xffffffff84021000    2e903 vboxguest.ko (/boot/modules/vboxguest.ko)
                526 pci/vboxguest
19    2 0xffffffff8408e000     2ce0 vboxnetflt.ko (/boot/modules/vboxnetflt.ko)
                532 ng_vboxnetflt
22    1 0xffffffff8409d000     3f30 vboxnetadp.ko (/boot/modules/vboxnetadp.ko)
                534 vboxnetadp
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 8,488
Messages: 32,562

I Have even no any simple change in my machine just i did mke buildworld and kernel as the regular upgrade.
No simple change? You upgraded to a new minor version. Granted this shouldn't be much of an issue but kernel modules can be quite finicky about the exact kernel version they were built for.
 
OP
OP
t4z3v4r3d

t4z3v4r3d

Member


Messages: 79

No simple change? You upgraded to a new minor version. Granted this shouldn't be much of an issue but kernel modules can be quite finicky about the exact kernel version they were built for.
The kernel was upgraded 12.1 and all packages too before. Just upgrading world and after that i did it for all packages again.
So i expected to have a working machine.
 

T-Daemon

Aspiring Daemon

Reaction score: 224
Messages: 594

Check the permissions of the /tmp folder, vbox creates temporary files there. That might explain working with sudo. I had an issue with xorg because some process changed permissions on /tmp.
 
OP
OP
t4z3v4r3d

t4z3v4r3d

Member


Messages: 79


t4z3v4r3d@virtual /usr/home/t4z3v4r3d $ ls -la / | grep tmp
drwxrwxrwt 8 root wheel 896 Mar 25 22:49 tm
 

sgunn

Member

Reaction score: 4
Messages: 28

FWIW I am having the same issue. Did a forced pkg upgrade to reinstall everything, which didn't help.

I am on 12.1-p3.
 

T-Daemon

Aspiring Daemon

Reaction score: 224
Messages: 594

You said no logs, look in ~/.config/VirtualBox, there must be some logs.
 

Paul Floyd

Member

Reaction score: 11
Messages: 70

You said no logs, look in ~/.config/VirtualBox, there must be some logs.
The log does mention that the Guest Additions ISO can't be found. I get the same message on Linux, so it's probably not the cause. Then there is an ACCESSDENIED error, at about the same point that Linux warns that USB is not accessible.

I tried deleting the logs, they don't get regenerated. I also tried enabling USB. No joy. The last things that truss -f outputs are

Code:
69868: openat(AT_FDCWD,"/usr/home/paulf/.config/kdeglobals",O_RDONLY|O_CLOEXEC,00) = 8 (0x8)
69868: fstat(8,{ mode=-rw------- ,inode=805307,size=3701,blksize=4096 }) = 0 (0x0)
69868: fstat(8,{ mode=-rw------- ,inode=805307,size=3701,blksize=4096 }) = 0 (0x0)
69868: fstat(8,{ mode=-rw------- ,inode=805307,size=3701,blksize=4096 }) = 0 (0x0)
69868: read(8,"[$Version]\nupdate_info=filepick"...,16384) = 3701 (0xe75)
69868: read(8,0x80b0dcb8d,12683)                 = 0 (0x0)
69868: mmap(0x0,45056,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 34577829888 (0x80cffd000)
69868: close(8)                                  = 0 (0x0)
69868: fstatat(AT_FDCWD,"/home/paulf/.config/breezerc",0x7fffffff9b80,0x0) ERR#2 'No such file or directory'
69868: fstatat(AT_FDCWD,"/usr/local/etc/xdg/breezerc",0x7fffffff9b80,0x0) ERR#2 'No such file or directory'
69868: fstatat(AT_FDCWD,"/etc/xdg/breezerc",0x7fffffff9b80,0x0) ERR#2 'No such file or directory'
69868: fstatat(AT_FDCWD,"/usr/local/etc/xdg/breezerc",0x7fffffff9b80,0x0) ERR#2 'No such file or directory'
69868: SIGNAL 11 (SIGSEGV) code=SEGV_ACCERR trapno=12 addr=0x803dd2a18
69868: poll({ 3/POLLIN },1,-1)                   ERR#4 'Interrupted system call'
69868: <thread 101211 exited>
69868: process killed, signal = 11 (core dumped)
 

T-Daemon

Aspiring Daemon

Reaction score: 224
Messages: 594

I was hoping there would be a hint in the log. I suppose there is no core dump file in the users home directory, isn't it? I can't reproduce the crash, it runs fine on my system. Here my system info:

amd64
12.1-RELEASE-p3, binary upgrade (12.0-R-p10 -> 12.1-R)
latest package repository
virtualbox-ose-5.2.34_1
virtualbox-ose-kmod-5.2.34
(both packages installed after the system upgrade)
vboxusers group

What I would try is perform a fresh system installation on a spare USB stick, SD card, empty partition, etc., install x11/xorg-minimal, graphics driver, a lightweight wm (x11-wm/twm will do), emulation/virtualbox-ose (-kdm). If the problem persists, open a bug report, if not then a fresh system installation should be considered.
 
OP
OP
t4z3v4r3d

t4z3v4r3d

Member


Messages: 79

In my case it's running by sudo, I did't change perms and/or configs.
It seems problem is some part of new configurations that i don't where it is.
 

Paul Floyd

Member

Reaction score: 11
Messages: 70

In my case, this was a clean install of FreeBSD 12.1. I don't particularly want to have to reinstall the OS - the reason that I want to use VBox is to not have to install more OSes on bare metal.
 

T-Daemon

Aspiring Daemon

Reaction score: 224
Messages: 594

If the problem persists, open a bug report
Someone has already filed a bug report PR 245054 , which has been marked as a duplicate of bug PR 244847, possible fix this weekend (comment #6).

There is a reference in the Makefile of virtualbox-ose to the gcc9 situation (line 35), mentioned in comment #2.

Remains the question why not all systems are affected (mine is not).
 

sgunn

Member

Reaction score: 4
Messages: 28

If this helps, I removed virtualbox, then pulled down a slightly older version from the pkg repository and installed it and it started right up.
 
OP
OP
t4z3v4r3d

t4z3v4r3d

Member


Messages: 79

I have tried to reinstall it by ports but my machine was crashed after reboot, crashed and crashed ....
So i decided to remove it and install it by pkg again.
Again is running by sudo.
Problem is still remaining.
 

T-Daemon

Aspiring Daemon

Reaction score: 224
Messages: 594

I have tried to reinstall it by ports but my machine was crashed after reboot
You could try sgunn's method:
I removed virtualbox, then pulled down a slightly older version from the pkg repository and installed it and it started right up.
In the quarterly pkg repository virtualbox-ose is at version 5.2.34 ( 5.2.34_1 in latest repo), ex.:

fetch http://pkg0.isc.freebsd.org/FreeBSD:12:amd64/quarterly/All/virtualbox-ose-5.2.34.txz
from the same directory:
pkg add virtualbox-ose*

I still haven't figured out why my machine is unaffected.
 
OP
OP
t4z3v4r3d

t4z3v4r3d

Member


Messages: 79

It was ....
I've tried it before ( ~ 10 h )- failed -

Code:
cat /usr/ports/emulators/virtualbox-ose/distinfo
TIMESTAMP = 1571257463
SHA256 (VirtualBox-5.2.34.tar.bz2) = 9abff37330bba46b97aa836bc886397ba9cfb06cb75be5d60ac31f5ae9c2f2e1
SIZE (VirtualBox-5.2.34.tar.bz2) = 118268064
SHA256 (VBoxGuestAdditions_5.2.34.iso) = d1b63891abca37fd78f5c8af1764e10e5754b1eecabd1fcfe7599c29a93ba007
SIZE (VBoxGuestAdditions_5.2.34.iso) = 49661952
 

von_Gaden

Active Member

Reaction score: 17
Messages: 129

I'm sorry to report I am hit by this issue too. I've updated two machines with FreeBSD 12.1-P3 and emulators/virtualbox-ose-nox11 built from source, version 5.2.34_2 and the system started to reboot with kernel panic - "sleeping thread". It *sometimes* works if I start Virtualbox manually.
 
Top