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

Hyper-V not merging snapshots automatically - Disk merge failed.

October 8, 2019, 2:39 am
$
0
0

Hi,

I have asked this question before however the same problem has occurred and is driving me crazy. Now we have a 2016 Hyper-V environment with Server 2016 VMs. We run daily backups using DPM 2016.

Now I came in after the weekend to find that all of my VM backups had failed and every VM that had failed had a .avhdx file left behind. I have tried shutting down the virtual machine but I get caught out with "Merge in Progress - Failed".

Sometimes when I shutdown the virtual machine it will fail to start and say that there is an issue with the virtual hard disk chain and it needs to be reconnected.

The only way I have found to fix it is to manually merge the virtual hard disks and then re-create the virtual machine. This works and then I can take another backup however a few days later the same issue will happen again.

I don't have time to constantly merge virtual machines every other day and of course it affects the production environment. There have been changes to our group policy and as it is affecting all of our hosts I wonder if this is the problem however I am not sure what to look at. I heard about the "Logon as a service" causing an issue however this made no change for me.

If anyone has any ideas I would love to hear them, currently going through it with Microsoft Support however they don't listen to the issue.

↧
Search

Move VM from Windows Server 2012 Hyper-v to Proxmox or other hypervisor

October 8, 2019, 3:45 am
$
0
0

Hello!

We have Dell server which was purchased with Windows Server 2012 Standard OEM license. Server runs VM with Windows Server 2008R2. Host and Guest servers are activated. We need to move to other Hypervisor (eg ESXI or Proxmox) on the same host, but we want to preserves product license!

Could we read product key inside the VM and use it on the other Hypervisor? other suggestions?

Thanks in advance!

↧
↧

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.

↧

Detect Virtual Machine and Logical Processor/Processor Socket ID mapping using Powershell

October 11, 2019, 8:55 am
$
0
0

When I do this:

if ((pPipe = _wpopen(L"powershell -Command \"Get-Counter '\\Hyper-V VM VID Partition(*)\\*'\"", L"rt")) == NULL) exit(1);

I get this output wherein the VM is mapped to its preferred Numa Node index (Socket ID):

\\win-3t40ilvkkvh\hyper-v vm vid partition(lg5)\remote physical pages : 0
\\win-3t40ilvkkvh\hyper-v vm vid partition(lg5)\preferred numa node index : 0
\\win-3t40ilvkkvh\hyper-v vm vid partition(lg5)\physical pages allocated : 264200
\\win-3t40ilvkkvh\hyper-v vm vid partition(lg2)\remote physical pages : 0
\\win-3t40ilvkkvh\hyper-v vm vid partition(lg2)\preferred numa node index : 1
\\win-3t40ilvkkvh\hyper-v vm vid partition(lg2)\physical pages allocated : 264200

My question is how can I get the mapping between the VM and Logical processor. If some kind soul could answer, I would be grateful. 

Ex: VM LG5 is mapped to LP1 of Socket0(numa node) or VM LG2 is mapped to LP0 of Socket 1

thanks

ananda



↧

Hyper-V VM Generation 2 - How to boot from .ISO

November 8, 2013, 12:31 am
$
0
0

Hi guys, 

Server OS: Windows Server 2012 R2

I have a VM Gen2 with following settings: 

I can boot fine from the same .iso from a Gen1 VM so the .iso is bootable. 

I know that the Gen2 VM uses SCSI instead of IDE, but I have no clue regarding how to boot from the .iso..

Any ideas?

Thanks in advance!

Best regards,

Kenny

↧
↧

Hyper-V Cluster - iSCSI and MPIO / TEAM Interface

October 12, 2019, 6:28 pm
$
0
0

Hi,

We have two HP servers with 2*10G network ports. Can anyone provide the best practice to use both the 10G NIC with redundancy config ? Can we use NIC Teaming or MPIO ? can both the interface be configured with same VLAN IPs ?

Thanks,

suhag

↧

CSV STATUS_IO_TIMEOUT When starting a specific VM

October 2, 2019, 7:12 am
$
0
0

Hi, 

