I am planning to test install the latest Hyper-V core on a DELL R6415

( 17763.557.190612-0019.rs5_release_svc_refresh_SERVERHYPERCORE_OEM_x64FRE_en-us ) 

I do notice that there is a known issue mentioned with recent DELL EPYC servers, to wit :

"

To
install Windows Server 2016 RTM using the operating system (OS) installation media:

1. Press F2 during the POST to access System Settings and disable Virtualization Technology in the Processor settings.
2. Install Windows Server 2016 with the OS installation media.
3. Apply the latest Update Rollup via Windows Update. Windows Server 2016 RTM requires a hotfix (available on June 2017 Update Rollup and later) for a known AMD IOMMU issue. Deployments after Windows Server version 1709 no longer need this hotfix.
4. Go to System Settings (F2 during the POST) and enable Virtualization Technology in the Processor settings.

"

Is it safe to assume that this is already fixed in 17763.557.190612-0019.rs5_release ??

Has anybody here successfully  installed Hyper-V2019 on an EPYC server?

TIA!

Read full post . . . .

Hello,

Our backup team is reporting issues backing up two servers.  When checking the servers I am unable to take new checkpoints from either HyperV manager or SCVMM.  From HyperV manager if I go to settings and change the checkpoint type from Production
to Standard I am able to take checkpoints, however the backups are still failing.

I’m fairly certain that the issue is related to the fact that even though the VM does not appear to have a checkpoint if I look at the properties of VM it appears that the first disk does not have a checkpoint while the other two do:

Is there a way to force these checkpoints to merge?

Read full post . . . .

Hi,

IP address is set on Hyper-V host machine. When I try to query it using the following SCVMM command, IPAddress field in the adapters is empty.

 Get-SCHostNetworkAdapter -VMHost $vmRef.VMHost 

Has anyone faced this issue earlier? Is there any way to fix this issue? 

Thanks,

Priya

Priya

Read full post . . . .

I have a 2019 server (new clean install) and am trying to install wsus from the server manager gui.

All goes well until post installation tasks and I get: "Fatal Error: Failed to start and configure the WSUS service"

When I look at the log I see (amongst other things):

2019-08-16 09:47:33  CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.GetServerVersion()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
2019-08-16 09:47:33  StartServer encountered errors. Exception=The request failed with HTTP status 503: Service Unavailable.
2019-08-16 09:47:33  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service

Any ideas?

regards

roga

Read full post . . . .

Hi all,

Hoping someone may have ideas on how to resolve this one!  We have a 2-node cluster (HPE ProLiant DL360 Gen10) built on Windows 2019 Standard GUI, iSCSI to Nimble storage.  All validation tests pass with flying colors!  When we were testing,
i.e. with very little load we had one instance of a 2019 VM (vm version 9) which got stuck in a ‘stopping-critical’ state when rebooting.  At this point, the host has gone ‘awol’ with cluster functions, from then on any cluster operation failed until
the host is rebooted (draining would never finish, any other live migration times out and fails).  We found that we had a switch down so put it down to that (even though redundant paths were AOK).  Since then it has been working beautifully as expected,
I’ve done plenty of migrations, draining of hosts without issue, until yesterday.  The client decided to patch a Window 7 VM, it rebooted and got stuck in the same fashion, Stopping-Critical.  I have tried the trick of killing the VM process, this
does not work in this scenario.  There is nothing we can do except cold boot the server, forcing failover to the other host.  Obviously a bit of an issue as the 30 servers now running on there restart on the other host, interrupting file / print
services etc.

I’ve read about disabling VMQ but I really don’t want to go disabling the advanced performance features unless we absolutely have to.  I am using Dynamic memory on most of the machines, otherwise pretty standard configurations.

No issues with resource we are using under half memory on both hosts.

Any ideas?

Thanks,
Simon

Read full post . . . .

Hi all,

Hoping someone may have ideas on how to resolve this one!  We have a 2-node cluster (HPE ProLiant DL360 Gen10) built on Windows 2019 Standard GUI, iSCSI to Nimble storage.  All validation tests pass with flying colors!  When we were testing,
i.e. with very little load we had one instance of a 2019 VM (vm version 9) which got stuck in a ‘stopping-critical’ state when rebooting.  At this point, the host has gone ‘awol’ with cluster functions, from then on any cluster operation failed until
the host is rebooted (draining would never finish, any other live migration times out and fails).  We found that we had a switch down so put it down to that (even though redundant paths were AOK).  Since then it has been working beautifully as expected,
I’ve done plenty of migrations, draining of hosts without issue, until yesterday.  The client decided to patch a Window 7 VM, it rebooted and got stuck in the same fashion, Stopping-Critical.  I have tried the trick of killing the VM process, this
does not work in this scenario.  There is nothing we can do except cold boot the server, forcing failover to the other host.  Obviously a bit of an issue as the 30 servers now running on there restart on the other host, interrupting file / print
services etc.

I’ve read about disabling VMQ but I really don’t want to go disabling the advanced performance features unless we absolutely have to.  I am using Dynamic memory on most of the machines, otherwise pretty standard configurations.

No issues with resource we are using under half memory on both hosts.

Any ideas?

Thanks,
Simon

Read full post . . . .

Hi,

Server Name : TrustHost: i have 5 VMs, Host window is win 2016

Server Name : TrustHostRep:  host window is win 2012 R2

i had replicated 3 Vms from host to Replica. working perfectly fine that are on Hyper V config 5.0. 

now i’m trying to add another vm on replica that is also on 5.0 config. But i’m facing subjected error.

Any help ? 

Thanks

Read full post . . . .

Hello guys, is there anyway I can recover my Hyper-V VM after accidentally Reverted? I dont have snaps nor backups… I noke a few years ago it was not possible but maybe now there is a way around I have WServer 2016.

Thanks!

Read full post . . . .

EVENT-ID: 1230, 1146 & 1069 

Server 2016 3 Node Cluster. Validation wizard passes. 

When live migrating VMs between host a VM will hang up in a "re-starting" or "processing" mode. The VM does belong to either host and cannot be removed from the Failover Cluster Manger, and doesn’t show on the HyperV manager. The Failover
Cluster Events then cycle the EVENT-ID: 1230, 1146 & 1069 events. All VM on the host become completely unresponsive. 

The only way to correct the cluster is hard shutdown the host server experiencing the Event-IDs. Then import the original VM which began the issues.  

Read full post . . . .

When trying to access Disk management, i am getting a prompt to initialize the disks which are already initialized, i am not able to access Diskpart as well via command prompt.
First, disk management takes forever to open and it gives me a prompt to initialize the disks which were already initialized.

Read full post . . . .