On Tue, Feb 09, 2021 at 09:01:23PM +0100, Emmanuel Kasper wrote:
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 kernelEmmanuel
Tried with a fresh update of debian/testing64 the result is not that different. It hangs after shutdown and restart. See also the screenshot taken from the GUI. The issue is again the same: the box is created with the VboxVGA instead of the suggested VMSVGA.
[...] VirtualBox Guest Additions: Building the modules for kernel 5.10.0-3-amd64. update-initramfs: Generating /boot/initrd.img-5.10.0-3-amd64VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
An error occurred during installation of VirtualBox Guest Additions 6.1.18. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
Unmounting Virtualbox Guest Additions ISO from: /mnt
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 6.0.0
VBoxService inside the vm claims: 6.1.18
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 6.0.0
VBoxService inside the vm claims: 6.1.18
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 6.0.0
VBoxService inside the vm claims: 6.1.18
Going on, assuming VBoxService is correct...
Restarting VM to apply changes...
==> testing: Attempting graceful shutdown of VM...
==> testing: Booting VM...
==> testing: Waiting for machine to boot. This may take a few minutes...
==> testing: Checking for guest additions in VM...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
On 2/9/21 11:16 AM, Francesco P. Lovergine wrote:Package: cloud.debian.org Severity: normalIn 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
-- Francesco P. Lovergine
Attachment:
VirtualBox_testing_10_02_2021_09_29_31.png
Description: PNG image
