Virtualbox 6.1.12-4 fails

I just had a Windows 10 VM crash on me. I’m compiling linux-zen 5.8.2 now and will test.

A complete crash or just the VM itself?
AMD graphics?

So it’s working as expected? :wink:

6 Likes

The VM.

Yes, amdgpu.

Hmm… once I removed the ProjectC scheduler from my kernel, the Win10 VM was stable again, could sustain over one hour of streaming in browser. No further errors in the logs.
But you don’t seem to be using that scheduler, and using VBoxSVGA in the guest?

Looks like we’re not the only ones fighting this:

https://bbs.archlinux.org/viewtopic.php?id=258217

https://www.virtualbox.org/ticket/19644

Hopefully this means something good will happen soon.

2 Likes

pitty my virt-manager network doesnot work , so now back to virtualbox but not full extentions lol

just disabled usb to use… busy installing now…

Strange? I have it working on mine but virtual-box doesn’t on any Arch install.

mine just hung from what i dont know, when i made de profile it complain with usb thing, disable usb works…

Hmm i never tried disabling usb? How do you do that in virtual-box?

you got to the setting of a profile and left you see usb. just uncheck it…
if you make a profile to setup…

1 Like

5.8.2 didn’t make any difference, but then it might just be SPSS being weird. I open SPSS, click the Edit menu bar item, Windows VM crashes. I don’t really need SPSS anyway, so… :man_shrugging:

I tried with USB disabled and an EndeavourOS install just freezes virtualbox. It hasn’t got any better for me. I am using virt-manager Qemu.

I been switxhed to wifi network dont work, its a pity lol

Hi

Even with the latest update of this morning,

[2020-08-28T10:08:39+0800] [ALPM] upgraded virtualbox-host-modules-arch (6.1.12-12 -> 6.1.12-13)
[2020-08-28T10:08:39+0800] [ALPM] upgraded python2-sip-pyqt5 (4.19.23-1 -> 4.19.24-1)
[2020-08-28T10:08:39+0800] [ALPM] upgraded python-sip (4.19.23-1 -> 4.19.24-1)
[2020-08-28T10:08:39+0800] [ALPM] upgraded nvidia (450.66-14 -> 450.66-15)
[2020-08-28T10:08:39+0800] [ALPM] upgraded md4c (0.4.4-1 -> 0.4.5-1)
[2020-08-28T10:08:39+0800] [ALPM] upgraded mathjax2 (2.7.8-1 -> 2.7.9-1)
[2020-08-28T10:08:39+0800] [ALPM] upgraded mathjax (3.0.5-1 -> 3.1.0-1)
[2020-08-28T10:08:39+0800] [ALPM] upgraded linux-headers (5.8.3.arch1-1 -> 5.8.4.arch1-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded libde265 (1.0.5-2 -> 1.0.6-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded intel-gmmlib (20.2.4-1 -> 20.2.5-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded gettext (0.20.2-1 -> 0.21-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded geoip-database (20200721-1 -> 20200825-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded f2fs-tools (1.13.0-2 -> 1.14.0-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded cups-filters (1.28.0-1 -> 1.28.1-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded imagemagick (7.0.10.26-1 -> 7.0.10.28-1)
[2020-08-28T10:08:36+0800] [ALPM] upgraded bbswitch (0.8-342 -> 0.8-343)
[2020-08-28T10:08:36+0800] [ALPM] upgraded linux (5.8.3.arch1-1 -> 5.8.4.arch1-1)

I still have the same error message about “usb-xhci” when I try to launch the VM.
During the update, I got the following warning
possibly missing firmware for module xhci_pci

For the time being, I can only use VB with the setting usb 1.1.

I gave up on virtual-box for the time being and am using virt-manager qemu.

The ‘error’ message you get - does it actually say it is a ‘warning’ instead? If so, it happens with all Arch-based systems, and is completely ignorable, as are the ones about old RAID hardware firmware that you see when integrating new kernel versions after update.

Here it works without problems …
VB

Have you tried installing EndeavourOS lately with it? I can install anything that isn’t Arch based.

Yes of course, you can see it in the capture!