[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bullseye64 Vagrant box does not boot



On Tue, May 16, 2023 at 12:08:06PM +0200, Domenico Andreoli wrote:
> On Fri, May 12, 2023 at 09:56:34PM +0200, Lucas Nussbaum wrote:
> > Hi,
> 
> Hi,
> 
> > On 11/05/23 at 20:13 +0200, Domenico Andreoli wrote:
> > > 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
> > 
> > I maintain the Vagrant images.
> > 
> > It also works for me in the regression tests I'm running on salsa:
> > https://salsa.debian.org/cloud-team/debian-vagrant-images/-/jobs/4206692
> > 
> > What is the host kernel version?
> 
> It was 5.10.178-3, now I updated it to 5.10.179-1.
> 
> > Could you try with vagrant-libvirt from stable, not stable-backports?
> 
> Yes of course.
> 
> Now vagrant-libvirt is 0.3.0-1. I also installed all the recommends,
> previously most were left out. No other bpo packages were/are installed.
> 
> Same result, still not booting.

I side-stepped the issue by upgradig the host to Bookworm. Everything
works again.

Thanks,
Domenico

Attachment: signature.asc
Description: PGP signature


Reply to: