Quantcast
Channel: Hyper-V forum
Viewing all 19461 articles
Browse latest View live
↧

Issue replicating - event id 33702

June 27, 2019, 12:59 am
$
0
0

Hi I have 2 servers running 2012R2 that replicate a VM with three VHDs. I started getting this event :

Pending log file size is more than (694493 MB). Change tracking for virtual machine 'COMPUTERNAME' will be disabled since the pending log file size has exceeded its limit. (Virtual machine ID xxxxxxxxxxxx)

The replication never completes it gets to 100% and then starts over. I removed the replication and set it up from scratch exporting initially to USB Media and then importing again. It was successful however I am still getting the same error. I tried Googling the event, which appears in the Hyper-V-VMMS logs, but there is nothing out there. Has anyone seen this before ? I can not see any system event or application log errors both HyperV servers have enough disk space.

Thanks

Bob

Reno Nevada


↧
Search

Importing .ovf and .ova files

June 27, 2019, 6:49 am
$
0
0

I need to import in an Hyper-v server some VMs saved as .ova or .ovf files.

The files were created on a VMware ESXi host.

The files contain Linux VMs and do not contain any VMware tool.

What is the simplest procedure?

Regards

Mario

↧
↧

Error with Windows Hyper-V 2019

June 27, 2019, 1:52 pm
$
0
0

I am seeing an error every time I try to connect to the Windows Hyper-V server.

I have attempted a large number of various solutions, have followed the instructions in this guide, along with changing policies, and working through the potential list of causes as denoted by the error message.

↧

Features on Demand on Hyper-V Server 2019

June 20, 2019, 7:55 am
$
0
0

A Server Core installation of Server 2019 Standard / Datacenter allows 'Features on Demand' to be installed (mmc, event viewer, etc, plus optionalliy IE11). Does anyone know whether it's possible to install the features on the stand-alone (free) Hyper-V Server 2019? I've just tried running the Powershell commands to install them (listed here: https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19) - it reports as completed successfully, but the commands don't seem to be available and a search on the C drive for the relevant .exe files doesn't locate anything.

It may well be that, given that Hyper-V Server is free, the features aren't available - but it would be useful to know for sure.

Thanks

David

↧

Can we restrict the number of VMs that can be created on a single Hyper-V host?

June 27, 2019, 6:55 pm
$
0
0

Dear Experts,

Can we restrict the number of VMs that can be created on a single Hyper-V host?

We have Windows Server 2016 stand alone Hyper-V host and we need to restrict only 45 VMs on the host.

Many thanks...

DevT-MCT

↧
↧

Hyper-V 2019 - Guest VM's shutdown unexpectedly

December 12, 2018, 12:26 am
$
0
0

Hi,

Since upgrading my Hyper-V servers to Windows Server 2019, including KB4471332 from last night, my guest VM's do not power down on restart of the 2019 host.

I can confirm integration components are as up to date as possible, and each guest is configured to shutdown when the host restarts.

Each guest gets the "Why did I shutdown unexpectedly message".

The even viewer yields the following all within 30 seconds of restarting the host:

Shut down physical computer. Stopping/saving all virtual machines...

'ADFS' failed to perform the 'Shutting Down' operation. The virtual machine is currently performing the following operation: 'Shutting Down'. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
'ADFS' failed to shut down. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)

The Update Orchestrator Service service terminated with the following error:
This operation returned because the timeout period expired.

Failed to restore configuration for port 59229EE2-C880-4BF2-9849-89A21EC17772 (Friendly Name: ) on switch 300C0E17-E123-4182-BE62-AAD1860BE841 (Friendly Name: ), status = Object Name not found..

Everything is configured as it was on the 2016 Hyper-V host.

The message ADFS failed to shut down because it is shutting down seems terribly odd to me.  Of course its shutting down, just need the host to wait. (Yes the registry is set to 120 as the default time for the host....)

Fairly simple to recreate....just spin up a 2019 server, install Hyper-V role, throw in a VM and test.

Any help would be appreciated, but my money is on it being another bug.

↧

VmHostAssignableDevice of a PCI device to a 32-bit Guest OS

June 25, 2019, 10:17 am
$
0
0

Hi,

Whenever I try to set over PCI-passhtru a PCI device to a 32 bits Guest VM (Linux Guest, Windows 7 Guest), if the VM is a 32 bit instance, the device is not enumerated and it does not show up into the guest.

For the same hyper-v configuration, but running a 64 bits Guest VM (Linu, Windows 10), then the device is enumerated and the drivers of the VMs can probe it.

Please, why does Hyper-v cares if the VM is 32 bits or 64s for PCI Passthru ? Are they are tuning with Hyper-v PCI enumartion when one needs to leverage PCI-passhtru ?

thank you,

↧

Hyperv OS 2019 vs Veeam vs checkpoints

June 23, 2019, 1:58 am
$
0
0

Hey.

dunno if this is Veeam related problem or hyperv, here's the story.

Hyperv server - 2012 R2 with three VMS (2 linux machines and one OS 2016 VM).

Created a new server OS 2019 with hyperv role installed.

Turned off virtual machines on 2012R2 and live migrated to hyperv 2019.

Installed veeam backup and replication on OS 2019 and configured daily backups of virtual machines.

It works for 2-3 days then it stops working with an error about checkpoints.
I think it's hyperv issue and not veeam issue.
For example if I want to edit disk on a virtual machine it's greyed out stating that checkpoints exists (but there are no checkpoints?!?). Creating checkpoints manually not working, throwing an error.

But if we reboot Hyperv OS 2019 server then everything is OK. On VM settings we can edit the disk (it isn't grayed out more). And backups are running with no problem.


Any clues?

BCR

↧
Search

HyperV: how to attach a vhd/vhdx to VM

June 28, 2019, 3:46 am
$
0
0

Hi Experts,

how to attach the disk (vhd/vhdx) to a given VM using the WMI ?

APIs (WMI or Win32) helps in attaching the disk to hypervisor host and not the VM. Powershell has this capability but i could not find with WMI or Win32. Am I misunderstanding these API set ?

Can you please help to point to the APIs either in WMI or Win32 (virtdisk.dll) ?

-Bala

↧
↧

Cannot PuTTY into Hyper-V VM (Ubuntu 18 server)

June 28, 2019, 5:26 am
$
0
0

An Ubuntu 18.04 server virtual machine in Hyper-V refuses connections via PuTTY. The guest is running & can be pinged from the host (Windows 10, 1903). The server is freshly built from an iso. Openssh-server was installed during installation. The guest's adapter has a static IP address and is configured as an external switch on the host's adapter.

Server shows that it's listening on port 22. PuTTY will connect to remote systems. Using WSL to ssh into the server also results in Connection refused. PuTTY will also connect to VirtualBox VMs when that is used.

What may be a related issue is that after installing Apache2 & browsing to the VM's IP address I get the host (which is used for developing web sites), not the guest.
↧

PLEASE HELP!!!! Trying to enable my Hyper V Manager and Platform... Error "The referenced assembly could not be found."

June 29, 2019, 11:39 pm
$
0
0

PLEASE HELP!!!! Trying to enable my Hyper V Manager and Platform...

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Image Version: 10.0.17134.860
Enabling feature(s)
[==========================100.0%==========================]
Error: 14081
The referenced assembly could not be found.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

-------------------------------------------------------------

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

PS C:\WINDOWS\system32>

DISM Log------

2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll:                                            - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll:                                            - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll: Version 10.0.17134.1 - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll: Parent process command line: "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"  - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Enter DismInitializeInternal - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Input parameters: LogLevel: 2, LogFilePath: C:\WINDOWS\Logs\DISM\dism.log, ScratchDirectory: (null) - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Initialized GlobalConfig - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Initialized SessionTable - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Waiting for m_pInternalThread to start - CCommandThread::Start
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=10464 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=10464 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 m_pInternalThread started - CCommandThread::Start
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Created g_internalDismSession - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Leave DismInitializeInternal - DismInitializeInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Enter DismOpenSessionInternal - DismOpenSessionInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Input parameters: ImagePath: DISM_{53BFAE52-B167-4E2F-A258-0A37B57FF845}, WindowsDirectory: (null), SystemDrive: (null) - DismOpenSessionInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Waiting for m_pInternalThread to start - CCommandThread::Start
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 m_pInternalThread started - CCommandThread::Start
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2019-06-30 14:31:14, Info                  DISM   PID=4596 TID=9952 Scratch directory set to 'C:\Users\Servtop1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2019-06-30 14:31:14, Info                  DISM   PID=4596 TID=9952 DismCore.dll version: 10.0.17134.1 - CDISMManager::FinalConstruct
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   PID=4596 TID=9952 Successfully loaded the ImageSession at "C:\WINDOWS\SYSTEM32\Dism" - CDISMManager::LoadLocalImageSession
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Connecting to the provider located at C:\WINDOWS\SYSTEM32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Warning               DISM   DISM Provider Store: PID=4596 TID=9952 Failed to load the provider: C:\WINDOWS\SYSTEM32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Connecting to the provider located at C:\WINDOWS\SYSTEM32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Connecting to the provider located at C:\WINDOWS\SYSTEM32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Connecting to the provider located at C:\WINDOWS\SYSTEM32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Connecting to the provider located at C:\WINDOWS\SYSTEM32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Connecting to the provider located at C:\WINDOWS\SYSTEM32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Warning               DISM   DISM Provider Store: PID=4596 TID=9952 Failed to load the provider: C:\WINDOWS\SYSTEM32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-06-30 14:31:14, Info                  DISM   DISM FFU Provider: PID=4596 TID=9952 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
[4596] [0x8007007b] FIOReadFileIntoBuffer:(1381): The filename, directory name, or volume label syntax is incorrect.
[4596] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[4596] [0xc142011c] WIMGetMountedImageHandle:(2897)
2019-06-30 14:31:14, Info                  DISM   DISM WIM Provider: PID=4596 TID=9952 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-06-30 14:31:14, Info                  DISM   DISM VHD Provider: PID=4596 TID=9952 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-06-30 14:31:14, Info                  DISM   DISM FFU Provider: PID=4596 TID=9952 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
2019-06-30 14:31:14, Info                  DISM   DISM Imaging Provider: PID=4596 TID=9952 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2019-06-30 14:31:14, Info                  DISM   DISM VHD Provider: PID=4596 TID=9952 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-06-30 14:31:14, Info                  DISM   DISM Imaging Provider: PID=4596 TID=9952 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[4596] [0x8007007b] FIOReadFileIntoBuffer:(1381): The filename, directory name, or volume label syntax is incorrect.
[4596] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[4596] [0xc142011c] WIMGetMountedImageHandle:(2897)
2019-06-30 14:31:14, Info                  DISM   DISM WIM Provider: PID=4596 TID=9952 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-06-30 14:31:14, Info                  DISM   DISM Imaging Provider: PID=4596 TID=9952 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2019-06-30 14:31:14, Info                  DISM   DISM Imaging Provider: PID=4596 TID=9952 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 physical location path: C:\ - CDISMManager::CreateImageSession
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 Event name for current DISM session is Global\{C1C12B84-6439-41DB-939D-20D382922ECB} - CDISMManager::CheckSessionAndLock
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 Create session event 0xbd8 for current DISM session and event name is Global\{C1C12B84-6439-41DB-939D-20D382922ECB}  - CDISMManager::CheckSessionAndLock
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 Successfully loaded the ImageSession at "C:\Users\Servtop1\AppData\Local\Temp\E03F5CC7-1094-49E2-A4CC-EAC6227D213D" - CDISMManager::LoadRemoteImageSession
2019-06-30 14:31:14, Info                  DISM   DISM Image Session: PID=11088 TID=11044 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Connecting to the provider located at C:\Users\Servtop1\AppData\Local\Temp\E03F5CC7-1094-49E2-A4CC-EAC6227D213D\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   DISM OS Provider: PID=11088 TID=11044 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM OS Provider: PID=11088 TID=11044 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM OS Provider: PID=11088 TID=11044 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2019-06-30 14:31:14, Warning               DISM   DISM OS Provider: PID=11088 TID=11044 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Connecting to the provider located at C:\Users\Servtop1\AppData\Local\Temp\E03F5CC7-1094-49E2-A4CC-EAC6227D213D\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-06-30 14:31:14, Warning               DISM   DISM Provider Store: PID=11088 TID=11044 Failed to load the provider: C:\Users\Servtop1\AppData\Local\Temp\E03F5CC7-1094-49E2-A4CC-EAC6227D213D\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:14, Info                  DISM   DISM Manager: PID=4596 TID=9952 Image session successfully loaded from the temporary location: C:\Users\Servtop1\AppData\Local\Temp\E03F5CC7-1094-49E2-A4CC-EAC6227D213D - CDISMManager::CreateImageSession
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 Target image information: OS Version=10.0.17134.860, Image architecture=amd64 - CDismCore::LogImageSessionDetails
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Leave DismOpenSessionInternal - DismOpenSessionInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Session id is: 2 - DismOpenSessionInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Enter DismGetOsInfoInternal - DismGetOsInfoInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Input parameters: Session: 2 - DismGetOsInfoInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Initialized default cancel event - DismGetOsInfoInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Leave DismGetOsInfoInternal - DismGetOsInfoInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Enter DismDeleteInternal - DismDeleteInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Leave DismDeleteInternal - DismDeleteInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Enter DismEnableFeatureInternal - DismEnableFeatureInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Enter DismEnableDisableFeatureInternal - DismEnableDisableFeatureInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Input parameters: Session: 2, EnableFeatureName: Microsoft-Hyper-V, DisableFeatureName: (null), Identifier: (null), PackageIdentifier: 0,                             LimitAccess: 0, SourcePathCount: 0, EnableAll: 0, CancelEvent: 0x0000000000000B7C, Progress: 0x000001691AA373EC, UserData: 0x0000000000000000 - DismEnableDisableFeatureInternal
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=8756 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:14, Info                  DISM   API: PID=4596 TID=9952 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Connecting to the provider located at C:\Users\Servtop1\AppData\Local\Temp\E03F5CC7-1094-49E2-A4CC-EAC6227D213D\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-06-30 14:31:14, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2019-06-30 14:31:14, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_SUCCESS
2019-06-30 14:31:14, Info                  DISM   DISM Package Manager: PID=11088 TID=11044 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2019-06-30 14:31:14, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2019-06-30 14:31:14, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_SUCCESS
2019-06-30 14:31:14, Info                  DISM   DISM Package Manager: PID=11088 TID=11044 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2019-06-30 14:31:14, Info                  DISM   DISM Package Manager: PID=11088 TID=11044 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2019-06-30 14:31:15, Info                  DISM   DISM Package Manager: PID=11088 TID=11044 Initiating Changes on Package with values: 5, 7 - CDISMPackage::Internal_ChangePackageState
2019-06-30 14:31:15, Info                  DISM   DISM Package Manager: PID=11088 TID=11044 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2019-06-30 14:31:17, Info                  DISM   DISM Package Manager: PID=11088 TID=3956  Error in operation: (null) (CBS HRESULT=0x80073701) - CCbsConUIHandler::Error
2019-06-30 14:31:17, Error                 DISM   DISM Package Manager: PID=11088 TID=11044 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073701)
2019-06-30 14:31:17, Error                 DISM   DISM Package Manager: PID=11088 TID=11044 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x80073701)
2019-06-30 14:31:17, Error                 DISM   API: PID=4596 TID=9952 Failed to process features change - CEnableDisableFeatureCommandObject::InternalExecute(hr:0x80073701)
2019-06-30 14:31:17, Error                 DISM   API: PID=4596 TID=9952 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80073701)
2019-06-30 14:31:17, Error                 DISM   API: PID=4596 TID=8756 CEnableDisableFeatureCommandObject internal execution failed - DismEnableDisableFeatureInternal(hr:0x80073701)
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Exit DismEnableDisableFeatureInternal - DismEnableDisableFeatureInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Exit DismEnableFeatureInternal - DismEnableFeatureInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Enter DismGetLastErrorMessageInternal - DismGetLastErrorMessageInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Exit DismGetLastErrorMessageInternal - DismGetLastErrorMessageInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Enter DismDeleteInternal - DismDeleteInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Leave DismDeleteInternal - DismDeleteInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Enter DismCloseSessionInternal - DismCloseSessionInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Input parameters: Session: 2 - DismCloseSessionInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Refcount for DismSession= 2s 0 - CSessionTable::RemoveSession
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=9952 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=9952 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=9952 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=9952 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Package Manager: PID=11088 TID=11044 Finalizing CBS core. - CDISMPackageManager::Finalize
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=11088 TID=11044 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Manager: PID=4596 TID=9952 Closing session event handle 0xbd8 - CDISMManager::CleanupImageSessionEntry
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   DISM Provider Store: PID=4596 TID=9952 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=9952 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Leave DismCloseSessionInternal - DismCloseSessionInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Enter DismShutdownInternal - DismShutdownInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=10464 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=10464 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=10464 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=10464 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2019-06-30 14:31:17, Info                  DISM   PID=4596 TID=10464 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2019-06-30 14:31:17, Info                  DISM   PID=4596 TID=10464 Scratch directory set to 'C:\Users\Servtop1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2019-06-30 14:31:17, Info                  DISM   PID=4596 TID=10464 DismCore.dll version: 10.0.17134.1 - CDISMManager::FinalConstruct
2019-06-30 14:31:17, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=10464 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Deleted g_internalDismSession - DismShutdownInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Shutdown SessionTable - DismShutdownInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 Leave DismShutdownInternal - DismShutdownInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll:                                          - DismShutdownInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2019-06-30 14:31:17, Info                  DISM   API: PID=4596 TID=8756 DismApi.dll:                                          - DismShutdownInternal


↧

Unable to Disable Hyper-V on Windows 10 Version1809

June 30, 2019, 11:17 am
$
0
0

I have been trying to disable Hyper-V on Windows 10 in order to run VMWare and have been unable to.  I continue to get the following error from VMware Workstation 15 Player:
"VMware Player and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Player."

My OS specs:

  • Edition: Windows 10 Pro
  • Version: 1809
  • OS build: 17763.557

I have tried the following:

  • Running these on an elevated CMD:
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Dism.exe /online /Cleanup-Image /StartComponentCleanup
  • sfc /scannow
  • In elevated Powershell:
  • Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

It also recommends reinstalling .NET framework, which did not help.

  • I have disabled all features related to Hyper-V through Programs and Features
  • I have run:
  • Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
  • In an elevated Powershell

This did not work either.

I have tried running:
bcdedit /set hypervisorlaunchtype off

In an elevated Powershell session.  This did not work either.

I can't find any other steps online to disable Hyper-V and I'm completely out of ideas.  Any help would be much appreciated.

↧

Hyper V templates

June 30, 2019, 12:55 pm
$
0
0

Hello team,

Hope you are doing well!

I've faced the follow issue. 

I've created HYPER V templates and i didn't have any problems. But when i trying to deploy it. It's pop us black window without any information and it's seem that windows is not running. Can you please explain me what i'm doing wrong and what i'm missing? 

Thank you in advance!

↧
↧

hyper-v cluster 2016, event id 25, Hyper-V-VmSwitch

April 18, 2018, 6:51 am
$
0
0

I have a cluster, 2 nodes. There are repeating events id 25, every few second:

The MAC address 00-15-5D-AE-25-19 has moved from port 53A6AB28-EBD3-4F72-B690-69406077B8A7 (Friendly Name: vSwitchFN_External) to port 6D5ABBEF-0A8E-4F5D-8CC2-0871846CEF82 (Friendly Name: BCK).

The MAC address 00-15-5D-AE-25-18 has moved from port 53A6AB28-EBD3-4F72-B690-69406077B8A7 (Friendly Name: vSwitchFN_External) to port 9A8780F9-D931-4F85-B087-397A2F718C01 (Friendly Name: HB).

The MAC address 00-15-5D-AE-25-18 has moved from port 9A8780F9-D931-4F85-B087-397A2F718C01 (Friendly Name: HB) to port 53A6AB28-EBD3-4F72-B690-69406077B8A7 (Friendly Name: vSwitchFN_External).

The MAC address 00-15-5D-AE-25-19 has moved from port 6D5ABBEF-0A8E-4F5D-8CC2-0871846CEF82 (Friendly Name: BCK) to port 53A6AB28-EBD3-4F72-B690-69406077B8A7 (Friendly Name: vSwitchFN_External).

