[Fusioninventory-user] Container OpenVZ (Proxmox) and UUID

Ahmed, Fnu S FSAHMED at beckman.com
Mon Jul 13 15:38:23 UTC 2015

These are the commands
ps -ef | grep fusion
root     19647     1  0 14:04 ?        00:00:00 /usr/bin/perl /usr/bin/fusioninventory-agent --server=http://xxxx /glpi/plugins/fusioninventory --user=glpi --password=glpi --basevardir=/var/log/fusioninventory-agent -stdout
After this, when I start the service fusioninventory start, it says that it is running. But, cannot see the module in the agent management module. If it is communicating, what is it communicating with? Also the URL http://xxx /glpi/plugins/fusioninventory takes me to the not found page and " The requested URL /glpi/plugins/fusioninventory/front/wizard.php was not found on this server." Page. Is it possible for you to check  and set everything right remotely? Or else, please advice what to do. Please help.


-----Original Message-----
From: Fusioninventory-user [mailto:fusioninventory-user-bounces+fsahmed=beckman.com at lists.alioth.debian.org] On Behalf Of Guillaume Rousse
Sent: Friday, July 10, 2015 1:57 PM
To: fusioninventory-user at lists.alioth.debian.org
Subject: Re: [Fusioninventory-user] Container OpenVZ (Proxmox) and UUID

Le 03/06/2015 16:28, Guillaume Rousse a écrit :
> Le 02/06/2015 12:26, Guillaume Rousse a écrit :
>> So I'd rather first define our expected semantic first, before
>> asserting anyone practice if wrong, and here is my suggested definition:
>> - HARDWARE/UUID should be physical host identifier, unique among all
>> other physical hosts (and should eventually get renamed as
>> - HARDWARE/VMID should be virtual host identifier, unique among all
>> other virtual hosts from the same hypervisor only (and should
>> eventually get renamed as VIRTUAL_HOST_ID)
> So, is HARDWARE/UUID supposed to be a physical host identifier or a
> global host identifier ?
> In the first case, it should be unique among physical hosts only,
> virtual hosts should have same UUID than their physical host, and
> should change UUID when they are migrated to another physical host.
> In the second case, it should be unique among all hosts (either
> physical or virtual), but what's the usefulness of additioanl
> virtual-machine specific HARDWARE/VMID identifier ?

After some discussion with other developpers, we agreed on the following
- ensure HARDWARE/UUID is really unique among all machines, either physical or virtual
- drop HARDWARE/VMID as confusing
- ensure hosts know their guests UUIDs, to allow relationships to be established on GLPI

Our specification
has been updated, and the following commits implements the change:

Please test those changes, if possible.

Fusioninventory-user mailing list
Fusioninventory-user at lists.alioth.debian.org
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

More information about the Fusioninventory-user mailing list