You are not logged in.
@EndUserOnly you can see the changes for libvrt 6.6 and 6.7 on https://libvirt.org/news.html
Offline
What fixed it for me was switching from Bridged Adapter to NAT.
Offline
VirtualBox 6.1.14 has just been released. I think that all problems were solved.
ChangeLog:
VirtualBox 6.1.14 (released September 04 2020)
This is a maintenance release. The following items were fixed and/or added:
GUI: Fixes file name changes in the File location field when creating Virtual Hard Disk (bug #19286)
VMM: Fixed running VMs which failed to start with VERR_NEM_MISSING_KERNEL_API_2 when Hyper-V is used (bug #19779 and #19804)
Audio: fix regression in HDA emulation introduced in 6.1.0
macOS host: Fixed webcam passthrough and audio input on Mojave and newer by requesting authorization from the user (bug #19758)
macOS host: VBoxHeadless no longer able to start VMs (6.1.4/6.0.18 regression; bug #19706)
Windows host: Fixes in serial port implementation
Shared Clipboard: Fixed a potential crash when copying HTML data (6.1.2 regression; bug #19226)
Linux host and guest: Linux kernel version 5.8 support
EFI: Fixed reading ISO9660 filesystems on attached media (6.1.0 regression; bug #19682)
EFI: Support booting from drives attached to the LsiLogic SCSI and SAS controller emulations
Offline
I can confirm the freeze is gone, although started a little slow (I guess it was redetecting stuff).
Kernel 5.8.5-arch1-1
Virtualbox 6.1.12 r139181
Last edited by Joel (2020-09-05 03:32:36)
* PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with xfce4.
* Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with xfce4.
* AUR contributor.
Offline
VirtualBox 6.1.14 has just been released. I think that all problems were solved.
Anyone tested 6.1.14 yet? Still waiting for update.
@Joel 6.1.12 still not working for me. And this is with 5.8.6 kernel.
Offline
Just wanted to share my experience with an issue that hopefully will be resolved on the upcoming 6.1.14 version.
Others have said that is somehow related with USB. Well, my guest OS is a Debian 10 with no USB support, mouse or desktop environment. Just a headless machine I connect to through ssh. Boot is always fine and I can even do things for a while but I noticed that the bug was triggered a few times the moment I switch virtual desktops on the host using a keyboard shortcut. Last time it happened also with both guest OS window and host Chromium browser in the same virtual desktop but right after clicking on a browser tab.
This is just pure guessing but looks like the reason could be a dead lock between guest and host competing for an input device.
Offline
VirtualBox 6.1.14 has just been released. I think that all problems were solved.
Anyone tested 6.1.14 yet? Still waiting for update.
[...]
I was among the group which could get this fixed by disabling bridged networking, and for me, then the above mentioned update fixed it for me(AURs virtualbox-bin), so not need disable that anymore(or downgrade packages, as I just did instead). You wasen't in that group unfortunetly, if memory not decieves me, so cannot tell if also will fix your laptop, unfortunetly.
Thanks for ketting us know about the update, lucas.teles
Last edited by mhertz (2020-09-05 19:19:27)
Offline
@mhertz Thanks for pointing this out. I might as well wait for the proper virtualbox update. The package has been flagged out of date so I assume it will be out soon.
Good to know this fixes things.
Offline
You're welcome
@all, not important, but just wanted to add that an arch VM didn't crash(/hang) on the virtualbox from the repo(only win10's did, I tested 2 different with same result), though still something going on OS-independant, as even though the mouse was locked in the arch VM, then I couldn't use key-combo's e.g. couldn't open a terminal or dmenu prompt in my WM, and was picked up by host instead, despite as said, locked mouse/focus in VM. Wasen't fixed by using NAT, llike the windows issue. Fixed also in new version from AUR(virtualbox-bin).
Last edited by mhertz (2020-09-05 23:06:21)
Offline
https://www.virtualbox.org/wiki/Changelog
Linux host and guest: Linux kernel version 5.8 support
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
I want to thank everyone who spent time for this thread.
With the updated Virtualbox (6.1.14) and Extention Pack (6.1.14) we have support for the 5.8.x kernel and it seems everything
is working as intended.
This thread must be marked as SOLVED, as the solution is ... updating the Virtualbox packages.
Thanks again.
Last edited by pavlosdec (2020-09-07 21:45:29)
Offline
You can mark first post as [SOLVED] yourself as you are OP.
https://bbs.archlinux.org/viewtopic.php?id=130309
Please mark solved threads as [SOLVED]
Marking threads as [SOLVED], after a solution has been found will help others to find an expedient solution for their own issues. Please be considerate and mark those threads when an answer is found.
Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.
Offline
@amish
I tried that and I couldn't add anything to the title. Then I realized that the title had the maximum number of characters...
OK, it is marked as solved!
Offline
I want to thank everyone who spent time for this thread.
With the updated Virtualbox (6.1.14) and Extention Pack (6.1.14) we have support for the 5.8.x kernel and it seems everything
is working as intended.
This thread must be marked as SOLVED, as the solution is ... updating the Virtualbox packages.Thanks again.
Just wanted to add that I didn't needed any extensions-packs here, only the v6.1.14 virtualbox, which I just now reverted from AUR to community-repo version, and all well Granted you need the extension pack if using USB 1.1+ or other propriotary features etc. Thanks yourself for making the thread/addressing the issue!
Offline
Great to hear that it is solved now. Thank you very much!
(Virtualbox works for me again without freeze now)
Offline
Can confirm the freezing issue is fixed. I had to switch to LTS and today switched back to default kernel after seeing VB update.
Last edited by r2d2 (2020-09-10 05:17:59)
Offline
Yeah, well - that is all fine and dandy, but for me - the poor performance makes Virtual Box a non-candidate on this particular Arch Linux build. I remember it well on Debian, smooth as a baby's bottom. Of course everything on Debian was stable, not rolling. Fortunately, I found this out during a time when I did not actually need VB (I have a Windows system right beside me). I also noted that there was at least one Debian build that was posted here with a problem. For me, if I need VB I'm going dual-boot with Debian. Again, I thank the developers for all that they do.
Offline
Hey guys, I know the thread is solved and kind of closed, but VB is working again with the new kernel, but I'm noticing a bit of performance lost for what it was before the problem. Anyone feels the same?
Also, anyone here that uses Qemu/libvirt instead of VB, that has a better performance machine? I would like to change to Qemu/libvirt, but tried in the past and cannot get a good performance like on VB.
Offline
You accidentally hit Report instead of Post brainfucksec...
QEMU offers definitely better performance but it is a bit more difficult to configure than VirtualBox. Anyway, after this big problem with the Kernel I definitely switched to QEMU with virt-manager and I feel very good.
Offline
QEMU offers definitely better performance but it is a bit more difficult to configure than VirtualBox. Anyway, after this big problem with the Kernel I definitely switched to QEMU with virt-manager and I feel very good.
Do you have win10 on QEMU. Can you share your configurations or some guide you follow? I would love to make the switch too.
Offline
Questionable if QEMU is already fixed. It did suffer from the same problem indeed. QEMU hasn't been updated yet but the kernel and libvirt have been. Depends on where the bug actually is in. I haven't tested it yet.
Do you have win10 on QEMU. Can you share your configurations or some guide you follow? I would love to make the switch too.
There is a setup wizard in 'virt-manager' that should guide you. Virt-Manager is somewhat weird regarding storage pools and network devices. They never are properly started or shut down when opening/closing virt-manager here but once you get over it its easy.
Wiki: https://wiki.archlinux.org/index.php/libvirt
Last edited by Maniaxx (2020-09-26 20:02:30)
sys2064
Offline
I solved the problem by setting the chipset to ICH9 and eliminating the extension pack.
Thanks, It's work.
Also, i switched from NAT to Bridged Adapter.
Offline