Config:

No NLB (MAC spoofing) on VMs.

PS C:\Users\pero>  Get-NetLbfoTeam


Name                   : mgmt
Members                : {M2, M1}
TeamNics               : mgmt-624
TeamingMode            : Lacp
LoadBalancingAlgorithm : Dynamic
LacpTimer              : Fast
Status                 : Up

Name                   : vm
Members                : {K2L1, K1L1}
TeamNics               : vm
TeamingMode            : Lacp
LoadBalancingAlgorithm : Dynamic
LacpTimer              : Fast
Status                 : Up


PS C:\Users\pero> Get-VMNetworkAdapter -ManagementOS

Name          IsManagementOs VMName SwitchName MacAddress   Status IPAddresses
----          -------------- ------ ---------- ----------   ------ -----------
BCK           True                  vSwitchFN  00155DAE2519 {Ok}
HB            True                  vSwitchFN  00155DAE2518 {Ok}
SETswitchSMB2 True                  SETswitch  00155DAE250C {Ok}
SETswitchSMB1 True                  SETswitch  48DF371EFC2D {Ok}
LM            True                  SETswitch  00155DAE250D {Ok}

PS C:\Users\pero> Get-VMSwitch

Name      SwitchType NetAdapterInterfaceDescription
----      ---------- ------------------------------
vSwitchFN External   Microsoft Network Adapter Multiplexor Driver #2
SETswitch External   Teamed-Interface


PS C:\Users\pero> Get-VMNetworkAdapterVlan -ManagementOS

VMName VMNetworkAdapterName Mode   VlanList
------ -------------------- ----   --------
       SETswitchSMB1        Access 1980
       LM                   Access 1981
       HB                   Access 1044
       BCK                  Access 887
       SETswitchSMB2        Access 1979


