Hi Frankie
Thanks for you interest for the Vagrant Boxes.
Can you reproduce the issue with
https://app.vagrantup.com/debian/boxes/testing64 ?
contrib boxes are going the way of the doodo for bullseyes, as the dkms
kernel drivers needed for the guest extensions are now in the mainline
kernel
Emmanuel
On 2/9/21 11:16 AM, Francesco P. Lovergine wrote:
Package: cloud.debian.org
Severity: normal
In order to replicate the issue, just up with a current image
(20200607.1). Runnig the VM causes a kernel panic, as in the attached
screenshot
Moving from VboxSVGA to VboxMSVGA solves the issue. That happens only
after upgrading to current bullseye 5.10 kernel, instead of the
historical 5.6.
Virtualbox in use is 6.1.18.
-- System Information:
Debian Release: 10.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-14-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
You know an upstream is nice when they even accept m68k patches.
- John Paul Adrian Glaubitz, Debian OpenJDK maintainer
