What is the recommended way to modify an existing disk on sheepdog? I thought about making the base image default to starting up with DHCP and then dynamically modify itself from within a running VM - but that is a lot more work than having command-line tools to just jump into a virtual disk and start modding things.
On Mon, Jan 23, 2012 at 1:09 AM, MORITA Kazutaka <[email protected]> wrote: > At Wed, 18 Jan 2012 19:00:24 -0800, > Bryan Whitehead wrote: >> >> I'm trying to move away from using qcow2 and instead use sheepdog. >> >> I've gone through the hoops of getting sheepdog running with qemu/kvm. >> I can boot/run from a sheepdog VDI, but taking a snapshot and rebasing >> a new vdi for another instance I'm left without a way to manipulate >> the newly created vdi. >> >> qemu-img -p convert centos6-base.qcow2 sheepdog:centos6-base >> qemu-img snapshot -c snaptest0 sheepdog:centos6-base >> qemu-img create -b sheepdog:centos6-base:1 sheepdog:test >> >> after a virt-clone domain, and virsh edit newdomain I can boot sheepdog:test >> >> But running this: >> guestfish -d newdomain -i < guestfish-commands.txt (this doesn't work) >> >> does not work. seems the hooks from guestfish->qemu are different? > > I took a quick look at guestfish code, and it seems that guestfish > doesn't support network block devices (e.g. nbd, rbd, and sheepdog). > > I'm not familiar with guestfish, so I might be wrong. > > Thanks, > > Kazutaka -- sheepdog mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/sheepdog