PS C:\Users\pero> Get-NetAdapter

Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
mgmt-624                  Microsoft Network Adapter Multiplexo...       6 Up           F4-03-43-5C-75-91         2 Gbps
K1L2                      HPE Ethernet 10Gb 2-port 561T Adapter        32 Up           48-DF-37-1F-0F-09        10 Gbps
K1L1                      HPE Ethernet 10Gb 2-port 561T Adap...#4      30 Up           48-DF-37-1F-0F-08        10 Gbps
SMB2                      Hyper-V Virtual Ethernet Adapter #5          35 Up           00-15-5D-AE-25-0C        20 Gbps
SMB1                      Hyper-V Virtual Ethernet Adapter #4          11 Up           48-DF-37-1E-FC-2D        20 Gbps
LM1                       Hyper-V Virtual Ethernet Adapter #3          16 Up           00-15-5D-AE-25-0D        20 Gbps
BCK1                      Hyper-V Virtual Ethernet Adapter #2          27 Up           00-15-5D-AE-25-19        10 Gbps
HB1                       Hyper-V Virtual Ethernet Adapter             19 Up           00-15-5D-AE-25-18        10 Gbps
M2                        Broadcom NetXtreme Gigabit Ethernet #3       20 Up           F4-03-43-5C-75-91         1 Gbps
M1                        Broadcom NetXtreme Gigabit Ethernet          24 Up           F4-03-43-5C-75-90         1 Gbps
vm                        Microsoft Network Adapter Multiple...#2      17 Up           48-DF-37-1E-FC-2C        20 Gbps
K2L2                      HPE Ethernet 10Gb 2-port 561T Adap...#2      15 Up           48-DF-37-1E-FC-2D        10 Gbps
K2L1                      HPE Ethernet 10Gb 2-port 561T Adap...#3      18 Up           48-DF-37-1E-FC-2C        10 Gbps

The events intensively fill the log and sometimes network connectivity for these virtual adapters (BCK, HB) is temporary lost.

What is problem?

↧

Best practice iSCSI server configuration with hyperv (Windows 2012 and 2016)

June 30, 2019, 6:51 pm
$
0
0
Hi,

I have always used good common practices, but I have found some options that I do not know and I would like the help to confirm with you.

1 - Disable all NIC options, leaving only IPV4;
2 - Disable the options to register in DNS and Netbios;
4 - Set MTU to 9000 in advanced settings;
5 - Disable VMQ in the advanced settings;

New information I found. Are they really necessary?

Click on the Advanced tab under the NIC properties and set the following attributes' values ​​to Disabled:

- IPv4 Checksum Offload
- IPv4 TSO Offload
- Large Send Offload V2 (IPV4)
- Large Send Offload V2 (IPV6)
- Offload IP Options
- Offload tagged traffic
- Offload TCP Options
- Recv Segment Coalescing (IPV4)
- Recv Segment Coalescing (IPV6)
- TCP Checksum Offload (IPv4)
- TCP Checksum Offload (IPv6)
- UDP Checksum Offload (IPv4)
- UDP Checksum Offload (IPv6)

New Dell recommendation information

https://downloads.dell.com/manuals/all-products/esuprt_software/esuprt_it_ops_datcentr_mgmt/general-solution-resources_white-papers3_en-us.pdf

Note: Recommended registry settings apply to all versions of Windows Server unless directly specified.
HKLM \ SYSTEM \ CurrentControlSet \ Services \ mpio \ Parameters
- PDORemovePeriod
- PathRecoveryInterval
- UseCustomPathRecoveryInterval
etc...

Note: The registry settings in Table 6 only apply to Windows Server 2012 or later
HKLM \ SYSTEM \ CurrentControlSet \ Services \ mpio \ Parameters
- DiskPathCheckDisabled
- DiskPathCheckInterval

I do not understand what you mean by (single-path). Should these settings only be applied for single-path communication? If I have use (multi-path) should not we configure?

This appendix contains recommended changes for iSCSI initiators. These changes apply to single-path and MPIO configurations that use iSCSI to connect to SC Series storage.
HKLM \ SYSTEM \ CurrentControlSet \ Control \ Class \ {4D36E97B-E325-11CE-BFC1-08002BE10318} \ <Instance Number> \ Parameters

HKLM \ SYSTEM \ CurrentControlSet \ Services \ Tcpip \ Parameters \ Interfaces \ <SAN Interface GUID>
- TcpAckFrequency
- TcpNoDelay

