I'm currently debug it with paolo from qemu. I have a workaround for qemu if needed (don't known where proxmox 4.0 will be released).
----- Mail original ----- De: "aderumier" <aderum...@odiso.com> À: "Wolfgang Bumiller" <w.bumil...@proxmox.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 29 Septembre 2015 14:05:55 Objet: Re: [pve-devel] qemu start hanging on dell r710 ok, thanks wolfgang ! ----- Mail original ----- De: "Wolfgang Bumiller" <w.bumil...@proxmox.com> À: "aderumier" <aderum...@odiso.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 29 Septembre 2015 13:53:40 Objet: Re: [pve-devel] qemu start hanging on dell r710 > On September 29, 2015 at 12:35 PM Alexandre DERUMIER <aderum...@odiso.com> > wrote: > > Can someone tell me how to debug with qemu dbg package ? AFAIK it just contains unstripped binaries, so you can use 'gdb' to debug it. (You might have to run /usr/lib/debug/usr/bin/kvm (or qemu-*) instead of the regular binary, but I don't think that's necessary, I'm not sure though right now...) To see the source line contents in backtraces the source files have to be available. (You can add a path to the source tree with the `dir` command from within qemu if you've built the package in a temporary location and deleted the files already. Note that the files must be exactly the same you compiled from otherwise the output will just be wrong.) It'll only allow you to debug the qemu related parts though, eg. if the VM dies of an error inside the guest itself (kernel segfault or whatever), then that's not actually an error in the host qemu process, so you won't get the chance to do a backtrace if the guest kernel segfaults because qemu then exits successfully... _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel