VirtualBox

Changes between Version 2 and Version 3 of Ticket #9046, comment 2


Ignore:
Timestamp:
Feb 18, 2019 2:47:21 PM (5 years ago)
Author:
EKuser

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9046, comment 2

    v2 v3  
    1 Is this ticket being worked? This issue is also a show-stopper for me ... unable to use VirtualBox because it does not show the processor id in Windows 10. To prove this, open Windows PowerShell, and type:
    2 Get-WmiObject -Query "Select processorId from Win32_Processor"
    3 
    4 It is empty. I have tried vboxmanage to add eax-edx registers, etc. The Windows Device Manager shows the CPU entered via vboxmanage, but the PowerShell command above does not.
    5 
    6 I am running the Windows client virtualbox on a MacOSX host with Hyper-V paravirtualization enabled.
     1Deleted

© 2023 Oracle
ContactPrivacy policyTerms of Use