All of lore.kernel.org
 help / color / mirror / Atom feed
From: Farkas Levente <lfarkas-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
To: Fedora/Linux Management Tools
	<et-mgmt-tools-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [et-mgmt-tools] ANNOUNCE: virt-top 0.3.2.7 released
Date: Fri, 21 Sep 2007 12:11:05 +0200	[thread overview]
Message-ID: <46F398B9.5070707@bppiac.hu> (raw)
In-Reply-To: <46F38947.9040709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Richard W.M. Jones wrote:
> Richard W.M. Jones wrote:
>> Richard W.M. Jones wrote:
>>> Farkas Levente wrote:
>>>> [root@kvm ~]# /usr/bin/virt-top --connect qemu:///system
>>>> libvir: error : this function is not supported by the hypervisor:
>>>> virConnectGetHostname
>>>> Fatal error: exception Libvirt.Virterror(3, 0, _, 2, _, 0, _, _, 0,
>>>> _, _, 0)
>>>> [root@kvm ~]# rpm -q libvirt
>>>> libvirt-0.3.2-2
>>>
>>> You've found a real bug.  Virt-top is not very well tested against
>>> qemu, or rather that should be not tested at all.  But I'll go and
>>> try to make it work with qemu now.  Probably take a few hours though ...
>>
>> The patch to fix that particular bug is attached.  There may be other
>> though, still testing ...
> 
> OK, I'm fairly sure this is the only patch needed.
> 
> I'm going to roll this in to the next (0.3.2.8) release later.
> 
> Libvirt needs works to support block and network stats from QEMU/KVM.
> Virt-top won't fail because this is missing, it just can't display
> anything in those columns.  The work as far as I understand it is fairly
> simple, but also lower down on my list of priorities at the moment.
> 
> Another thing which virt-top uses but which is missing in QEMU/KVM is
> physical CPU usage and CPU pinning.  I have absolutely no idea if qemu
> supports this -- I assume it does through ordinary Linux mechanisms such
> as numactl.  As for KVM, no idea whatsoever.

maybe you can ask kvm people:-)
anyway if the new version will be uploaded i can try it again.

-- 
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

       reply	other threads:[~2007-09-21 10:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46F25C6F.8030903@redhat.com>
     [not found] ` <46F267CA.3010501@bppiac.hu>
     [not found]   ` <46F2694B.1020802@redhat.com>
     [not found]     ` <46F26C3F.9010005@bppiac.hu>
     [not found]       ` <46F27202.50005@redhat.com>
     [not found]         ` <46F27464.7070909@bppiac.hu>
     [not found]           ` <46F27576.7050002@redhat.com>
     [not found]             ` <46F27F07.8010705@redhat.com>
     [not found]               ` <46F38947.9040709@redhat.com>
     [not found]                 ` <46F38947.9040709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-09-21 10:11                   ` Farkas Levente [this message]
     [not found]                     ` <46F398B9.5070707-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-09-23 11:32                       ` [et-mgmt-tools] ANNOUNCE: virt-top 0.3.2.7 released Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46F398B9.5070707@bppiac.hu \
    --to=lfarkas-lwvwdrzso4ghxe+lvdladg@public.gmane.org \
    --cc=et-mgmt-tools-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.