[Bug Report] VM which is not detected as VM (VM Name: Xen)

Hi

Somehow we can activate Product Key with “Allow VM” is off.
Is it known issue? Can you readjust VM detection algorithm to detect such machine as well?

The details are following:

According to systeminfo the VM type is “Xen”
http://www.ibm.com/developerworks/cloud/library/cl-hypervisorcompare-xen/

System Manufacturer: Xen
System Model: HVM domU
BIOS Version: Xen 4.6.1-xs131112, 11/11/2016

systeminfo:

Host Name: FTC1
OS Name: Microsoft Windows Server 2012 R2 Standard
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server
OS Build Type: Multiprocessor Free
Registered Owner: NetworkLayer
Registered Organization: NetworkLayer
Product ID: 00252-70000-00000-AA535
Original Install Date: 12/21/2016, 9:30:23 PM
System Boot Time: 12/21/2016, 6:08:02 PM
System Manufacturer: Xen
System Model: HVM domU
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2600 Mhz
BIOS Version: Xen 4.6.1-xs131112, 11/11/2016
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-06:00) Central Time (US & Canada)
Total Physical Memory: 4,092 MB
Available Physical Memory: 2,799 MB
Virtual Memory: Max Size: 5,500 MB
Virtual Memory: Available: 4,273 MB
Virtual Memory: In Use: 1,227 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Logon Server: \\FTC1
Hotfix(s): 302 Hotfix(s) Installed.
Network Card(s): 2 NIC(s) Installed.
[01]: XenServer PV Network Device
Connection Name: PublicNetwork-A
DHCP Enabled: No
IP address(es)
[01]: 158.85.210.75
[02]: fe80::498f:de6e:3f4a:6cba
[02]: XenServer PV Network Device
Connection Name: PrivateNetwork-A
DHCP Enabled: No
IP address(es)
[01]: 10.122.166.7
[02]: fe80::f194:2812:3208:3d21
Hyper-V Requirements: A hypervisor has been detected. Features required for
Hyper-V will not be displayed.

Thanks for reporting. Xen is mostly used for Linux, so it is currently detected in Linux only. We will add it to the list of Windows VMs

Thanks! Please let us know ETA for the changes.

Why is detection different per target OS?
Also, can current VM detection algorithm detect VM which does not exist right now? (i.e. is detection algorithm specific per VM, or generic)

VM detection can’t be generic, as their are so many vendors who manufacturer pc’s for Windows, unlike Mac. Every VM has some unique signature, will provide you a list for Windows.

Got it. Thanks!

Just a one more related question.

You just mentioned there’s no generic way to detect.
That means, in the future, when new VM is created, it may not be detected by current LexActivator module.

And. that version of our software which includes current LexActivator can be activated on that specific VM until we provide the new version of our software with new LexActivator module, correct?

Yes, but creating a VM software is not easy, expecting a completely new VM now is very rare, especially after the advent of dockers.

Sounds like I don’t need to worry too much about that case, then.

Please let us know ETA for the changes (supporting XEN detection in Windows)

It will be added in v2.5 end of December.

Thanks!