Leslie Mann wrote: > Avi Kivity <[EMAIL PROTECTED]> writes: > > >> The SIGIO means some I/O has occured, but what exactly, we don't know. >> Can you generate a core, attach it with gdb, and generate a backtrace? >> >> Check the backtrace for signs of your password and delete them if >> found. It shouldn't be there, but then it shouldn't crash either. >> >> > > Avi: > > I'm a little bit at a loss as to what to do to get a core backtrace. gcore > gets > me 3 frames with no symbol info and I don't see how that can help you. >
It's probably the aio thread. But wasn't there a segfault? That should get us a nice core. > I have upgraded the Cisco VPN client from 4.6 to a newer version 4.8 and as > well > have tried using a kvm version from svn pulled today, still locking up. > Lockup > seems to happen around when the VPN client attempts to establish IKE session. > > FYI I am using vde_switch for networking. I did manage to get debugging info > compiled with no optimization. The backtrace that follows is from attaching > to > running qemu process after UI lock up. Perhaps there are some clues here? If > not, anything else I provide that would help? > > The backtrace is unhelpful. I guess we should bisect the kvm-17 -> kvm-18 changes. This is a bit difficult as the userspace interface changes are in there, meaning that userspace and the kernel have to be updated in step. I'll prepare the first patch. Can you ensure that your upgraded setup still works kvm-17. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
