Virtualbox 6.1.12-4 fails

I wonder whether it’s related to CPU - it’s running fine on my Ryzen-based laptop, no freezes or anything.

@jonathon
How can i install the the development version of virtual-box. I have downloaded the run file.

Edit: VirtualBox-6.1.97-139689-Linux_amd64.run

That’s not something I want to go through… :cold_sweat:

Packages or bust.

1 Like

Never mind then. I already have it installed. Not sure it’s going to work anyway.

Edit: It flatlines like the rest! :rofl:

Screenshot_2020-08-15_16-47-03

1 Like

I updated to 5.8.1

[roger@lenovo ~]$ uname -a
Linux lenovo 5t.8.1-arch1-1 #1 SMP PREEMPT Wed, 12 Aug 2020 18:50:43 +0000 x86_64 GNU/Linux

I have this configuration
installés
and still gets this error

w10

I also obtained an error when I switched to virtualbox-host-modules-arch instead of virtualbox-host-dkms

I now have Windows10 VM up and running.
I switched back to virtualbox-host-modules-arch 6.1.12.9 and enabled USB 1.1. Then it worked. So this problem may be related to USB controller?

No expertise here - but the new kernel (5.8) has new USB 3.0/3.1 stuff in it… possible connection?

You have downgraded your VirtualBox packages but not the extension pack - the error is saying that the extension pack is too new for your version of VirtualBox.

Given the current repo packages/state should work, I’d try that (then fiddle with USB if it’s not working).

2 Likes

I just followed a post from thc on the arch forums and was up and running in seconds.
Had a few kernel updates since and everything running as expected.



I found the source of the problem.

I looked into the details of the package virtualbox. 6.1.12-4 is a patch for the upcoming 5.8 kernel:

https://github.com/archlinux/svntogit-c … d9db127101

Right there is stated "Use the extension pack 6.1.13.139853 if required...". (This version is still a "testcase" and not easy to find)

Either use the AUR package "virtualbox-ext-oracle" or download it here:
https://www.virtualbox.org/download/tes … ox-extpack

I presume this problem will finally vanish with kernel 5.8/virtualbox 6.1.13.

https://bbs.archlinux.org/viewtopic.php?pid=1920818#p1920818

3 Likes

This is going to be my rant on the virtualbox failing. All along i have been having freezing problems trying to download endeavour mostly. It freezes online either at verifying the keyserver stage or during downloading. I’ve been messing around with this for a long time and yes there has been the issue with virtualbox not starting because of the packages but this has not been my issue mostly.

Because of the freezing i switched to vboxvga again to try and I am able to install other distros but not from the online Endeavour site. Virtualbox is working but i cannot download from Endeavour without it freezing during the downloads. Something isn’t right! I don’t know what the problem is.

Screenshot_2020-08-16_10-40-38

Screenshot_2020-08-16_10-42-45

Edit: Frozen right here again!

Screenshot_2020-08-16_11-02-48

2 Likes

For what it’s worth - I installed EndeavourOS in a VM (online install) just a short while ago; it took forever. The installer stayed at 23% for a very long time, then at 50% for an equally long time, and finally at something like 85% for a very long time.

But, in the end, it did install.

I used VBoxSVGA with 256mb of RAM for graphics.

2 Likes

Mine is frozen …you can tell the difference. It’s not just waiting it’s actually locked up.

Edit: I used to use VBoxSVGA and i just switched back to vboxvga and i don’t really see much difference. My main concern is i get full screen because i don’t run vm’s in boxes.

1 Like

@ricklinux
I just ran another install of EOS in virtualbox, I get a long, long pause at the same spot you are stuck at … even to the point that I get two lines in the terminal output showing the slides advancing in the GUI. The next step that pops up is a key server message referring to a server with zimmerman in the name (sorry, I couldn’t catch it all as things went by pretty quick).

My main point is, that it seems like you are getting stuck somewhere right before a keyserver call … not sure if that’s helpful, but it’s an observation from doing more installs on my side.

2 Likes

This would make sense - it’s not VirtualBox freezing, it’s the installation process hanging at refreshing/obtaining the keys.

2 Likes

That’s what I’m alluding to that it’s frozen because of a network issue related to the server or keys i don’t know. But, i probably have the fastest internet of anyone on this forum. So i know when there is an issue. I just can’t get a handle on it. There have been issues with virtualbox updates and then the new kernel, but i have had virtualbox working in between all this and then not working again but i have it working with the following on the 5.8.1 kernel. I have installed Mint, MX, Manjaro, Open Suse, Ubuntu & PopOS with no issues. Using VBoxSvga as that isn’t causing the freezing. It’s just locked when it gets to downloading Endeavour online. Whether it’s related to the keys or whatever is out of my hands. I’m just trying to point out the issue.

