Debian Bug report logs - #822452
vmdebootstrap: can't produce a working wheezy image

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Antonio Terceiro <terceiro@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: vmdebootstrap: can't produce a working wheezy image

Date: Sun, 24 Apr 2016 13:49:35 -0300

[Message part 1 (text/plain, inline)]

Package: vmdebootstrap
Version: 1.5-1
Severity: normal

$ sudo http_proxy=http://127.0.0.1:3142 vmdebootstrap --enable-dhcp --image test-grub.img --serial-console --distribution wheezy --verbose --log test-grub.log && echo booting image && kvm -snapshot -nographic test-grub.img
Creating disk image
Creating partitions
Installing MBR
Creating filesystem ext4
Mounting /dev/mapper/loop0p1 on /tmp/tmpnAlgj7
Debootstrapping wheezy [amd64]
Give root an empty password
Removing udev persistent cd and net rules
Setting up networking
Updating the initramfs
Installing extlinux
Optimizing image for compression
Cleaning up
booting image

SYSLINUX 6.03 20151108 Copyright (C) 1994-2014 H. Peter Anvin et al
Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or directory
boot: 
Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or directory
boot: 
Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or directory
boot: 
[ ^^^^ repeats forever ^^^^ ]

The log file is attached.


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

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

Versions of packages vmdebootstrap depends on:
ii  debootstrap         1.0.80
ii  extlinux            3:6.03+dfsg-11
ii  kpartx              0.5.0+git1.656f8865-9
ii  libjs-sphinxdoc     1.3.6-2
ii  mbr                 1.1.11-5+b1
ii  parted              3.2-15
ii  python-cliapp       1.20160316-1
ii  python-distro-info  0.14
ii  python2.7           2.7.11-8
pn  python:any          <none>
ii  qemu-utils          1:2.5+dfsg-5+b1

Versions of packages vmdebootstrap recommends:
ii  grub2-common      2.02~beta2-36
ii  python-guestfs    1:1.32.4-1
ii  qemu-system       1:2.5+dfsg-5+b1
ii  qemu-user-static  1:2.5+dfsg-5+b1
ii  squashfs-tools    1:4.3-3

Versions of packages vmdebootstrap suggests:
pn  cmdtest       <none>
ii  pandoc        1.16.0.2~dfsg-1
pn  u-boot:armhf  <none>

-- no debconf information

-- 
Antonio Terceiro <terceiro@debian.org>

