Le 11/02/2021 à 19:26, Francesco P. Lovergine a écrit :
> On Thu, Feb 11, 2021 at 06:15:24PM +0100, Emmanuel Kasper wrote:
>> if testing64 is working so far, including with the kernel of your
>> choice, should we close this bug report ?
>>
>
> Well, in any case I would add a doc note about the
On Thu, Feb 11, 2021 at 06:15:24PM +0100, Emmanuel Kasper wrote:
if testing64 is working so far, including with the kernel of your
choice, should we close this bug report ?
Well, in any case I would add a doc note about the vbox graphic controller
deprecation in 6.1 that could cause issues
if testing64 is working so far, including with the kernel of your
choice, should we close this bug report ?
On Wed, Feb 10, 2021 at 03:21:49PM +0100, Emmanuel Kasper wrote:
This looks good to me. Vagrant/Virtualbox on testing are using the mainline
kernel guest additions, probably with a fake Virtualbox version.
You can see on the guest that the additions come from mainline kernel:
dpkg --search
$ vagrant plugin uninstall vagrant-vbguest
Uninstalling the 'vagrant-vbguest' plugin...
Successfully uninstalled micromachine-3.0.0
Successfully uninstalled vagrant-vbguest-0.29.0
frankie@legolas:~/vagrant
$ vagrant plugin list
No plugins installed.
frankie@legolas:~/vagrant
$ vagrant destroy
On Wed, Feb 10, 2021 at 02:16:47PM +0100, Emmanuel Kasper wrote:
Le 10/02/2021 à 10:22, Francesco P. Lovergine a écrit :
On Wed, Feb 10, 2021 at 10:13:02AM +0100, Francesco P. Lovergine wrote:
Well, it is automagically done by vagrant at provisioning time for
the debian/testing64, maybe
Le 10/02/2021 à 10:22, Francesco P. Lovergine a écrit :
> On Wed, Feb 10, 2021 at 10:13:02AM +0100, Francesco P. Lovergine wrote:
>> Well, it is automagically done by vagrant at provisioning time for
>> the debian/testing64, maybe because the local Virtualbox installation
>> has the extension
On Wed, Feb 10, 2021 at 10:13:02AM +0100, Francesco P. Lovergine wrote:
Well, it is automagically done by vagrant at provisioning time for the
debian/testing64, maybe because the local Virtualbox installation has the
extension installed?
Sorry, I mean the guest additions ISO installed on
On Wed, Feb 10, 2021 at 10:00:47AM +0100, Emmanuel Kasper wrote:
config.vm.provider "virtualbox" do |v|
v.customize ["modifyvm", :id, "--graphicscontroller", "vmsvga"]
end
That could probably considered a vagrant issue. I found that it is a
non-issue with 4.x up to 5.9, but 5.10+ is not
config.vm.provider "virtualbox" do |v|
v.customize ["modifyvm", :id, "--graphicscontroller", "vmsvga"]
end
That could probably considered a vagrant issue. I found that it is a
non-issue with 4.x up to 5.9, but 5.10+ is not compatible with the
default choice. Not sure if the suggested
On Wed, Feb 10, 2021 at 09:37:53AM +0100, Francesco P. Lovergine wrote:
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
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
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
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
14 matches
Mail list logo