Should this setting be used only for 10GbE configuration?

- Enable RFC1323 timestamps (TCP High Performance Extensions)
netsh int tcp set global timestamps = enabled
HKLM \ SYSTEM \ CurrentControlSet \ Services \ TCPIP \ Parameters \ Tcp1323Opts

- Disable Nagle's Algorithm
- Disable NIC Interrupt Modulation

For Windows 2012 and R2 you need to apply KBs. What to say that for 2016 does not need? Just ensure that all the updates have been installed?

Recommended updates and hotfixes for Windows Server 2012
R2 / 2016 Microsoft publishes updates for Windows Server 2012 R2 and Windows Server 2016 cumulatively. Any updates for storage-related files are included in the monthly cumulative updates. Apply the latest monthly cumulative update from Microsoft to ensure that the storage-related files msdsm.sys, mpio.sys, msiscsi.sys,
and storport.sys stay current.
See the Microsoft Update Catalog at
 https://www.catalog.update.microsoft.com/Home.aspx to locate specific KB downloads.

Thank you.
↧
Search

Windows Server 2019 Hyper-V: An error occurred while attempting to connect to server

June 30, 2019, 9:52 pm
$
0
0

I have a big problem and I hope someone can help me fix it.

I have an HP ProLiant ML150G6 server with a RAID array, running Windows Server 2019 and the Hyper-V role. I use the server to run my router (pfsense) and vpn server and also to run test development versions of pfsense and opnsense with various virtual switches and guests. I recently installed Windows Server 2019. It was previously running Windows Server 2012R2.) It was a clean installation. The server does not have any other roles installed.

Everything was working perfectly for a couple of weeks until I installed HP System Management Homepage (so i would have visibility of the RAID array). SMH appears to be working properly. However, now, I cannot open the Hyper-V manager. Before I installed SMH, the Hyper-V Manager would open up directly without prompting to identify the server. Now it prompts to select either the local computer or another computer. Irrespective of whether I select local computer or server by its name, I get the following error:

I noticed that SMH is logged in with User: hpsmh_local_administrator local access.

However, there is only one account on the computer, administrator. I tried to view "your account info" and the window immediately closed. Every time I try to access it, there are a couple of errors in the log.

Log Name:      Application
Source:        Windows Error Reporting
Date:          6/30/2019 9:45:54 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      WIN2019
Description:
Fault bucket 1757441387302897424, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy
P2: praid:microsoft.windows.immersivecontrolpanel
P3: 10.0.17763.1
P4: 9d9d9332
P5: usercpl.dll
P6: 10.0.17763.1
P7: 9d66a87d
P8: c0000005
P9: 0000000000008e59
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER647D.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6682.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66A2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66A0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66D0.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_windows.immersiv_f167a0bd4efb88a811c3148b8a962fb2e721660_31aeda3d_1db36817

Analysis symbol: 
Rechecking for solution: 0
Report Id: d0d72daa-e596-43cb-8418-94f7a73d2cdb
Report Status: 268435456
Hashed bucket: 63a2246414aad0b98863afa163c24710
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Windows Error Reporting" /><EventID Qualifiers="0">1001</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-07-01T04:45:54.426214400Z" /><EventRecordID>1017</EventRecordID><Channel>Application</Channel><Computer>WIN2019</Computer><Security /></System><EventData><Data>1757441387302897424</Data><Data>5</Data><Data>MoAppCrash</Data><Data>Not available</Data><Data>0</Data><Data>windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy</Data><Data>praid:microsoft.windows.immersivecontrolpanel</Data><Data>10.0.17763.1</Data><Data>9d9d9332</Data><Data>usercpl.dll</Data><Data>10.0.17763.1</Data><Data>9d66a87d</Data><Data>c0000005</Data><Data>0000000000008e59</Data><Data></Data><Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER647D.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6682.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66A2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66A0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66D0.tmp.txt</Data><Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_windows.immersiv_f167a0bd4efb88a811c3148b8a962fb2e721660_31aeda3d_1db36817</Data><Data></Data><Data>0</Data><Data>d0d72daa-e596-43cb-8418-94f7a73d2cdb</Data><Data>268435456</Data><Data>63a2246414aad0b98863afa163c24710</Data><Data>0</Data></EventData></Event>

