search for: virdomainqemumonitorcommand

...memory image, byte per byte, nothing special; I will give this output to tools and parsers like Volatility to get the value from it. I looked around and the only way to get the memory in such a way is using the QEMU monitor command `pmemsave`. I am using libvirt through its Python bindings and the virDomainQemuMonitorCommand seems not to be exposed by the API so, as suggested in some mails I read into the mailig list, I switched to virDomainMemoryPeek. Using this function keeps up to 14-16 seconds to read 512Mb of memory with the 64Kb limitation and 2-3 seconds with the 1Mb one; but the most annoying thing is that I c...

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

Hi, Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when creating a KVM VM using libvirt. This command meaning in “qemu-kvm --help” is: -qmp dev like -monitor but opens in 'control' mode. I added command-line equivalent options into the xml file, like below format: <qemu:commandline> <qemu:arg value="-s"/> <qemu:arg