does not install into given block devices

[Hadmut Danisch]

Hi,

I'm trying (and still doing some tests) to install a KVM host into a given lvm partition. When trying this, ubuntu-vm-builder completely ignored the block device (given with --raw) and created a qcow2.

I am currently repeating tests, and although an existing block device as a hard disk is given, ubuntu-vm-builder still creates a directory in /tmp to run debootstrap on.

This indicates a broken abstraction and object-orientation of the Disk model used in the vm builder. Please fix.

A better concept would be to have an abstract base class of a Disk and then different inheritances for several disk types, which behave differently, e.g. for a given raw device use kpartx to create partitions and install directly into the partitions, while using a tmp file and qemu-img to pack a qcow2 image.

But the current structure of vm-builder is poor in behalf of it's disk treatment. Definitely needs improvement urgently.

regards

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: ubuntu-vm-builder 0.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Wed Jul 28 10:12:10 2010
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/usr/bin/tcsh
SourcePackage: vm-builder

[Sergey Svishchev (svs)]

At least one problem ("ubuntu-vm-builder completely ignored the block device (given with --raw) and created a qcow2.") is fixed in 0.12.4-0ubuntu0.2.