Bug #8953
closed
Virtual machines considered as physical nodes
Added by Alexandre Anriot almost 9 years ago.
Updated over 8 years ago.
Category:
Web - Nodes & inventories
Description
Hello,
I don't know if it's related to #7204 or not but I have some Debian 8 VMs which are detected as physical nodes:
General
- Hostname: XXXXXX.YYYYYY.ZZZZZZ
- Machine type: Physical machine
- Manufacturer: VMware, Inc.
- Total physical memory (RAM): 3.87 GB
- Total swap space: 4 GB
- Motherboard UUID: cf52a288-84b9-b647-2c32-XXXXXXXXXXXX
- System Serial Number: VMware-42 27 3a 64 02 76 f8 77-5b 36 a0 4d 00 XX XX XX
Operating system details
- Operating System: Debian GNU/Linux 8.5 (jessie)
- Operating System Type: Linux
- Operating System Name: Debian
- Operating System Version: 8.5
- Operating System Service Pack: None
- Operating System Architecture Description: x86_64-linux-thread-multi
The issue is not very urgent for us, as we are using the manufacturer field to build a dynamic group, because of:
[[https://www.rudder-project.org/redmine/issues/6972]]
Cheers,
- Subject changed from Virtual machines considered as "physical" ones to Virtual machines considered as "physical" nodes
- Subject changed from Virtual machines considered as "physical" nodes to Virtual machines considered as physical nodes
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,
- Category set to Web - Nodes & inventories
- Assignee set to Nicolas CHARLES
- Target version set to 3.1.14
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)
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1059
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
- Related to Bug #9049: Some KVM virtual machines considered as physical nodes added
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.15/14 and 3.2.8/7 which were released today.
Also available in: Atom
PDF
Updated by Alexandre Anriot almost 9 years ago
Updated by 
Updated by François ARMAND almost 9 years ago
Updated by Nicolas CHARLES almost 9 years ago
Updated by