I have the strangest problem with a customers infrastructure that I can't seem to get to the bottom of.

Server OS Windows Server 2019 Standard

Two Servers in the cluster accessing the CSV on a Dell EMC SC277984 via iSCSI over a 10GB back bone.

Basically long story short, but when rebooting (the act of powering it on) a specific VM it causes the CSV to drain and produces a myriad of errors and mayhem, it takes the entire estate down for about 15 minutes whilst everything begins to resume and power up again.

This error is found in the event logs.

Cluster Shared Volume 'Volume1' ('Cluster Disk 2') has entered a paused state because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished.

I have tried rebooting the SAN, rebooting the hosts running a Cluster Validation Test (passes with no errors) 

I'm keen to try removing the role itself from the cluster and recreating the VM in hyper-V from scratch and re-attaching it's original disks but haven't had the opportunity to try this yet.

↧

Hyper-V 2016 VMs stuck 'Creating checkpoint 9%' while starting backups

March 28, 2017, 1:40 pm
$
0
0

We have a two clustered W2016 Hyper-V hosts, every couple of days one of the hosts gets stuck when the backup kicks off. In Hyper-V manager the VMs all say 'Creating checkpoint 9%' It's always the same percentage 9%. You can't cancel the operation and the VMMS service refuses to stop, the only way to get out of the mess is to shutdown the VMs, and hard reset the effected node. The backup works for a few days then it all starts again.

The only events I can see on the effected node is:

Event ID: 19060 source: Hyper-V-VMMS

'VMName' failed to perform the 'Creating Checkpoint' operation. The virtual machine is currently performing the following operation: 'Creating Checkpoint'.

Can anybody help please? Cluster validation is clean. Hosts and guests are patched up.

↧
Search

Availability of Microsoft Hyper-V Server 2019

February 25, 2019, 5:38 am
$
0
0

Dear Microsoft!

On https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2019 you link the hyper v core server setup. However, it only leads to https://cloudblogs.microsoft.com/windowsserver/2018/11/13/update-on-windows-server-2019-availability/ and there is no download available.

When are you planning to make it available?

By the way: The download that was briefly online https://software-download.microsoft.com/download/pr/17763.1.180914-1434.rs5_release_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO is barely usable for 2 reasons:

A after installing it and activating Remote desktop, the server does not start to listen on port 3389. No RDP possible!

B Trying to do an in-place upgrade from Hyper-V Server 2016 leads to an error: "The installation failed in the SAFE_OS phase with an error during SET_Product_Key operation"



↧
↧

WS2K19 Essentials Hyper-V powers down VM's each week

September 16, 2019, 3:30 am
$
0
0

For the last month, something strange is happening with our new Hyper-V server. During the summer holidays we bought and installed a new physical server with Windows Server 2019 Essentials installed on it; on which we also enabled and configured the Hyper-V role. On that physical Hyper-V, we have three VM's running, which are:

1. Domain controller;
2. File sharing server, part of the domain;
3. App server, also part of the domain.

All of the three VM's also have Windows Server 2019 Essentials as OS. Each WS2K19 Essentials server has its own dedicated license.

Each monday between 9:30 am and 10:30 am the Hyper-V power downs both the File and App servers. When we look in the logs there isn't anything that explains the power down of the VM's. Updates are also disabled to make sure that isn't the culprit.

Does someone has any ideas of what might be wrong or where to look in what direction? I've been looking for over a month now and can't seem to find anything.

Thanks!

↧

Hyper v VM not able to start after vSAN

October 14, 2019, 10:35 pm
$
0
0

Hi,

Not able to start the Virtual machine after configured vSAN getting the below error, we have 2 physical host, and 1 storage. i'm trying to do configure SQL failover cluster in the VM, so shared storage planning to attach from storage.  created the lun in the storage and created virtual san in the Hyper v manager and assigned the vSAN in fiber channel adapter in the VM. but when trying to start the VM i'm getting the below error. 

 

Regards,

Manikandan
↧

Enhanced Session Mode Not Available Until First Login on VM

March 7, 2019, 2:24 pm
$
0
0

