Rudder

Hello Ilan,

This looks a lot like http://www.rudder-project.org/redmine/issues/9052

Can you upload the inventory (it may contain sensitive information, so I understand if it's not possible)?
To debug this issue, do you have a file /var/log/dmesg, with any relevant content in it (actually, the content of dmesg), or simply "(Nothing has been logged yet.)" ?
In the inventory, what is the content of BIOS/SMANUFACTURER entry ?

Kind regards,
Nicolas

Hello Nicolas,

Here is the Bios part of inventory :
<BIOS>
<ASSETTAG /> <BDATE>04/01/2014</BDATE>
<BMANUFACTURER>SeaBIOS</BMANUFACTURER>
<BVERSION>1.9.1-5.el7</BVERSION>
<MMANUFACTURER /> <MMODEL /> <MSN /> <SKUNUMBER /> <SMANUFACTURER>Red Hat</SMANUFACTURER>
<SMODEL>OpenStack Compute</SMODEL>
<SSN>e1622fe8-eb7d-44d0-a2d5-7ce6991b2120</SSN>
</BIOS>

Dmesg is already in attachment to this issue, maybe is not what you expect ?

Thansk

Hello Ilan,

For dmesg, I need to be sure if you have actual content in file /var/log/dmesg, or if it's an empty file, because based on the dmesg you sent, it should be correctly detected as QEMU/KVM

Kind regards

Ilan,

I fail to reproduce it - it may have been fixed by https://www.rudder-project.org/redmine/issues/9763
Could you check with an agent in version 4.1 final to see if it still happen ?

Kind regards,
Nicolas

Hi Nicolas,

I have checked with agent 4.1.1 and it is the same problem.

Machine type is "physical"

Best regards,

Ilan

File /var/log/dmesg is empty on debian 8 - causing invalid detection
see https://github.com/fusioninventory/fusioninventory-agent/pull/594