Hi,
we have a problem with the following installation:
we have a system that’s a compute node in an Openstack test installation.
Now on this machine we decided to install Ganglia, to check it’s monitoring
capabilities regarding virtual machines hosted on that node by Openstack.
We then proceeded
Hello,
On an OpenStack node you may be able to use libxenstore instead of libvirt.
You'll need to recompile hsflowd to try this. Looking at
trunk/src/Linux/Makefile it appears to look for libvirt first, but you can
override that by compiling hsflowd like this:
make clean
make LIBVIRT=no
Th
Hi Neil,
thanks for the suggestion.
I tried to do it. After recompiling hsflowd i checked the files it had open
and it showed:
hsflowd 30019 nobody mem REG 251,3 84728
927248 /usr/lib/libxenctrl.so.3.2.0
hsflowd 30019 nobody mem REG
try having soft links using ln command, may or may not work though :)
ln -s
On Wed, Aug 17, 2011 at 4:17 PM, Emanuele Verga
wrote:
> Hi Neil,
> thanks for the suggestion.
> I tried to do it. After recompiling hsflowd i checked the files it had open
> and it showed:
> hsflowd 30019 nobody
I don't think the soft-links will work, but try this:
1) go back to compiling hsflowd for libvirt.
2) using virt-manager or equivalent, tell it about the "storage pool" of type
"filesystem directory" at /var/lib/nova/instances.
See details here:
http://virt-manager.org/page/StorageManagement
(
>
> Ok, I tried linking one of the disk files to the default storage pool
> folder and it actually detected the linked volume in libvirt:
>
After issuing a *virsh pool-refresh default *the disk was correctly detected
and reported as a volume by *virsh vol-list default, *but there is a
problem:
Th
On Aug 18, 2011, at 1:35 AM, Emanuele Verga wrote:
> Ok, I tried linking one of the disk files to the default storage pool folder
> and it actually detected the linked volume in libvirt:
>
> After issuing a virsh pool-refresh default the disk was correctly detected
> and reported as a volume b
Hi Neil,
Yes that's possible, the problem is Nova places each image in a separate
folder (/var/lib/nova/instance/INSTANCENAME/), so we would have to create a
new pool with the corresponding path each time a new instance is created,
and if we start to add more servers it quicly becomes impractical.
Hi, I downloaded and installe hsflowd trunk revision 226 but using hsflowd
I keep seeing virStorageLookupByPath errors, and VM disk statistics aren't
displayed. Do I need to tell hsflowd explicitly to use target="vda" call? If
yes, how?
Thanks in advance,
Emanuele
2011/8/25 Emanuele Verga
> H
Sorry, the failure of virStorageLookupByPath() was preventing
virDomainBlockStats() from being attempted.
I checked in a fix for this, and also code to try the newer
virDomainGetBlockInfo() call as a fallback should virStorageLookupByPath()
fail. This call only came in with libvirt version 0
Hi Neil,
thanks a lot for the help!
I verified libvirt version, it's 0.8.8
I've dowloaded and compiled hsflowd revision 227: now ganglia correctly
receives and processes statistics VM Bytes Written and VM Writes.
(http://imageshack.us/f/846/vmstats.png/)
Other disk statistics for VM ( VM Bytes
On Aug 31, 2011, at 8:15 AM, Emanuele Verga wrote:
> Hi Neil,
> thanks a lot for the help!
>
> I verified libvirt version, it's 0.8.8
>
> I've dowloaded and compiled hsflowd revision 227: now ganglia correctly
> receives and processes statistics VM Bytes Written and VM Writes.
> (http://ima
12 matches
Mail list logo