On Thu, May 11, 2023 at 07:55:08PM +0200, Dick Visser wrote: > "works for me" > > vagrant@bullseye:~$ uname -a > Linux bullseye 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 > GNU/Linux > > dick.visser@GA0267 mainstream_distros$ vagrant -v > Vagrant 2.3.4 thanks fo rchecking > > This is on an intel mac with virtualbox Version 7.0.8 r156879 (Qt5.15.2) Right, I omitted important info. I used the libvirt provider on my stable Debian: libvirt-daemon 7.0.0-3+deb11u2 vagrant 2.2.14+dfsg-2 vagrant-libvirt 0.7.0-1~bpo11+1 > On Thu, 11 May 2023 at 18:05, Domenico Andreoli <cavok@debian.org> wrote: > > > Hi, > > > > I'm having issues in booting latest debian/bullseye64 Vagrant box. > > > > I use that Vagrant box regularly, if I pick v11.20221219.1 (the > > previous version) it still works but if instead I go for the latest > > (v11.20230501.1) Vagrant sits there waiting for the box to show up on > > the network. > > > > Also upgrading the previous box with apt results in a non-booting system, > > it looks like that the latest kernel is somewhat broken. It's 100% > > reproducible on my side. > > > > Am I the only one? Could anybody else double check? > > > > Is there anything I can do to investigate and get a bootlog? > > > > Thanks, > > Dom > > > > -- > > rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 > > ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05 > > -- rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
Attachment:
signature.asc
Description: PGP signature