[test.log (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #12 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Neil Williams <codehelp@debian.org>

To: vmdebootstrap-devel@lists.alioth.debian.org

Cc: Antonio Terceiro <terceiro@debian.org>, 822452@bugs.debian.org

Subject: Re: [Vmdebootstrap-devel] Bug#822452: vmdebootstrap: can't produce a working wheezy image

Date: Sun, 24 Apr 2016 19:27:41 +0100

[Message part 1 (text/plain, inline)]

On Sun, 24 Apr 2016 13:49:35 -0300
Antonio Terceiro <terceiro@debian.org> wrote:

> Package: vmdebootstrap
> Version: 1.5-1
> Severity: normal
> 
> $ sudo http_proxy=http://127.0.0.1:3142 vmdebootstrap --enable-dhcp
> --image test-grub.img --serial-console --distribution wheezy
> --verbose --log test-grub.log && echo booting image && kvm -snapshot
> -nographic test-grub.img Creating disk image Creating partitions
> Installing MBR Creating filesystem ext4

Can you test with --roottype ext2 ? ext3 works for me too.

The extlinux.conf file is correctly generated, it just looks like the
filesystem is not mounted.

> SYSLINUX 6.03 20151108 Copyright (C) 1994-2014 H. Peter Anvin et al
> Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or
> directory boot: 
> Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or
> directory boot: 
> Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or
> directory boot: 
> [ ^^^^ repeats forever ^^^^ ]

All of the wheezy test images I've used were using ext2 and it may be
that a change in the default has resulted in syslinux not coping in
wheezy.

I can update the docs and the default for wheezy.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

[Message part 2 (application/pgp-signature, inline)]

Message #17 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Antonio Terceiro <terceiro@debian.org>

To: Neil Williams <codehelp@debian.org>

Cc: vmdebootstrap-devel@lists.alioth.debian.org, 822452@bugs.debian.org

Subject: Re: [Vmdebootstrap-devel] Bug#822452: vmdebootstrap: can't produce a working wheezy image

Date: Mon, 25 Apr 2016 10:56:07 -0300

[Message part 1 (text/plain, inline)]

On Sun, Apr 24, 2016 at 07:27:41PM +0100, Neil Williams wrote:
> On Sun, 24 Apr 2016 13:49:35 -0300
> Antonio Terceiro <terceiro@debian.org> wrote:
> 
> > Package: vmdebootstrap
> > Version: 1.5-1
> > Severity: normal
> > 
> > $ sudo http_proxy=http://127.0.0.1:3142 vmdebootstrap --enable-dhcp
> > --image test-grub.img --serial-console --distribution wheezy
> > --verbose --log test-grub.log && echo booting image && kvm -snapshot
> > -nographic test-grub.img Creating disk image Creating partitions
> > Installing MBR Creating filesystem ext4
> 
> Can you test with --roottype ext2 ? ext3 works for me too.

yes, it works with --roottype ext3

> The extlinux.conf file is correctly generated, it just looks like the
> filesystem is not mounted.
> 
> > SYSLINUX 6.03 20151108 Copyright (C) 1994-2014 H. Peter Anvin et al
> > Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or
> > directory boot: 
> > Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or
> > directory boot: 
> > Loading boot/vmlinuz-3.2.0-4-amd64... failed: No such file or
> > directory boot: 
> > [ ^^^^ repeats forever ^^^^ ]
> 
> All of the wheezy test images I've used were using ext2 and it may be
> that a change in the default has resulted in syslinux not coping in
> wheezy.
> 
> I can update the docs and the default for wheezy.

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Neil Williams <codehelp@debian.org>

To: Antonio Terceiro <terceiro@debian.org>

Cc: 822452@bugs.debian.org, vmdebootstrap-devel@lists.alioth.debian.org

Subject: Re: [Vmdebootstrap-devel] Bug#822452: Bug#822452: vmdebootstrap: can't produce a working wheezy image

Date: Mon, 25 Apr 2016 15:43:48 +0100

[Message part 1 (text/plain, inline)]

On Mon, 25 Apr 2016 10:56:07 -0300
Antonio Terceiro <terceiro@debian.org> wrote:

> On Sun, Apr 24, 2016 at 07:27:41PM +0100, Neil Williams wrote:
> > On Sun, 24 Apr 2016 13:49:35 -0300
> > Antonio Terceiro <terceiro@debian.org> wrote:
> > > $ sudo http_proxy=http://127.0.0.1:3142 vmdebootstrap
> > > --enable-dhcp --image test-grub.img --serial-console
> > > --distribution wheezy --verbose --log test-grub.log && echo
> > > booting image && kvm -snapshot -nographic test-grub.img Creating
> > > disk image Creating partitions Installing MBR Creating filesystem
> > > ext4  
> > 
> > Can you test with --roottype ext2 ? ext3 works for me too.  
> 
> yes, it works with --roottype ext3
> > 
> > All of the wheezy test images I've used were using ext2 and it may
> > be that a change in the default has resulted in syslinux not coping
> > in wheezy.
> > 
> > I can update the docs and the default for wheezy.  

OK, I'll update the docs, add a yarn test and a check on the options
that ext4 isn't going to work if wheezy is specified. (i.e. --roottype
becomes required if distribution is mapped to wheezy using
distro_info and the roottype must not be ext4.) IIRC syslinux in wheezy
just doesn't handle ext4 for the boot files. A separate /boot ext2
partition seems to be more work than it's worth. Once grub is working,
it may be possible to convert to ext4 [0] but that too seems like a lot
of work/risk.

[0]
https://www.debian-administration.org/article/643/Migrating_a_live_system_from_ext3_to_ext4_filesystem

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

[Message part 2 (application/pgp-signature, inline)]

Message #27 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Antonio Terceiro <terceiro@debian.org>

To: Neil Williams <codehelp@debian.org>

Cc: 822452@bugs.debian.org, vmdebootstrap-devel@lists.alioth.debian.org

Subject: Re: [Vmdebootstrap-devel] Bug#822452: Bug#822452: vmdebootstrap: can't produce a working wheezy image

Date: Mon, 25 Apr 2016 12:35:29 -0300

[Message part 1 (text/plain, inline)]

On Mon, Apr 25, 2016 at 03:43:48PM +0100, Neil Williams wrote:
> On Mon, 25 Apr 2016 10:56:07 -0300
> Antonio Terceiro <terceiro@debian.org> wrote:
> 
> > On Sun, Apr 24, 2016 at 07:27:41PM +0100, Neil Williams wrote:
> > > On Sun, 24 Apr 2016 13:49:35 -0300
> > > Antonio Terceiro <terceiro@debian.org> wrote:
> > > > $ sudo http_proxy=http://127.0.0.1:3142 vmdebootstrap
> > > > --enable-dhcp --image test-grub.img --serial-console
> > > > --distribution wheezy --verbose --log test-grub.log && echo
> > > > booting image && kvm -snapshot -nographic test-grub.img Creating
> > > > disk image Creating partitions Installing MBR Creating filesystem
> > > > ext4  
> > > 
> > > Can you test with --roottype ext2 ? ext3 works for me too.  
> > 
> > yes, it works with --roottype ext3
> > > 
> > > All of the wheezy test images I've used were using ext2 and it may
> > > be that a change in the default has resulted in syslinux not coping
> > > in wheezy.
> > > 
> > > I can update the docs and the default for wheezy.  
> 
> OK, I'll update the docs, add a yarn test and a check on the options
> that ext4 isn't going to work if wheezy is specified. (i.e. --roottype
> becomes required if distribution is mapped to wheezy using
> distro_info and the roottype must not be ext4.)

