I mentioned this to Andreas yesterday, but just to have text in this bug:
- Each "uec image tarball" is a tarfile with files explained at http://bazaar.launchpad.net/~ubuntu-on-ec2/vmbuilder/automated-ec2-builds/annotate/head%3A/README.files
- to boot one of these in test drive:
# the .img files are largely sparse, so using 'tar -S' is quite desirable.
tar -Sxvzf tarball.tar.gz
bname=$(echo *.img) && bname=${bname%.img}
# It is not necessary to use a qcow backing image, but useful to keep the
# .img file pristine
qemu-img create -f qcow2 -b ${bname}.img.dist disk.img
kvm -boot a -fda ${name}-floppy -drive file=disk.img,if=virtio
I mentioned this to Andreas yesterday, but just to have text in this bug: bazaar. launchpad. net/~ubuntu- on-ec2/ vmbuilder/ automated- ec2-builds/ annotate/ head%3A/ README. files img,if= virtio
- Each "uec image tarball" is a tarfile with files explained at http://
- to boot one of these in test drive:
# the .img files are largely sparse, so using 'tar -S' is quite desirable.
tar -Sxvzf tarball.tar.gz
bname=$(echo *.img) && bname=${bname%.img}
# It is not necessary to use a qcow backing image, but useful to keep the
# .img file pristine
qemu-img create -f qcow2 -b ${bname}.img.dist disk.img
kvm -boot a -fda ${name}-floppy -drive file=disk.