Scenario:

- Windows 10 1809 Enterprise (x64) host.

- Windows 10 1809 Enterprise (x64) shielded guest VM on this host. 

- RDP is enabled on the guest and remote desktop works to the guest system from the host.

- Enhanced session is enabled/allowed in Hyper-V for the server and for the user.

Problem:

- New shielded VM, fully deployed successfully using PowerShell.

- When starting VMConnect, "Enhanced Session" is greyed out and unavailable initially for the guest VM.

- Once a user (any user) logs into the guest VM one time using remote desktop, Enhanced session is available for that guest VM and works fine from then on.

Things tried:

- Rebooting host.

- Restarting guest.

- Disabling and re-enabling Enhanced session in the Hyper-V settings.

What's missing and what happens during this first user login to all of a sudden make Enhanced session available and/or why is it not enabled/available initially?

Jason | https://home.configmgrftw.com | @jasonsandys

↧

Enable Hyper-V Replica for the VM with recovery checkpoint

July 21, 2019, 8:55 pm
$
0
0

VM has Recovery Checkpoint from Backup Agent and I need to enable to replica. Is it is good to enable replica along with checkpoint.  Please advise 

_ Ragav



↧
↧

Cannot Allocate wanted amount of RAM to hyper-V machine, although host has more than enough free memory

March 27, 2018, 7:16 am
$
0
0
Hi!

I recently bought a dedicated server, and i wanted to try the windows server 2016 edition ( evaulation version ).

To be short, my host server has 8GB of RAM, it is using about 1.3GB when idle, and when i try to allocate 5500MB to Hyper-V machine it just throws the classic error "Not Enough Memory in the system to start the virtual machine". 

I tried messing with the settings a little bit, suck as NUMA spanning, and dynamic memory ( it starts the hyper-v with dynamic memory, but it doesn't want to allocate more than 4.6GB RAM for hyper-V machine when it demands over that, while the host server still has more than 1.5GB RAM free )

In the end nothing worked.

One thing I was able to notify, is that, while the RAM on the host is free, some amount of RAM is cached ( tehnically that is free RAM, it clears up if needed), and here is the catch. I can not allocate RAM for Hyper-V machine if it is supposed to free up that cached RAM.

So here is an example, if 1.5GB RAM on host machine is cached. and host server uses 1.5GB on idle, that means that of totally 8GB, only 5GB remains. And what i am able to achieve, is to allocate only up to that "totally free" 5GB.


Although this is just a hypothesis, but i tested it and it is really weird how the limit is always that cache size.
But maybe I am wrong...

I would be extremely happy if someone has a clue or knows how to deal with this problem, as I am getting desperate.

Thanks :)
↧

Merging snapshots.

October 15, 2019, 6:57 am
$
0
0

I have a question i couldn't find answer. So I have a virtual machines with vhdx and 2 avhdx drives. VHDX max size 500GB.

All those 3 files were on 1TB storage. Both AVHDX increased to that level that no room left on 1Tb storage. So i cant merge them as well. I have attached 4Tb storage and moved VM storage via VM settings to new storage. So now i have tons of space to merge differentials to its parents. But one thing gives me worries.

Main parent is something like (1)-362Gb its child is (2)-235Gb and its child (3) is 457Gb.

I have to start merging 3 back to 2 so its mean 457 to 235 and i afraid that is will make more then 500 what is the limit and a it will fail destroying data. Could someone with more experience to bring in some light?

By the way if its safe to merge can I do it while VM is online?


↧
Search

Impossible to live-migrate VMs with .vhdx

May 8, 2019, 7:32 am
$
0
0

Hello everyone,

I have a Windows Server 2012 R2 and a new server with Server 2019.

I'm trying to live migrate VMs' from Server 2012 R2 to Server 2019 and noticed that VMs with .vhdx fail to be live migrated on the new host. The migration starts and progress until the end (or close to then end ?) of the process and then fail.

- On the 2012 R2 host, I can see the following error in the eventvwr: "Event 21026 Hyper-V-VMMS - Virtual machine migration operation for SERVER_NAME failed at migration destination SERVER_DST. (Virtual machine ID VM_ID)".

