search for: guestfs_remove_drive

...led with no drives added[2]. The reason this changed is that hotplugging makes it much more difficult to track drives in the handle across multiple launches. Should drives which were hot-added after launch be added before the second launch? What about drives which have been removed from the list (guestfs_remove_drive) -- should we remember those and magically reinstate them? I should note that neither behaviour was/is documented. The best advice of all is: DO NOT CALL LAUNCH MORE THAN ONCE ON THE SAME HANDLE! Handles are very cheap to create (guestfs_create is basically a malloc). There is no reason not to...

Greetings, I'd like to monitor the FS activities (read/write) at runtime on several virtual disk images running on Qemu KVM. The aim is to periodically inspect these images to identify possible Windows registry modification, file creation and so on.. What should be the optimal procedure? Shall I launch a new handler each time? It is a quite expensive procedure and it takes a lot of time on

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

This rounds off hotplugging support by allowing you to add and remove drives at any stage (before and after launch). Rich.