[ricklinux@eos-xfce ~]$ pacman -Qs | grep virtualbox
local/virtualbox 6.1.12-4
local/virtualbox-ext-oracle 6.1.13.139853-1
local/virtualbox-guest-iso 6.1.12-1
local/virtualbox-host-modules-arch 6.1.12-9
[ricklinux@eos-xfce ~]$ 
1 Like

Seeing all this makes me perplexed as to why I had no issues running a Win10 VM on the 5.7.9 kernel with the -4 version and still have no issues on 5.8.1. Could it be something outside of virtualbox itself?

1 Like

@ricklinux - I still haven’t run into issues building VMs with the EndeavourOS install … but a funny thing happened this evening… I created a brand new VM to try a vanilla Arch install … and it got stuck!

Screenshot from 2020-08-16 21-11-20

I am not sure where to go with this, but the following lines captured from journalctl are related. They occurred at the same time my arch linux install hung, and there wasn’t much else running on my laptop at the time.

Summary
Aug 16 20:23:47 ASUSEndeavour kernel: BUG: kernel NULL pointer dereference, address: 0000000000000044
Aug 16 20:23:47 ASUSEndeavour kernel: #PF: supervisor write access in kernel mode
Aug 16 20:23:47 ASUSEndeavour kernel: #PF: error_code(0x0002) - not-present page
Aug 16 20:23:47 ASUSEndeavour kernel: PGD 0 P4D 0 
Aug 16 20:23:47 ASUSEndeavour kernel: Oops: 0002 [#1] PREEMPT SMP PTI
Aug 16 20:23:47 ASUSEndeavour kernel: CPU: 2 PID: 24829 Comm: EMT-3 Tainted: P           OE     5.8.1-arch1-1 #1
Aug 16 20:23:47 ASUSEndeavour kernel: Hardware name: ASUSTeK COMPUTER INC. UX461UN/UX461UN, BIOS UX461UN.317 08/02/2019
Aug 16 20:23:47 ASUSEndeavour kernel: RIP: 0010:0xffff9cbd44f4b8a9
Aug 16 20:23:47 ASUSEndeavour kernel: Code: 49 01 f7 4c 89 7d d0 4d 85 ed 0f 84 d8 01 00 00 4d 85 ff 0f 84 7c 01 00 00 41 89 c7 45 29 e7 41 29 c4 45 89 7d 28 48 8b 45 d0 <44> 89 60 2c 48 c7 46 28 00>
Aug 16 20:23:47 ASUSEndeavour kernel: RSP: 0018:ffff9cbd4339f750 EFLAGS: 00010206
Aug 16 20:23:47 ASUSEndeavour kernel: RAX: 0000000000000018 RBX: ffff9cbd464527a0 RCX: 0000000000000002
Aug 16 20:23:47 ASUSEndeavour kernel: RDX: ffff9cbd44f7a52c RSI: ffff9cbd46452780 RDI: ffff9cbd46409c70
Aug 16 20:23:47 ASUSEndeavour kernel: RBP: ffff9cbd4339f778 R08: 0000000000000001 R09: 0000000000000008
Aug 16 20:23:47 ASUSEndeavour kernel: R10: 0000000000000006 R11: 0000000000000003 R12: 0000000000000000
Aug 16 20:23:47 ASUSEndeavour kernel: R13: ffff9cbd437283d0 R14: 000000000000000a R15: ffff9cbd46450230
Aug 16 20:23:47 ASUSEndeavour kernel: FS:  00007fa79ede2700(0000) GS:ffff97509ec80000(0000) knlGS:0000000000000000
Aug 16 20:23:47 ASUSEndeavour kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 16 20:23:47 ASUSEndeavour kernel: CR2: 0000000000000044 CR3: 000000000231a005 CR4: 00000000003626e0
Aug 16 20:23:47 ASUSEndeavour kernel: Call Trace:
Aug 16 20:23:47 ASUSEndeavour kernel:  ? update_load_avg+0x7e/0x660
Aug 16 20:23:47 ASUSEndeavour kernel:  ? enqueue_entity+0x14e/0x750
Aug 16 20:23:47 ASUSEndeavour kernel:  ? resched_curr+0x20/0xc0
Aug 16 20:23:47 ASUSEndeavour kernel:  ? VBoxHost_RTThreadPreemptRestore+0x17/0x50 [vboxdrv]
Aug 16 20:23:47 ASUSEndeavour kernel:  ? do_vfs_ioctl+0x304/0x6e0
Aug 16 20:23:47 ASUSEndeavour kernel:  ? supdrvIOCtlFast+0x66/0xb0 [vboxdrv]
Aug 16 20:23:47 ASUSEndeavour kernel:  ? VBoxDrvLinuxIOCtl_6_1_12+0x56/0x250 [vboxdrv]
Aug 16 20:23:47 ASUSEndeavour kernel:  ? ksys_ioctl+0x82/0xc0
Aug 16 20:23:47 ASUSEndeavour kernel:  ? __x64_sys_ioctl+0x16/0x20
Aug 16 20:23:47 ASUSEndeavour kernel:  ? do_syscall_64+0x44/0x70
Aug 16 20:23:47 ASUSEndeavour kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 16 20:23:47 ASUSEndeavour kernel: Modules linked in: exfat fuse hidp ccm rfcomm snd_hda_codec_hdmi cmac algif_hash algif_skcipher af_alg bnep uvcvideo btusb btrtl videobuf2_vmalloc btbcm videobu>
Aug 16 20:23:47 ASUSEndeavour kernel:  asus_nb_wmi crc32_pclmul asus_wmi snd_hda_core ghash_clmulni_intel wmi_bmof sparse_keymap mxm_wmi aesni_intel iwlwifi snd_hwdep drm_kms_helper crypto_simd gpio>
Aug 16 20:23:47 ASUSEndeavour kernel: CR2: 0000000000000044
Aug 16 20:23:47 ASUSEndeavour kernel: ---[ end trace e1c500430a09d09c ]---
Aug 16 20:23:47 ASUSEndeavour kernel: RIP: 0010:0xffff9cbd44f4b8a9
Aug 16 20:23:47 ASUSEndeavour kernel: Code: 49 01 f7 4c 89 7d d0 4d 85 ed 0f 84 d8 01 00 00 4d 85 ff 0f 84 7c 01 00 00 41 89 c7 45 29 e7 41 29 c4 45 89 7d 28 48 8b 45 d0 <44> 89 60 2c 48 c7 46 28 00>
Aug 16 20:23:47 ASUSEndeavour kernel: RSP: 0018:ffff9cbd4339f750 EFLAGS: 00010206
Aug 16 20:23:47 ASUSEndeavour kernel: RAX: 0000000000000018 RBX: ffff9cbd464527a0 RCX: 0000000000000002
Aug 16 20:23:47 ASUSEndeavour kernel: RDX: ffff9cbd44f7a52c RSI: ffff9cbd46452780 RDI: ffff9cbd46409c70
Aug 16 20:23:47 ASUSEndeavour kernel: RBP: ffff9cbd4339f778 R08: 0000000000000001 R09: 0000000000000008
Aug 16 20:23:47 ASUSEndeavour kernel: R10: 0000000000000006 R11: 0000000000000003 R12: 0000000000000000
Aug 16 20:23:47 ASUSEndeavour kernel: R13: ffff9cbd437283d0 R14: 000000000000000a R15: ffff9cbd46450230
Aug 16 20:23:47 ASUSEndeavour kernel: FS:  00007fa79ede2700(0000) GS:ffff97509ec80000(0000) knlGS:0000000000000000
Aug 16 20:23:47 ASUSEndeavour kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 16 20:23:47 ASUSEndeavour kernel: CR2: 0000000000000044 CR3: 000000000231a005 CR4: 00000000003626e0

Oddly, while this session was stuck I created another VM and installed EOS using online without issue?

I am baffled, but wanted to at least let you know that I was able to reproduce what you have been experiencing.

1 Like

It seems that it is only Arch based installs that are a problem. I installed 6 other non Arch based distro’s without any problems. Every time I try an Endeavour install it stops responding during the start to download or during. I’ve done enough messing with it that I have come to the conclusion that VirtualBox will need some type of updates to work properly on Arch.

1 Like

No virtualbox host problems here on linux 5.8, linux-zen 5.8 or linux-lts 5.4.

local/virtualbox 6.1.12-4
local/virtualbox-ext-oracle 6.1.13.139853-1
local/virtualbox-guest-iso 6.1.12-1
local/virtualbox-host-dkms 6.1.12-4

I did have an EndeavourOS guest VM freeze up on me downloading files for an update, so I changed to the linux-lts kernel in the VM and no more issues since.

Any issues are probably caused by running kernel 5.8 in a guest VM, which is not really a surprise as it was just released. This should be fixed in Virtualbox 6.14.

1 Like

No, I did not downgrade anything. Just following normal updates and selecting usb 1.1.

1 Like