Go-Que offers news and technical knowledge articles from all IT visualization software brands. Go-que is sponsored by &

Restrictions running Hyper-V under W10 Professional x64?

Please help me understand the restrictions applicable to running under W10 Professional x64.  Some users are trying to run Hyper-V under W10 and it does not seem to support either more than one socket or more than 64 logical processors.

Please notice that this SS from the VM running  W10 Professional x64 as the host and guest.  Cinebench on a 64/128 core/thread AMD 3990X.  The VM recognizes all 128 threads (logical processors) but only runs half.  Can this be changed
with a setting or will it work in W10 Professional x64 for Workstation or Windows Server?  Thanks and enjoy, John.

Read full post . . . .

Cannot enable the Promiscuous mode at Virtual switch for spanning port


How to enable Promiscuous mode at Virtual machines (Hyper-V) windows 2019 server

What the power shell command and version to run this command please?



Read full post . . . .

Windows Admin Center cannot connect to hyper v core 2019

I need help connecting to Windows server core 2019, I currently have Hyper-v core 2019 installed on a dell server, then install the windows admin center tool on another computer, using Windows 10 , when running the windows admin center application to connect
to hyper-v core, the following error message

"WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default,
the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.

Thanks for your support

Read full post . . . .

Windows 2012r2 Hyper-V Generation 2 firmware boot order No boot entries are configure

I have 2 host HyperV which configure in cluster. Inside the host there are multiple virtual machine. When I try to create new virtual machine usung Generation 2, its firmware boot order shows " No boot entries are configure". How to solve this
issues without break the failover cluster configuration? For your information, all virtual machine inside the host are production.


Read full post . . . .

Windows 2019 Hyper-V Host Static or Dynamic ram allocation

We are setting up a Windows 2019 Hyper-V VM running on a Physical Windows 2019 Server with 64GB of Ram. The Physical server will be running a few lightweight apps and also the Hyper V roles. I have been reading up on Dynamic V’s Static memory allocation
for the Hyper-V server and cannot decide which option is better. As I see it I have 2 ways I could go -

1. Allot 32GB of static ram to the Windows 2019 Hyper-V VM

2. Enable Dymanic Ram Set 8GB of Ram as a minimum Value, Set the Max Ram to 32GB with a 20% Memory buffer

We are planning to use the Hyper V for lightweight Remote desktop use.

What I am wondering is, does having Dynamic Memory instead of static cause speed issues for the VM when the amount of RAM required has to be increased or is this so fast that it is not noticeable.

Any thoughts would be appreciated 

Read full post . . . .

When converted vhd is attached, hyper-v vm does not boot. Even not from ISO

I have been rolling out Hyper-V hosts and creating Hyper-V VM’s for quite a while now. Everything fine, until this case. I need some greater minds to shed some light on this. 

I need to convert a running Windows 2008 R2 server with 8 GB RAM into a Hyper-V VM. We need this machine so we can run a specific old software (from time to time), and the physical machine is acting up. My Hyper-V host runs Windows 2019 Hyper-V host, has
enough physical RAM (16 GB). It has been used to create and run all kinds of VM’s (Windows 2008 server -> Windows 2019 server), Windows 10 etc.. Never failed. RAID 10 on harddisks and enough room.

I have tried a few ways to create the VHD file for this running server. Straight from the server with disk2vhd, and from system recovery backups created by Veritas Back-up Exec System Recovery (tried a few versions of the software). My VHD’s contain all
the files I see on the real server, and the real server has only one partition. No hidden partitions (checked with diskpart). 

The VM I create has the same amount of RAM as the real one, Generation 1. When I attach an iso to it, with the Windows 2008 R2 boot disk, it boots just as expected. Once I attach the VHD to it, it never boots. Black screen, blinking cursor (if the VHD is
the first boot drive), sentence showing I need to push any key to start booting from DVD if the DVD is the first boot device. But the VM does not boot. Once I disconnect the VHD, the same VM boots fine. 

Tried creating a blank VHD for the same VM: VM boots fine. 

I have never has this experience with Hyper-V and none of my Google searches bring this scenario up. Any ideas? 

Next up I will try a competitive system to boot the VHD.

Kind regards,

Wouter Pinkhof


Wouter Pinkhof PINKH bvba,

Read full post . . . .

Top 20 articles for vRealize products, June 2020

Read full post . . . or

Cumulative Update for vRealize Automation 7.6 Cumulative Update for vRealize Automation 7.5 Cumulative Update for vRealize Automation 8.0.1 Cumulative Update for vRealize Automation 7.4 Network port diagram for vSphere 6.x Cumulative Update for vRealize Orchestrator 7.6 Troubleshooting VMRC connectivity in vRealize Automation How to reset the root password in vRealize Log Insight Mapping vRA 8.x

The post Top 20 articles for vRealize products, June 2020 appeared first on VMware Support Insider.

Top 20 articles for NSX, June 2020

Read full post . . . or

After upgrade to 6.4.5 or later, LB doesn’t give an option to not select Service certificates under Server SSL NSX-T Edge cannot enter/exit Maintenance Mode Steps to recover if ESXi 7.0 NSX kernel module are not installed after ESXi upgrade Flow fails to display in the UI when system memory gets overloaded NSX Manager logs

The post Top 20 articles for NSX, June 2020 appeared first on VMware Support Insider.

Failover Cluster Shared Volume Failing IO Error – Help!

So, needed to reboot a cluster yesterday and drained roles from one server, rebooted, moved roles over and rebooted other. However, now one of the CSV is showing as failed. It is not ReadOnly, I have tried in the Server Manager to attach the disk and get an
Access Denied error, tried via powershell as admin and get the same error. any advise? Tried to change the IsManualAttached as well get access denied for that too.

  • Usage : Other
  • NameFormat :
  • OperationalStatus : Detached
  • HealthStatus : Unknown
  • ProvisioningType : Fixed
  • ParityLayout : Unknown
  • Access : Read/Write
  • UniqueIdFormat : Vendor Specific
  • DetachedReason : By Policy
  • WriteCacheSize : 0
  • ObjectId : {1}SERV-HC-01root/Microsoft/Windows/Storage/Providers_v2SPACES_VirtualDisk.Objec tId="{533570b8-ec7e-4e22-XXXb-e6519f296089}:VD:{352a1d48-XXX2-11ea-80be-2477710262
  • PassThroughClass :
  • PassThroughIds :
  • PassThroughNamespace :
  • PassThroughServer :
  • UniqueId : 111E2A35A23EEA11XXX6E9610262D
  • AllocatedSize : 23991687315456
  • FootprintOnPool : 47983374630912
  • FriendlyName : SERV-HDD-VDISK01
  • Interleave : 262144
  • IsDeduplicationEnabled : False
  • IsEnclosureAware : False
  • IsManualAttach : True
  • IsSnapshot : False
  • LogicalSectorSize : 512
  • Name :
  • NumberOfAvailableCopies :
  • NumberOfColumns : 6
  • NumberOfDataCopies : 2
  • OtherOperationalStatusDescription :
  • OtherUsageDescription :
  • PhysicalDiskRedundancy : 1
  • PhysicalSectorSize : 4096
  • RequestNoSinglePointOfFailure : False
  • ResiliencySettingName : Mirror
  • Size : 23991687315456
  • UniqueIdFormatDescription :
  • PSComputerName :
  • CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDisk CimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace…} CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Read full post . . . .

Loss internet connection after restart

I did lose my internet connection in VM (centOS 7) after I restart my PC (windows 10). 

I have created this network through virtual switch- type internal - connection type internal and it was working fine. But after I restarted my PC it doesn’t work.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 16 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995