Log Name:      Application
Source:        Application Error
Date:          6/30/2019 9:45:53 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN2019
Description:
Faulting application name: SystemSettings.exe, version: 10.0.17763.1, time stamp: 0x9d9d9332
Faulting module name: usercpl.dll, version: 10.0.17763.1, time stamp: 0x9d66a87d
Exception code: 0xc0000005
Fault offset: 0x0000000000008e59
Faulting process id: 0x518
Faulting application start time: 0x01d52fc7dcb3cc1b
Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe
Faulting module path: C:\Windows\System32\usercpl.dll
Report Id: d0d72daa-e596-43cb-8418-94f7a73d2cdb
Faulting package full name: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Application Error" /><EventID Qualifiers="0">1000</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2019-07-01T04:45:53.290176400Z" /><EventRecordID>1016</EventRecordID><Channel>Application</Channel><Computer>WIN2019</Computer><Security /></System><EventData><Data>SystemSettings.exe</Data><Data>10.0.17763.1</Data><Data>9d9d9332</Data><Data>usercpl.dll</Data><Data>10.0.17763.1</Data><Data>9d66a87d</Data><Data>c0000005</Data><Data>0000000000008e59</Data><Data>518</Data><Data>01d52fc7dcb3cc1b</Data><Data>C:\Windows\ImmersiveControlPanel\SystemSettings.exe</Data><Data>C:\Windows\System32\usercpl.dll</Data><Data>d0d72daa-e596-43cb-8418-94f7a73d2cdb</Data><Data>windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy</Data><Data>microsoft.windows.immersivecontrolpanel</Data></EventData></Event>


It's a good thing that I configured pfsense to start automatically, or I would be dead in the water.

I hope someone can help me fix this.

↧

Hyper-V / Windows Core 2016 device management

June 17, 2019, 2:59 am
$
0
0
Spent several hours getting Windows Device Management to remotely connect to Hyper-V Core 2016. Only to discover later, after searching the web, this isn't going to work. Never. Device management is to be done with PNPUtil and / or DevCon. Not exactly the most user-friendly tools. So I wonder how you out there manage devices and drivers on Windows Core?

Simon Weel


↧
↧

Hyper-V VM Crash Issue

July 1, 2019, 5:53 am
$
0
0

Happy Monday,

Our environment is Hyper-V 2012 R2 and the VM in question is Windows server 2016. 

This morning I received a report that a windows share was unavailable. Once I checked the VM that host the share, I discovered the VM has crashed with the error message attached to the request.

I search the error in both event viewer on the VM and the Hyper-V host but couldn't find any related event to the error. I also, searched the internet but found answers that don't fit my case. 

If you have encountered similar error or you know what would cause such issue, please share the information.

My goal is to prevent similar crashed in

the future.

Your help is appreciated.

Raed

↧

Hyper-V 2019 - Guest VM's shutdown unexpectedly

December 12, 2018, 12:26 am
$
0
0

Hi,

Since upgrading my Hyper-V servers to Windows Server 2019, including KB4471332 from last night, my guest VM's do not power down on restart of the 2019 host.

I can confirm integration components are as up to date as possible, and each guest is configured to shutdown when the host restarts.

Each guest gets the "Why did I shutdown unexpectedly message".

The even viewer yields the following all within 30 seconds of restarting the host:

Shut down physical computer. Stopping/saving all virtual machines...

'ADFS' failed to perform the 'Shutting Down' operation. The virtual machine is currently performing the following operation: 'Shutting Down'. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
'ADFS' failed to shut down. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)

The Update Orchestrator Service service terminated with the following error:
This operation returned because the timeout period expired.

Failed to restore configuration for port 59229EE2-C880-4BF2-9849-89A21EC17772 (Friendly Name: ) on switch 300C0E17-E123-4182-BE62-AAD1860BE841 (Friendly Name: ), status = Object Name not found..

Everything is configured as it was on the 2016 Hyper-V host.

The message ADFS failed to shut down because it is shutting down seems terribly odd to me.  Of course its shutting down, just need the host to wait. (Yes the registry is set to 120 as the default time for the host....)

Fairly simple to recreate....just spin up a 2019 server, install Hyper-V role, throw in a VM and test.

Any help would be appreciated, but my money is on it being another bug.

↧

can't see second hard drive in VM settings

July 1, 2019, 7:56 am
$
0
0

Hello,

I'm an old VMware user who is new to Hyper-V, so this is probably a basic question, but I couldn't seem to quite find the right search terms to hit upon an answer.

I have a server with a 100GB C: drive and an 800GB D: drive.  I've been asked to expand the D: drive by 200GB.  However, when I go into Hyper-V Manager, I don't see the second drive.  Can someone point me in the right direction?

Thanks,

Zack Hamilton


↧
Viewing all 19461 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>