search for: bracktrac

...> render the guest inaccessible. We of course want to eliminate as many of > those situations as possible, so we would love to see the backtrace you > can get from gdb. > > Laine, My apologies on the delay getting back to you, I've been pretty slammed lately. Anyway I have the bracktrace you requested. I simply started libvirtd, started my vm, killed libvirtd, then started it again with gdb in foreground mode with the breakpoint set. I got a ton of debug info that I posted here: http://www.aptalaska.net/~matt.s/libvirt.txt but the backtrace is simply: Breakpoint 1, 0x00007fff...

.... We of course want to eliminate as many of >> those situations as possible, so we would love to see the backtrace you >> can get from gdb. >> >> > Laine, > > My apologies on the delay getting back to you, I've been pretty slammed > lately. Anyway I have the bracktrace you requested. > > I simply started libvirtd, started my vm, killed libvirtd, then started > it again with gdb in foreground mode with the breakpoint set. > > I got a ton of debug info that I posted here: > > http://www.aptalaska.net/~matt.s/libvirt.txt > > but the backt...

Hi all, I''ve done as much bug-fixing as I''m going to be able to do in 0.24.2, I think, so please test the current code if you can. I made some unfortunately significant changes today, in order to try to remove any shared objects in the file server, which will hopefully solve the file corruption issues, plus some very strange issues resulting from renaming

On 04/20/2015 05:42 PM, Laine Stump wrote: > Well, this is when the qemu process is killed (I'm pretty clever, eh? :-) > > I have 3 questions: > > 1) what version of libvirt are you running and on what distro? > > 2) can you reproduce this reliably? > > 3) If the answer to 2 is "yes", do you have the libvirt-debuginfo > package installed, and can you