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

[Neil Williams]

On Sun, 24 Apr 2016 13:49:35 -0300
Antonio Terceiro <terceiro at 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/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/vmdebootstrap-devel/attachments/20160424/ccac2927/attachment-0001.sig>