please make ext3 the default for wheezy instead of requiring an explicit
--roottype. otherwise one cannot have generic build recipes using
vmdebootstrap that take the target distribution as a parameter (case in
point: I'm building vagrant-libvirt images using vmdebootstrap)

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Neil Williams <codehelp@debian.org>

To: Antonio Terceiro <terceiro@debian.org>

Cc: 822452@bugs.debian.org, vmdebootstrap-devel@lists.alioth.debian.org

Subject: Re: [Vmdebootstrap-devel] Bug#822452: Bug#822452: vmdebootstrap: can't produce a working wheezy image

Date: Mon, 25 Apr 2016 19:11:55 +0100

[Message part 1 (text/plain, inline)]

On Mon, 25 Apr 2016 12:35:29 -0300
Antonio Terceiro <terceiro@debian.org> wrote:

> On Mon, Apr 25, 2016 at 03:43:48PM +0100, Neil Williams wrote:
> > On Mon, 25 Apr 2016 10:56:07 -0300
> > Antonio Terceiro <terceiro@debian.org> wrote:
> > OK, I'll update the docs, add a yarn test and a check on the options
> > that ext4 isn't going to work if wheezy is specified. (i.e.
> > --roottype becomes required if distribution is mapped to wheezy
> > using distro_info and the roottype must not be ext4.)  
> 
> please make ext3 the default for wheezy instead of requiring an
> explicit --roottype. otherwise one cannot have generic build recipes
> using vmdebootstrap that take the target distribution as a parameter
> (case in point: I'm building vagrant-libvirt images using
> vmdebootstrap)

OK, I'll make it so that explicit ext4 on wheezy gives an error and
output a message that ext3 is being used on wheezy if roottype not
specified.

I can't guarantee that generic recipes for all current suites will
always exist though, especially unstable and after point releases. (I'm
hoping that lava.debian.net will help with point release testing.)

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

[Message part 2 (application/pgp-signature, inline)]

Message #37 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Antonio Terceiro <terceiro@debian.org>

To: Neil Williams <codehelp@debian.org>

Cc: 822452@bugs.debian.org, vmdebootstrap-devel@lists.alioth.debian.org

