Rudder

I have the same issue with KVM VMs.
Can be detected via BIOS "Name" (not vendor iirc) KVM.

Didn't remember to report but now I feel those could be related.

Thanks for reporting. We will check if it was corrected upstream and/or correct it.

Could you already send us the "dmesg" output (at least anything talking about virtual machine :).

Thanks,

From Florian's file, dmseg contains the line VMware vmxnet3 virtual NIC driver, but we match VMware vmxnet virtual NIC driver.
So i'm at least fixing this one

Nicolas CHARLES wrote:

From Florian's file, dmseg contains the line VMware vmxnet3 virtual NIC driver, but we match VMware vmxnet virtual NIC driver.
So i'm at least fixing this one

Hello Nicolas,

On my side, I have a mix of vmxnet3 and e1000 NICs. Could it be possible to check the MAC addresses vendors instead?

Alexandre Anriot wrote:

Nicolas CHARLES wrote:

From Florian's file, dmseg contains the line VMware vmxnet3 virtual NIC driver, but we match VMware vmxnet virtual NIC driver.
So i'm at least fixing this one

Hello Nicolas,

On my side, I have a mix of vmxnet3 and e1000 NICs. Could it be possible to check the MAC addresses vendors instead?

Hello Alexandre

Could you send me the output of dmesg | grep VMware, plus the inventories that are not correctly detected (they may contain sensitive data, so you can send them to me by mail directly)

see http://forge.fusioninventory.org/issues/3046

Hello Nicolas,

Here is the output:

[ 1.826215] VMware PVSCSI driver - version 1.0.5.0-k
[ 1.833681] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI
[ 1.871532] scsi0 : VMware PVSCSI storage adapter rev 2, req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254
[ 1.871630] vmw_pvscsi 0000:03:00.0: VMware PVSCSI rev 2 host #0
[ 1.872060] scsi 0:0:0:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2
[ 2.003886] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
[ 2.012616] scsi 2:0:0:0: CD-ROM NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5
[ 94.879284] systemd[1]: Detected virtualization 'vmware'.

Nicolas CHARLES wrote:

Hello Alexandre

Could you send me the output of dmesg | grep VMware, plus the inventories that are not correctly detected (they may contain sensitive data,
so you can send them to me by mail directly)

Alexandre Anriot wrote:

Hello Nicolas,

Here is the output:

[ 1.826215] VMware PVSCSI driver - version 1.0.5.0-k
[ 1.833681] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI
[ 1.871532] scsi0 : VMware PVSCSI storage adapter rev 2, req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254
[ 1.871630] vmw_pvscsi 0000:03:00.0: VMware PVSCSI rev 2 host #0
[ 1.872060] scsi 0:0:0:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2
[ 2.003886] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
[ 2.012616] scsi 2:0:0:0: CD-ROM NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5
[ 94.879284] systemd[1]: Detected virtualization 'vmware'.

Awesome, so propoed fix will detect the "VMware vmxnet3 virtual NIC driver" line, and node will be detected as Virtual

Great, thanks. ;-)

Nicolas CHARLES wrote:

Awesome, so propoed fix will detect the "VMware vmxnet3 virtual NIC driver" line, and node will be detected as Virtual