search for: guest_disk

...enshot, a core dump and a snapshot, then I resume the guest. Proof is that I can clearly analyse the memory core dump without any problem. Maybe I am breaking the disk's consistency once I extract the dump through the qemu-img command? The command is: qemu-img convert -f qcow2 -o backing_file=guest_disk.qcow2 -O qcow2 -s snapshot_n guest_disk.qcow2 new_disk_for_libguestfs.qcow2 Could it be that, as the backing file is pointing to the guest's disk which will evolve in time, when guestfs tries to read the data sees incosistencies? The guest_disk.qcow2 is a COW clone of a base_disk.qcow2, what...

...include the guest's disk. It just contains the guest's memory, so it's not relevant for consistency. > Maybe I am breaking the disk's consistency once I extract the dump through > the qemu-img command? > > The command is: > qemu-img convert -f qcow2 -o backing_file=guest_disk.qcow2 -O qcow2 -s > snapshot_n guest_disk.qcow2 new_disk_for_libguestfs.qcow2 Is the guest paused when you do this? If not, then this will create an inconsistent snapshot. > Could it be that, as the backing file is pointing to the guest's disk which > will evolve in time, when guest...

...> contains the guest's memory, so it's not relevant for consistency. > > > Maybe I am breaking the disk's consistency once I extract the dump > through > > the qemu-img command? > > > > The command is: > > qemu-img convert -f qcow2 -o backing_file=guest_disk.qcow2 -O qcow2 -s > > snapshot_n guest_disk.qcow2 new_disk_for_libguestfs.qcow2 > > Is the guest paused when you do this? If not, then this will create > an inconsistent snapshot. > > > Could it be that, as the backing file is pointing to the guest's disk > which &gt...

2015-05-28 10:10 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, May 28, 2015 at 09:48:41AM +0300, NoxDaFox wrote: > > 2015-05-27 15:21 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Wed, May 27, 2015 at 09:38:38AM +0300, NoxDaFox wrote: > > > > * RuntimeError: file receive cancelled by daemon - On r = > > >

...nc true libguestfs: trace: set_autosync = 0 libguestfs: trace: launch qemu: could not load kernel '/var/tmp/.guestfs-1000/kernel.6941': Permission denied libguestfs: trace: launch = -1 (error) Traceback (most recent call last): File "get_result.py", line 3, in <module> guest_disk = DiskOperations("PYTI.vdi") File "/usr/local/lib/python2.7/dist-packages/pyti/vmanager/diskhandler.py", line 20, in __init__ self.disk_fs.launch() File "/usr/lib/pymodules/python2.7/guestfs.py", line 188, in launch return libguestfsmod.launch (self._o) Ru...

...d into the root directory of the currently mounted guest disk. If it is guestfsd which crashes, then the appliance will exit, but I have checked that the coredump is written and synched first. You can then copy this out of the guest disk using guestfish and debug using gdb: $ guestfish --ro -a guest_disk -m /dev/vg/lv_root ><fs> ll / ><fs> download /core.xxx.yyy.zzz core $ gdb daemon/guestfsd core http://fedoraproject.org/wiki/StackTraces#Obtaining_a_stack_trace_from_a_core_dump Clearly you need to have a writable guest disk mounted for this to work, and you have to not...