- On the 2019 host, I can see the following error in the eventvwr: "The absolute path 'C:\Windows\system32\vmguest.iso' is valid for the " ISO Disk Image pool, but references a file that does not exist.

FYI: The guest OS that we are trying to move are 2008 R2 and 2012 Servers.

Live migration is enabled on both host and I tried to do it via CredSSP.

Migration of .vhd is working fine.

Does anyone have an idea on why this is happening ?

Thank you very much by advance for the help you can provide.

Cheers.

↧

Hyper-V Manager not able to connect the Local Server

February 11, 2019, 8:31 pm
$
0
0

Dear Experts...

Greetings !!!

1. Issue Description: 
Hyper-V Manager not able to connect the Local Server – Shows connecting to Virtual Machine Manager Service state and did not connect. Hyper-V Host shows Host Not Responding in the SCVMM console
Due to which VDIs were not launching to newly connecting users as just disappearing

2. Temporary Fix:
If we restart the server, the issue will be resolved but the current active users gets impacted. 
Need to power on all the VDIs and ensured all got registered state
And also the same issue keep on re-occurring frequently and affecting production users

3. Troubleshooting Steps Taken:
We tried to restart the service SCVMM and WS-Remote Management service which got restarted. But still the issue persists.
When we restart the WMI Service, one of its dependent service Hyper-V Virtual Machine Manager (vmms.exe) goes to stopping state and neither stopped nor restarted.
Tried to kill the vmms.exe process from task manager and via command prompt using the commands but it never destroyed. 
It says cannot stop the Virtual machine manager service, already another running instance exists, access denied (when kills process from task manager), etc.
Until the server reboot the issue will not be resolved.

Thanks in Advance ...

DevT-MCT

↧
↧

Hyper-V 2019 VM Cluster Replication

March 26, 2019, 3:36 am
$
0
0
Ever since upgrading our 2 Hyper-V clusters to 2019 from 2012 R2 when trying to set up a new VM replication I get errors. Works for existing VMs replicating that were created before the upgrade but any new VMs fail. Enabling the replication seems to create the VM fine on the replica and creates drives at 4,096KB ready for replication but trying to start the initial replication fails with the error:

Start-VMInitialReplication : Hyper-V failed to start replication for virtual machine 'VM': Operation aborted
(0x80004004). (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Hyper-V could not find the virtual machine 'VM' on the Replica server and will connect to the Hyper-V Replica
Broker in the next retry interval. (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Replication operation for virtual machine 'VM' failed. (Virtual machine ID
E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5) (Primary server: 'Host1', Replica server:
'Broker')
At line:1 char:1
+ Start-VMInitialReplication -VMName 'VM'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Start-VMInitialReplication],
   VirtualizationOperationFailedException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVMInitialReplicationCommand


Doing the same process through the failover cluster gui I get a similar error. Says the replication was enabled successfully however initial replication could not be started. And goes on to say Hyper-V could not find the virtual machine on the replica server.

Has this yet to be recognized as a bug in Windows Server 2019?
↧

Considerations for Virtualizing Single-DC environments

October 15, 2019, 4:02 pm
$
0
0

I just picked up my second break/fix client whose prior IT services left them with a single Windows server running the DC role (among others) and an uncertain backup solution.

After talking the risks over with the customer, I've been asked if it's possible to just virtualize the server, and take regular snapshots in addition to their current backup solution.  Then if there's an issue with the server we can just rollback to a known good snapshot.

I know that the official guidance is to not snapshot DCs to avoid USN rollbacks, but in a single-DC environment with no replication is that still an important consideration?   If so, what's the best guidance at this point since they're not going to go forward with a second machine just to be another DC.

↧

Question on import/export of VM

October 15, 2019, 6:29 pm
$
0
0

I have a 2012 R2 VM on a 2016 host.

The 2012 R2 VM is a domain member and running SharePoint.

I need to reload the 2016 host.

If I do an export to an extra hard drive in the server and reload the host, I can import it again without issue?

Thanks

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