On Fri, Feb 28, 2014 at 07:18:16AM +0100, Martin Pitt wrote:
> Package: vmdebootstrap
> Version: 0.2-1
> 
> I tried to create an image like this:
> 
> $ sudo vmdebootstrap --image=adt-sid-amd64.qemu --distribution=sid --verbose
> Creating disk image
> Creating partitions
> Installing MBR
> Creating filesystem ext4
> Mounting /dev/mapper/loop0p1 on /tmp/tmpbE3Nr8
> Debootstrapping
> Give root an empty password
> Removing udev persistent cd and net rules
> Setting up networking
> Installing extlinux
> Cleaning up
> ERROR: /tmp/tmpbE3Nr8/ldlinux.sys: Operation not permitted

I can reproduce something close to this on my up to date sid box, but
not exactly the same.

First, `loop` is not being loaded at boot as it used to (or at least I
never configured anything for it to happen so I assume it should), so I
have to

$ sudo modprobe loop

Then, the first image I build just works, and the second and all
subsequent ones fail.

----------------8<----------------8<----------------8<-----------------
$ sudo http_proxy=http://localhost:3142 vmdebootstrap 
--image=adt-sid-amd64.qemu --distribution=sid --serial-console --verbose 
Creating disk image
Creating partitions
Installing MBR
Creating filesystem ext4
Mounting /dev/mapper/loop0p1 on /tmp/tmpCLIQRk
Debootstrapping
Give root an empty password
Removing udev persistent cd and net rules
Setting up networking
Installing extlinux
Cleaning up

$ kvm -snapshot -nographic adt-sid-amd64.qemu 

SYSLINUX 4.05 20131121 Copyright (C) 1994-2011 H. Peter Anvin et al
Loading boot/vmlinuz-3.13-1-amd64.....
Loading boot/initrd.img-3.13-1-amd64..............ready.

...
... boots just fine
...

root@debian:~# halt

...
... shuts down just fine
...

$ sudo http_proxy=http://localhost:3142 vmdebootstrap 
--image=another-image.qemu --distribution=sid --serial-console --verbose
Creating disk image
Creating partitions
Installing MBR
Creating filesystem ext4
EEEK! Something bad happened...
Cleaning up
ERROR: command failed: ['mkfs', '-t', 'ext4', '/dev/mapper/loop0p1']

mke2fs 1.42.9 (4-Feb-2014)
Could not stat /dev/mapper/loop0p1 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
$
----------------8<----------------8<----------------8<-----------------

Maybe there is something broken with loop devices? The first
(successull) call takes 8 min to complete which AFAIR is too much.

-- 
Antonio Terceiro <terce...@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply via email to