From owner-freebsd-virtualization@freebsd.org Tue Aug 28 13:44:17 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4779E108CC9D for ; Tue, 28 Aug 2018 13:44:17 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A13CE8483D for ; Tue, 28 Aug 2018 13:44:16 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-lf1-x12a.google.com with SMTP id g6-v6so1410119lfb.11 for ; Tue, 28 Aug 2018 06:44:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=uu/iydn6by3NEoo2Bi8S7YxyRSrD0KRR/ayyGa2udlY=; b=tXSFiV2S0FARD1hiG780r6ETV3PVp+845WEpcfI48lBIknJKZKYPNPVZwBWHkGq6Da 6wkOFjuS01J2Jb5hFvXX1OTWUWNcV1OjTxIt2lab2dViVXd2on+LxiehSczsy7m1QdT6 dIcWTy+98aqMGK73kGgkcvexghkR3vKNuQjjZWJCZHHiKJ5yrzd6iPMajckIqsltnYYM hbWxrZOktfy0rlDaq0JU0l3aHdBYTlz1E2qxEZBbW20fmw17LF6FiFeSzpi6/BTLAO+6 TK7PYrU+84OTapgi7ltCOSkwVA+4aJSuL9fkzmJB7cVt/ohlns59STWkS4/ktKypl2bn W5tQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=uu/iydn6by3NEoo2Bi8S7YxyRSrD0KRR/ayyGa2udlY=; b=giHzcwlRkGLg89B2FPVCNqkkqLyT38hxmw1oMEwuhNrsnMJBBM+Zk/inz76XIygm0U 6JYStFugcRFIQnpDubtSS0crZ02mUOxxRMkEH4S0yiwQPVF4TX+avJ0SaoRUwDX0oghI KY6xLsnJAAqqhZLZUT/X8hqh7Lm/Kl1CFYetue18UijR5D2tb9hceGOj/ZXNkszrTtNx iC39XssP0fh/oesonkz0cYXlK0Z+5SXOPkFmU95p3Y3L1+iYcxuP/2CZgi6G2jG8S483 KWa6OE42MXIMtppHtgS58k+shCZekg6h6AekYut9H2GoYg/fbHRJyVdCHSANcOw9lQd1 8nsw== X-Gm-Message-State: APzg51A6Cs7VqjqK1e3YEtpeK7/EONhgvQU0FQbtWV8xX1t0b3caPbHQ 2/e7eiuGqwmtc+8JkTC5vgVZkMZP2bIa65inM8IrDA== X-Google-Smtp-Source: ANB0VdZZJh/IMqtwKnorJY1lCaahar1+R06k7eThj0wOlegpfkeh13gs7zPDzO5jAts7bfDpWxWDPstJNaxlPBbiO7o= X-Received: by 2002:a19:54c2:: with SMTP id b63-v6mr1406634lfl.128.1535463855305; Tue, 28 Aug 2018 06:44:15 -0700 (PDT) MIME-Version: 1.0 References: <201808281337.w7SDbAEe015573@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201808281337.w7SDbAEe015573@pdx.rh.CN85.dnsmgr.net> Reply-To: araujo@freebsd.org From: Marcelo Araujo Date: Tue, 28 Aug 2018 21:44:02 +0800 Message-ID: Subject: Re: on bhyve statistics To: "Rodney W. Grimes" Cc: Anish , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 13:44:17 -0000 On Tue, Aug 28, 2018, 9:38 PM Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > >> Currently, bhyve does not expose any of these statistics. All the > stats > > > available through bhyvectl --get-stats seem to be coming from the VMM, > > > not from the userspace emulation. > > > > >That is correct, byhvectl is a diagnostics tool for getting > > information from the kernel/vmm module. > > > > bhyvectl provide stats related to processor vmx/svm from vmm.ko and is > the > > first thing you want to run for performance regression. It will be nice > to > > include it as part of bhyve perf tool/dashboard that you are intended to > > build. > > From conversations with Peter Grehan he expressed that bhyvectl is > purely a diagnostics tool that should not be depended on by any > other tools. > > If you want to do similiar things you should program to the libvmmapi > interface, not bhyvectl. > The libvmmapi is more an internal library for usage with bhyvectl and bhyveload than for other purposes, of course it won't stop anybody to extend it to achieve other goals. > > -Anish > > > > On Mon, Aug 27, 2018 at 8:20 AM Rodney W. Grimes < > > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > > Hi list, > > > > > > > > I'm currently looking at getting the libvirt prometheus exporter[1] > to > > > > work with libvirt+bhyve. In its current state this doesn't work > because > > > > at least one of the API calls exposed by libvirt isn't implemented by > > > > the libvirt bhyve driver - so I started looking at implementing it. > > > > > > > > The first API call in question is virDomainBlockStats[2], which > returns > > > > statistics (number of read and written bytes and ops, respectively). > > > > > > > > Currently, bhyve does not expose any of these statistics. All the > stats > > > > available through bhyvectl --get-stats seem to be coming from the > VMM, > > > > not from the userspace emulation. > > > > > > That is correct, byhvectl is a diagnostics tool for getting > > > information from the kernel/vmm module. > > > > > > > OTOH, I did see that there are *some* > > > > stats being collected in bhyverun.c (see struct bhyvestats {...} > > > > stats;). I can't see how these are exposed though - a grep of > /usr/src > > > > turned up no other uses. Which brings me to the following questions: > > > > > > > > - are the stats in struct bhyvestats {...} stats exposed or used in > any > > > > non-obvious way? > > > > > > Not that I am aware of. > > > > > > > - architecturally, what would be the best ways to get stats out of > the > > > > user-space emulations? Off of the top of my head, I could think of > the > > > > following possibilities: > > > > - prometheus exporter > > > > - having some socket or pipe to request them > > > > - DTrace probes > > > > > > > > I wouldn't mind implementing any of the above, and so would like to > know > > > > which of these (or other options) would be the most acceptable, and > > > > would appreciate some guidance. > > > > > > I differ to others on what may be the best way to do this. > > > > > > > CC'ing novel@ for the libvirt side, and grehan@ for the > architectural > > > > bhyve questions. > > > > > > You should replace @grehan with @jhb,@tychon as Peter has moved on, > > > and John and Tycho are now the bhyve maintainers. I was going to > > > add them, and remove Peter, but I see no cc: anyway, so I am sure > > > that they are on the virtualization list though. > > > > > > > Fabian > > > > > > > > [1] https://github.com/kumina/libvirt_exporter > > > > [2] > > > > https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockStats > > > -- > > > Rod Grimes > > > rgrimes@freebsd.org > > -- > Rod Grimes > rgrimes@freebsd.org > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >