Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bento/ubuntu-22.04 libvirt no longer boots. #1604

Open
skyscooby opened this issue Mar 11, 2025 · 4 comments
Open

bento/ubuntu-22.04 libvirt no longer boots. #1604

skyscooby opened this issue Mar 11, 2025 · 4 comments
Labels
Status: Untriaged An issue that has yet to be triaged.

Comments

@skyscooby
Copy link

skyscooby commented Mar 11, 2025

Version

202502.21.0 - libvirt provider

Environment

Linux - KVM --provider libvirt

vagrant version
Installed Version: 2.4.3
Latest Version: 2.4.3

Scenario

Switching vagrant image from bento/ubuntu-22.04 202309.08.0 to 202502.21.0 results in image no longer booting. Console just shows pre-boot environment trying to boot from hard disk image... kernel doesn't even load

Steps to Reproduce

Vagrant.configure("2") do |config|
  config.vm.box      = "bento/ubuntu-22.04"
  config.vm.box_version = "202502.21.0"
  config.vm.provider "libvirt" do |pv|
    pv.cpus = 4
    pv.memory = 8192
    pv.driver = "kvm"
  end
end
  • Revert the identical Vagrantfile to box_version 202309.08.0 and it boots fine.

Expected Result

New Image should boot.

Actual Result

Nothing happens.. kernel doesn't even boot from SeaBIOS when reviewing the domain console..

Image

@skyscooby skyscooby added the Status: Untriaged An issue that has yet to be triaged. label Mar 11, 2025
@jflowers
Copy link

Same for Centos Stream 10

@Stromweld
Copy link
Collaborator

is this for x86 or arm64 machines?

@nsballmann
Copy link

nsballmann commented Mar 24, 2025

I see this on x86_64.

@skyscooby
Copy link
Author

is this for x86 or arm64 machines?

x86_64 -- as I only have x86 machines so I can't test arm64... we ban Apple here due to the architecture nuisance their M chips have started to cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Untriaged An issue that has yet to be triaged.
Projects
None yet
Development

No branches or pull requests

4 participants