On 10/05/2012 01:25 PM, Kashyap Chamarthy wrote: >> >> So, just to clarify, so I don't mess up, on libvirt's latest git, I'm applying only these >> two patches as below: >> >> [PATCH 1/2] blockjob: manage qemu block-commit monitor command >> [PATCH 2/2] blockjob: wire up online qemu block-commit >> >> # git am -3 /path-to-patch1 >> # git am -3 /path-to-patch2 >> # ./autogen.sh Here, I tend to use './autogen.sh --system CFLAGS=-g' if I intend to debug anything under gdb; the --system makes it more likely that the just-built libvirtd can be run without having to install it first. But the ./run script also helps there. >> # make >> # make check >> >> Then run the below (while using the qemu binary from it's git # >> ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -smp 2 -m 1024 >> /home/kashyap/vmimages/f17vm2.qcow2) > > (of-course with relevant changes to the 'emulator' attribute to the domain's libvirt xml file) Yep, and/or install the just-built qemu into the system location. > >> >> And use the 'virsh' to do the testing from the fresh compile: >> >> # ./run ./tools/virsh ... >> Yep, that's about what I'm doing in my tests. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list