Subject: Re: [Vmdebootstrap-devel] Bug#822452: Bug#822452: vmdebootstrap: can't produce a working wheezy image

Date: Mon, 25 Apr 2016 16:19:56 -0300

[Message part 1 (text/plain, inline)]

On Mon, Apr 25, 2016 at 07:11:55PM +0100, Neil Williams wrote:
> On Mon, 25 Apr 2016 12:35:29 -0300
> Antonio Terceiro <terceiro@debian.org> wrote:
> 
> > On Mon, Apr 25, 2016 at 03:43:48PM +0100, Neil Williams wrote:
> > > On Mon, 25 Apr 2016 10:56:07 -0300
> > > Antonio Terceiro <terceiro@debian.org> wrote:
> > > OK, I'll update the docs, add a yarn test and a check on the options
> > > that ext4 isn't going to work if wheezy is specified. (i.e.
> > > --roottype becomes required if distribution is mapped to wheezy
> > > using distro_info and the roottype must not be ext4.)  
> > 
> > please make ext3 the default for wheezy instead of requiring an
> > explicit --roottype. otherwise one cannot have generic build recipes
> > using vmdebootstrap that take the target distribution as a parameter
> > (case in point: I'm building vagrant-libvirt images using
> > vmdebootstrap)
> 
> OK, I'll make it so that explicit ext4 on wheezy gives an error and
> output a message that ext3 is being used on wheezy if roottype not
> specified.

cool, thanks.

> I can't guarantee that generic recipes for all current suites will
> always exist though, especially unstable and after point releases. (I'm
> hoping that lava.debian.net will help with point release testing.)

I guess at some point we might need to keep a set of sane defaults for
each supported distribution ... so that `vmdebootstrap --distribution
$foo` always works regardless of the value of $foo(?)

[signature.asc (application/pgp-signature, inline)]

Message #44 received at 822452@bugs.debian.org (full text, mbox, reply):

From: Neil Williams <codehelp@debian.org>

To: 822452@bugs.debian.org

Subject: Change of plan

Date: Sun, 17 Jul 2016 17:10:51 +0100

[Message part 1 (text/plain, inline)]

Generic recipes are not sufficiently important to go changing the
defaults which are correct for other options. When I came to implement
this fix, I realised that changing the default on-the-fly is just
"magic" and the correct thing to do is to exit with the exception. I'm
not going to start changing defaults on-the-fly or "hidden" from the
user. Predictable behaviour is more important.

Recipes can be done with config files per distribution and cliapp
supports reading all the various options from such files. (Examples of
the config format are in all of the vmdebootstrap log files.) See the
--config=FILE option.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

[Message part 2 (application/pgp-signature, inline)]

Message #49 received at 822452-close@bugs.debian.org (full text, mbox, reply):

From: Neil Williams <codehelp@debian.org>

To: 822452-close@bugs.debian.org

Subject: Bug#822452: fixed in vmdebootstrap 1.6-1

Date: Thu, 11 Aug 2016 22:19:48 +0000

Source: vmdebootstrap
Source-Version: 1.6-1

