Project

General

Profile

Actions

Bug #7204

closed

Debian Jessie, on VMWare, are wrongly considered as "Physical" machine

Added by Nicolas CHARLES over 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Virtual Debian Jessie with VMWare are considered physical, while they are virtual

The relevant info we should use to correctly detect they are virtual are:

 cat /proc/modules | grep -i vmw
vmw_balloon 12658 0 - Live 0xfXXXXXXXXXXX
vmwgfx 165847 0 - Live 0xfXXXXXXXXXXX
vmw_vmci 55383 0 - Live 0xfXXXXXXXXXXX
ttm 77862 1 vmwgfx, Live 0xfXXXXXXXXXXX
drm_kms_helper 49210 1 vmwgfx, Live 0xfXXXXXXXXXXX
drm 249955 4 vmwgfx,ttm,drm_kms_helper, Live 0xfXXXXXXXXXXX
vmw_pvscsi 21455 1 - Live 0xfXXXXXXXXXXX
scsi_mod 191405 4 sg,sd_mod,vmw_pvscsi,libata, Live 0xfXXXXXXXXXXX

and
 dmesg | grep -i vmw
[    0.000000] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/30/2013
[    0.000000] Hypervisor detected: VMware
[    0.000000] ACPI: XSDT 0x000000007FEF1204 00005C (v01 INTEL  440BX    06040000 VMW  01324272)
[    0.000000] ACPI: SRAT 0x000000007FEF1300 0000B8 (v02 VMWARE MEMPLUG  06040000 VMW  00000001)
[    0.000000] ACPI: HPET 0x000000007FEF12C8 000038 (v01 VMWARE VMW HPET 06040000 VMW  00000001)
[    0.000000] ACPI: WAET 0x000000007FEF12A0 000028 (v01 VMWARE VMW WAET 06040000 VMW  00000001)
[    0.838527] VMware PVSCSI driver - version 1.0.5.0-k
[    0.838900] vmw_pvscsi: using 64bit dma
[    0.839080] vmw_pvscsi: max_id: 16
[    0.839082] vmw_pvscsi: setting ring_pages to 8
[    0.843191] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI
[    0.862914] vmw_pvscsi 0000:03:00.0: irq 72 for MSI/MSI-X
[    0.862974] vmw_pvscsi: using MSI-X
[    0.862994] vmw_pvscsi: device does not support req_threshold
[    0.862995] vmw_pvscsi: driver-based request coalescing disabled
[    0.863047] scsi2 : VMware PVSCSI storage adapter rev 2, req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254
[    0.863100] vmw_pvscsi 0000:03:00.0: VMware PVSCSI rev 2 host #2
[    0.863232] scsi 2:0:0:0: Direct-Access     VMware   Virtual disk     1.0  PQ: 0 ANSI: 2
[    7.194933] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16
[    7.194987] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[    7.195095] vmw_vmci 0000:00:07.7: irq 75 for MSI/MSI-X
[    7.195121] vmw_vmci 0000:00:07.7: irq 76 for MSI/MSI-X
[    7.265442] [drm] Initialized vmwgfx 2.6.0 20140325 for 0000:00:0f.0 on minor 0

Actions #1

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.14 to 2.11.15
Actions #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.15 to 2.11.16
Actions #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.16 to 2.11.17
Actions #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.17 to 2.11.18
Actions #5

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #6

Updated by Nicolas CHARLES about 8 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #7

Updated by Nicolas CHARLES about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/872
Actions #8

Updated by Nicolas CHARLES about 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #9

Updated by Vincent MEMBRÉ about 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.

Actions

Also available in: Atom PDF