Hi Daniel, Thanks. The debugger program I used is a multi-level debugging tool called StackDB developed in our department. It was developed for Xen initially, and KVM support was only added recently. I've forwarded your email to the developer and hopefully it should be pretty straightforward to do so. Best Regards, Min On Nov 11, 2014, at 2:32 AM, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote: > On Mon, Nov 10, 2014 at 06:54:58PM -0700, Min Du wrote: >> Hi Kashyap, >> >> Thanks for the reply. >> >>>> >>>> Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when >>>> creating a KVM VM using libvirt. >>> >>> You might need to elaborate how exactly you're doing this. >> >> I wanted to add “-qmp tcp:127.0.0.1:1235” when creating VM because I >> was using a multi-level debugger which needs this option to get more >> information of the VM kernel debuginfo and the processes running inside >> the VM besides gdb attach. > > That's impossible, because libvirt owns the QMP monitor and cannot delegate > use to another process. A core part of the VM startup process requires that > libvirt talk to the QMP monitor to accomplish work, as well as to receive > ongoing notifications of changes in state. > > What is the debugger program you are using ? It really needs to be updated > to use the libvirt APIs instead of QEMU monitor directly. Libvirt provides > an API for issuing monitor commands which it should be able to use. It is > just a question of re-writing the debugger to know about this. > > Regards, > Daniel > -- > |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| > |: http://libvirt.org -o- http://virt-manager.org :| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| > |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
