Bug#833057: /usr/bin/extlinux: extlinux --install fails to boot if the rootfs is ext4

2017-06-30 Thread Peter Colberg
Control: tags -1 moreinfo

Hi Neil,

On Sun, Jul 31, 2016 at 11:29:25AM +0100, Neil Williams wrote:
> Package: extlinux
> Version: 3:6.03+dfsg-14
> Severity: important
> File: /usr/bin/extlinux
> 
> With vmdebootstrap, I'm trying to maintain extlinux support but the latest 
> package
> fails to make the image bootable if the rootfs is ext4. ext3 and ext2 work, 
> so I'm
> going to need to prevent vmdebootstrap images building ext4 if extlinux is 
> used until
> this is fixed. (Grub works fine with ext2, 3 and 4.)
> 
> When building on Jessie, this problem does not occur - only when building the 
> VM
> on stretch or sid. (This is a separate bug that syslinux requires the use of 
> files
> which are not included in the VM and cannot be installed using only the files 
> of
> the VM.)

Are you able to boot from ext4 after disabling the 64bit feature?

mkfs.ext4 -O ^64bit

http://www.syslinux.org/wiki/index.php?title=Filesystem#ext

Regards,
Peter



Bug#833057: /usr/bin/extlinux: extlinux --install fails to boot if the rootfs is ext4

2016-07-31 Thread Neil Williams
Package: extlinux
Version: 3:6.03+dfsg-14
Severity: important
File: /usr/bin/extlinux

With vmdebootstrap, I'm trying to maintain extlinux support but the latest 
package
fails to make the image bootable if the rootfs is ext4. ext3 and ext2 work, so 
I'm
going to need to prevent vmdebootstrap images building ext4 if extlinux is used 
until
this is fixed. (Grub works fine with ext2, 3 and 4.)

When building on Jessie, this problem does not occur - only when building the VM
on stretch or sid. (This is a separate bug that syslinux requires the use of 
files
which are not included in the VM and cannot be installed using only the files of
the VM.)

vmdebootstrap --owner neil --verbose --extlinux --roottype ext4  --distribution 
sid --image sid4.img
 - results in an image which just outputs "no such file or directory" for the
   kernel and initrd files (which blatantly do exist in the specified paths if
   the image is mounted using loopback support.)

vmdebootstrap --owner neil --verbose --extlinux --roottype ext3  --distribution 
sid --image sid3.img
 - results in an image which boots normally using
   qemu-system-x86_64 -m 2048 -enable-kvm -drive format=raw,file=sid3.img 

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages extlinux depends on:
ii  libc6  2.23-4

Versions of packages extlinux recommends:
ii  syslinux-common  3:6.03+dfsg-14

extlinux suggests no packages.

-- debconf information:
  extlinux/install: false
* extlinux/no-bootloader-integration:
  extlinux/title: