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

Bug#979228: marked as done (cloud.debian.org: Vagrant box debian/buster64 with provider libvirt: ,,error: invalid arch-independent ELF magic.")

Your message dated Tue, 26 Jan 2021 15:58:42 +0100
with message-id <c11a8433-e7c2-cc40-4636-1852b921fa44@debian.org>
and subject line 
has caused the Debian Bug report #979228,
regarding cloud.debian.org: Vagrant box debian/buster64 with provider libvirt: ,,error: invalid arch-independent ELF magic."
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

979228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979228
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cloud.debian.org
Severity: normal
Tags: upstream

Using https://app.vagrantup.com/debian/boxes/buster64 with provider libvirt
enters grub resuce
wit the following error message:

Booting from Hard Disk...
error: invalid arch-independent ELF magic.
Entering rescue mode...
grub resuce>

Host is Debian Buster:
#1 SMP Debian 4.19.160-2 (2020-11-28)

Package: qemu
Version: 1:3.1+dfsg-8+deb10u8

vagrant init debian/buster64
vagrant up --provider libvirt

Remark: it works fine with

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
according to bug submitter it was a problem in his local setup, closing

--- End Message ---

Reply to: