Your message dated Sat, 23 Feb 2019 14:18:12 +0100 with message-id <[email protected]> and subject line Re: xen-utils-3.2-1: Pygrub says "Error: Boot loader didn't return any data!" has caused the Debian Bug report #507020, regarding xen-utils-3.2-1: Pygrub says "Error: Boot loader didn't return any data!" 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 [email protected] immediately.) -- 507020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507020 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return any data". In the xend.log I see: ---- Launching bootloader as ['/usr/lib/xen-3.2-1/bin/pygrub', '--args=root=/dev/sda2 ro console=xvc0 xencons=xvc0', '--output=/var/run/xend/boot/xenbl.21780', '-q', '/dev/volume0/lenny.vandervlis.nl-swap']. ---- Switching the disk statements helps as a workarround, so this work: ---- disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', ] ---- Ian Campbell wrote about this problem: --- This code in /usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py looks suspect disks = [x for x in self.info['vbd_refs'] if self.info['devices'][x][1]['bootable']] if not disks: msg = "Had a bootloader specified, but no disks are bootable" log.error(msg) raise VmError(msg) devinfo = self.info['devices'][disks[0]] It goes to the trouble of making a list of bootable devices but then ignores it and goes back to self.info['devices']. I'd guess that the last line here should be: devinfo = disks[0] Although I don't know how you make bootable be true. You may find bringing this up on xen-devel useful. ----- With regards, Paul van der Vlis. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xen-utils-3.2-1 depends on: ii e2fslibs 1.41.3-1 ext2 filesystem libraries ii iproute 20080725-2 networking and traffic control too ii libc6 2.7-15 GNU C Library: Shared libraries ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr ii libgnutls26 2.4.2-1 the GNU TLS library - runtime libr ii libncurses5 5.6+20080830-1 shared libraries for terminal hand ii libsdl1.2debian 1.2.13-2 Simple DirectMedia Layer ii libxenstore3.0 3.2.1-2 Xenstore communications library fo ii python 2.5.2-3 An interactive high-level object-o ii python-central 0.6.8 register and build utility for Pyt ii udev 0.125-7 /dev/ and hotplug management daemo ii xen-utils-common 3.2.0-2 XEN administrative tools - common ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages xen-utils-3.2-1 recommends: ii bridge-utils 1.4-5 Utilities for configuring the Linu ii xen-hypervisor-3.2-1-amd64 [x 3.2.1-2 The Xen Hypervisor on AMD64 Versions of packages xen-utils-3.2-1 suggests: ii xen-docs-3.2 3.2.1-2 Documentation for Xen -- no debconf information
--- End Message ---
--- Begin Message ---Hi Hans, Op 22-02-19 om 16:37 schreef Hans van Kranenburg: > Hi Paul, > > This is about the bug report (#507020) about pygrub that you filed > before in the Debian bug tracker, against the Xen packages. > > Your bug report was targeted at a Xen package in a Debian distribution > older than the current stable (Stretch). > > Can you please help us by confirming that any of the following scenarios > does apply to your situation? > > * I had this problem a long time ago. It was never solved, but I found a > workaround, which is ... > * I had this problem a long time ago, and I solved it by not using Xen > any more, but by doing ... > * I still experience this problem, and I'm still using Xen > 3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ... > * I had this problem, and since upgrading to Stretch / Buster / ? it > seems it was solved, and I forgot to report it again. Please close it, > thanks. > * Other: ... I am not using Xen anymore, I did switch to Qemu/KVM for other reasons. I don't know if the problem is in Buster. I found a workarround or a solution, but not sure what it was... I will close the bug. With regards, Paul > Note that even if you found a solution, it's still very useful to report > it back to our bug tracker. There might be someone else running into the > same problem, who can be helped with your information. > > Please note that unless there's a response within a while from now, we > will close the bug report. If you discover this message later, and this > case is important to you, then you can try unarchiving the bug and > replying to it, or reach out to the maintainers email list at > pkg-xen-devel at lists.alioth.debian.org (no subscription required) and > post a message. > > Thanks, > Hans van Kranenburg > -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
--- End Message ---