We believe that the bug you reported is fixed in the latest version of
vmdebootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822452@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neil Williams <codehelp@debian.org> (supplier of updated vmdebootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 17 Jul 2016 15:29:01 +0100
Source: vmdebootstrap
Binary: vmdebootstrap
Architecture: source amd64
Version: 1.6-1
Distribution: unstable
Urgency: medium
Maintainer: VMDebootstrap List <vmdebootstrap-devel@lists.alioth.debian.org>
Changed-By: Neil Williams <codehelp@debian.org>
Description:
 vmdebootstrap - Bootstrap Debian into a (virtual machine) disk image
Closes: 822180 822452 826275 827130 831025 831029 831030 831439 833398
Changes:
 vmdebootstrap (1.6-1) unstable; urgency=medium
 .
   * Deprecating extlinux as default - to switch to grub in a
     future release.
   * Fix customisation support for alternative mirrors.
   * Switch to --no-systemd-networkd in man page (Closes: #831025)
   * Enable systemd-resolved together with systemd-networkd to
     ensure the final image has working DNS. (Closes: #831439)
   * Reset umask before creating files and restore. (Closes: #822180)
   * Disable ext4 with wheezy image (Closes: #822452)
   * Update documentation for --customize. (Closes: #826275)
   * Umount before doing the qcow2 conversion. (Closes: #831029)
   * Ensure chown is called after the qcow2 conversion. (Closes: #831030)
   * Exclude metadata_csum when building ext4 jessie images
     (Closes: #827130)
   * Support dependencies of custom packages. (Closes: #833398)
Checksums-Sha1:
 a6a23eedec2ad0c099ce5ce9e615682157677536 2231 vmdebootstrap_1.6-1.dsc
 7022e3cdaf1a88b23c10a9f77901253a4a430beb 67655 vmdebootstrap_1.6.orig.tar.gz
 e859b88031384001cf136731912b4a72e406118f 5812 vmdebootstrap_1.6-1.debian.tar.xz
 30ec9e9e0f7a8d182db9e4aee74744bd4bc0ea42 75684 vmdebootstrap_1.6-1_amd64.deb
Checksums-Sha256:
 22a88e4fbd8e62db1b0b5bbafb5c0675a5405754c8687ecb3604374cbba0b5b0 2231 vmdebootstrap_1.6-1.dsc
 9f2d6bdc22029d5176d8a6ac4756fc8ac5014d17ae0b4ca705f5f056bd881617 67655 vmdebootstrap_1.6.orig.tar.gz
 8fd6d251e40909aeb30d5d079807e87e68d73979b85cf50092c4be915bb7f698 5812 vmdebootstrap_1.6-1.debian.tar.xz
 667457a5e2a6a33956f48aae2ad60b6dad099b488969494c152e304697e346f0 75684 vmdebootstrap_1.6-1_amd64.deb
Files:
 7325dfe6e21767f3ba119701b28111d5 2231 admin extra vmdebootstrap_1.6-1.dsc
 093fa19964bd50d4eddc1452a925a9d3 67655 admin extra vmdebootstrap_1.6.orig.tar.gz
 b06cd26b0672a0824bcb4afa5e8fac1c 5812 admin extra vmdebootstrap_1.6-1.debian.tar.xz
 c6ec1eadbf2f68c334d058e2245751c3 75684 admin extra vmdebootstrap_1.6-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXrPPqAAoJEPFn5DyBQ7aCA4kP/iejnDcP8rvMRMIQ0hGfAFOW
HKH6IaJBJqGXKmcD2s28YP+sWyG1X7ZDdXas1bam7aH69fTJFDGveySJKj0rzipC
3Q5mx1x7kuyLogCeEcJk0lejWfceCQrNAcr5zv0qDqC3c3m1lW2mgV7f3OMfue8c
4C2nY0rtwlqhco1DAykipu3ZceN6G1Kz5usOoWYlmtF/Lqr0ryR+0BipiMSo9cwG
JvP0hnptl6ucoHcNESuXJVksQe+Zs3RX1apaatDdE8Cnt+xvs1gqvRSDFveiCrU6
ivZQQqOAHnp2mjeA8MT7qu8Hsu9bB6Szq5RZA5qx4+l+A8S99IVMUhNusRN3080f
PfNgodKsWvFJ70pQztjinH3ERt8Wx1DwLG8o2PV4d6zW5NTXxomB63sToB9FLgmn
OL3rbZTl9US0CMT2plmzChcJ09qpLl9YXkdmRWJeQ4pJerzI/uWKJGhtNWs1b3ZB
4Ycv23bUP4CeQNSVqEeg9AJIJwKVx2eKlLi86YtfKipCr8W0Kq8zcapMeyd6oZE3
4pwBJEKxeZ4FiErlLOq4hOaN8xnEzs4O29XWV1RfhsSLP4BXovbx9ri9475SUnBN
sM2++raU7aOrXSHwx9o5xNo0esYzxwn32JztI+SK8Myh1QHGU+IHCuVBTZ/LDcyO
k9dgiKA/7dLSImeNfEoH
=Qk+g
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.