search

purpleidea / vagrant-builder

an elegant method for making base images for vagrant-libvirt
GNU Affero General Public License v3.0
42 stars 23 forks source link

Debian 8 install hangs at 'apt-get install && apt-get upgrade -y' #21

Open wzzrd opened 8 years ago

wzzrd commented 8 years ago

After the package upgrade step for Debian 8, vagrant-builder / virt-builder hangs with the output below (added -v -x to the virt-builder commandline):

commandrvf: /bin/sh -c "exec >>'/tmp/builder.log' 2>&1

apt-get update && apt-get -y upgrade
"
[   75.225833] EXT4-fs (sda2): unable to read superblock
[   75.226671] EXT4-fs (sda2): unable to read superblock
[   75.227521] EXT4-fs (sda2): unable to read superblock
[   75.228340] isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32
[   75.229350] FAT-fs (sda2): bogus number of reserved sectors
[   75.229647] FAT-fs (sda2): Can't find a valid FAT filesystem
[   75.230509] attempt to access beyond end of device
[   75.230783] sda2: rw=16, want=3, limit=2
[   75.231020] hfsplus: unable to find HFS+ superblock
[   75.231802] hfs: can't find a HFS filesystem on dev sda2
GRUB install devices:

This is with unedited vagrant-builder files.

purpleidea commented 8 years ago

So this shitty thing about vagrant-builder is that unrelated "families" (whatever that means) have essentially different copies of the same code, since I was either too lazy or didn't care, or it was too hard, to unify one "code base". So the stuff you just patched (the raw vs qcow2 thing) happened in the v7/ folder, where as everything in debian/ is separate. So perhaps you have the same issue, and I forgot to ask you to patch it in both places.

So 1) try that same fix. 2) Please submit another patch

3) Feel free to try and unify the two code bases, although that's an optional goal 4) I realized that the last images I built were actually made on Fedora 21. So indeed I am now on F23, but perhaps I might not have tested the code fully with these new versions.

wzzrd commented 8 years ago

I tried the same fix already. Will look into this later. Not a real high priority for me :)