From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40845) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zpddq-0003RI-NB for qemu-devel@nongnu.org; Fri, 23 Oct 2015 10:48:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zpddn-00024h-GS for qemu-devel@nongnu.org; Fri, 23 Oct 2015 10:48:26 -0400 Received: from smtp.aimale.com ([166.78.138.199]:51154) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zpddn-00024X-9D for qemu-devel@nongnu.org; Fri, 23 Oct 2015 10:48:23 -0400 References: <1444952643-5033-1-git-send-email-valerio@aimale.com> <87h9lrkz56.fsf@blackfin.pond.sub.org> <56210A17.6080401@aimale.com> <87io63xpke.fsf@blackfin.pond.sub.org> <56250035.40805@aimale.com> <87twpkqyow.fsf@blackfin.pond.sub.org> <20151022191203.GC3736@thinpad.lan.raisama.net> <877fmeqeho.fsf@blackfin.pond.sub.org> <20151023081853.GA19259@redhat.com> From: Valerio Aimale Message-ID: <562A48B4.9040603@aimale.com> Date: Fri, 23 Oct 2015 08:48:20 -0600 MIME-Version: 1.0 In-Reply-To: <20151023081853.GA19259@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] QEMU patch to allow VM introspection via libvmi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , Markus Armbruster Cc: lcapitulino@redhat.com, Eduardo Habkost , qemu-devel@nongnu.org On 10/23/15 2:18 AM, Daniel P. Berrange wrote: > [...] > It can't today, but just because it creates a temporary file inside > mem-path and unlinks it immediately after opening a file descriptor. We > could make memory-backend-file also accept a full filename as argument, > or add a mechanism to let QEMU send the open file descriptor to a QMP > client. >> Valerio, would an command line option to share guest memory suffice, or >> does it have to be a monitor command? If the latter, why? > IIUC, libvmi wants to be able to connect to arbitrary pre-existing > running KVM instances on the host. As such I think it cannot assume > anything about the way they have been started, so requiring they > be booted with a special command line arg looks impractical for this > scenario. > > Regards, > Daniel Daniel, you are correct. libvmi knows of QEMU/KVM VMs only via libvirt/virsh. The scenario would work if libvmi was able to query, via qmp command, the path of the shared memory map.