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

There was a problem checking for updates 8007000e (Not enough memory)

October 10, 2018, 3:33 pm
$
0
0

If you look up the actual error number in "8007000E", which is "E", or "15" decimal, it is ERROR_OUTOFMEMORY.

I have been having problems updating virtual machines on Server 2012. Hyper-v is set to Start up RAM of 2048 with Minimum of 2048 and Maximum of 1048576 (the default).

If I bump both the minimum and startup to 8192, the update goes through. The VM does NOT ask for memory from the server during a Windows Update. This is a BUG!!! It should be fixed by now!!! And we should get better error messages!!!

For machines that can't have memory added, killing processes and services might free up enough. (I haven't bothered to try the updates at less than 8 GB.)


↧
Search

Hyper-V Replica unable to connect

October 9, 2018, 1:16 am
$
0
0

Hi Experts,

I have configured Hyper-V Replica on my DR site successfully and all goes fine. However from past two days replication suddenly stopped and entered in critical state so i decided to re-start replication but at the end it fails and producing error i have check and found below information on event viewer.

Wizard completed successfully.

After after complete loading it generate an error

As troubleshooting steps i have ran command mention in below post.

Event viewer on Primary Machine.

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          10/9/2018 1:09:59 PM
Event ID:      32000
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      CS1.csaplho.pk
Description:
Hyper-V failed to enable replication for virtual machine 'test-machine': The operation timed out (0x00002EE2). (Virtual machine ID 586079A3-AF78-4A86-B184-9565B5497470)
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" /><EventID>32000</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2018-10-09T08:09:59.515679900Z" /><EventRecordID>8951</EventRecordID><Correlation /><Execution ProcessID="2768" ThreadID="8504" /><Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel><Computer>CS1.csaplho.pk</Computer><Security UserID="S-1-5-18" /></System><UserData><VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events"><VmName>test-machine</VmName><VmId>586079A3-AF78-4A86-B184-9565B5497470</VmId><ErrorMessage>%%12002</ErrorMessage><ErrorCode>0x00002EE2</ErrorCode></VmlEventLog></UserData></Event>

Also i have try replica on two machine and same error occurred however different Primary server is same Replica server is fine.

↧
↧

I changed the VLAN ID 0 to 1, after that unable to connect to the Hypervisor server

October 7, 2018, 12:26 am
$
0
0
Created a Virtual switch and then connected the VM's to this virtual switch. The virtual switch was with external NIC option. Just to test I changed the VLAN id from 0 to 1 (The VM's were unable to ping each other) After applying the VLAN id change, we were unable to connect to Hypervisor server
↧

Fibre Channel MPIV with Live Migration on Hyper-V

October 15, 2018, 3:18 am
$
0
0

Hi Folks,

I've 2 Hyper-V servers.

Each server has 1 Physical HBA card used for SAN presentation(dedicated for SAN for Guest VM).

I've a guest VM running server 2012.

Fibre Channel Adapter has been created on one of this host and zoning has been created with NPIV is enabled.

Both the 2 Hyper-V servers are in a clustered mode. When i try to migrate the guest VM from one host the migration fails.

How can i ensure that the live migration works seamlessly from one host to another in case of host failure. The VM is getting isolated to one specific host and not failing over. Any suggestions would be of great help.

Thanks

Shashi 

↧

Hosted VM's didn't migrate to another host in a cluster the event of a failed host

October 3, 2018, 1:15 am
$
0
0

Hi Folks,

I've a 3 node Hyper-V cluster. One of the node went down due to hardware issues and all the VM's hosted on that physical host didn't migrate to other 2 nodes. It was a very strange that these VM's didn't auto failover.

I was trying to find out why it didn't happen. Performed below steps but was still unable to arrive at conclusion.

1. Cluster Events - Cluster node " " was removed from active failover cluster membership, this could be due to lost communication with other active nodes in the failover cluster. EVENT ID: 1135

2. EVENT ID 1681 - Virtual machines on the node have entered an un-monitored state.

3. EVENT ID 1673 - Cluster node " " has entered isolated state.

4. Events from Failover clustering : Operational - at the same time stamp, the clustered roles were transitioned from state offline pending to offline.

What the Sequence of events that i should follow on why exactly these hosted VM's didn't failover.

Thanks

Shashi  

↧
↧

Moving HyperV guests to a hyperV Cluster?

October 15, 2018, 6:51 am
$
0
0

we have several Hyper V servers, each with several guest machines.  The Hosts range from server 2008 R2 to 2012 and are domain members.

We set up a new cluster (3 2016 servers) and want to migrate the guests to the new cluster setup.

what is the best process for this, can anyone provide an article or post about this.

↧

Microsoft Hyper-V Network Adapter (Code 10)

September 11, 2018, 7:53 am
$
0
0

We have many virtual machines running Server 2016. One thing we noticed on the virtual machines that are configured with Citrix MCS (although I don't think Citrix MCS has anything to do with it) is that the Microsoft Hyper-V Network Adapter will eventually fail with a Code 10 error.

The strange thing is we have multiple 2016 servers running Citrix & RDS but the ones we keep having problems with are our largest ones (30-40 active users every day). Since they are configured with MCS which means they are using the same parent disk (read only) and have their own write vhdx, they all seem to start failing within a week of each other. It seems to take about 3-4 months before the first one presents this problem.

This is a reoccurring issue and I cannot figure out how to start troubleshooting this issue since I can't see anything in the event logs about what happened.

↧

Migrate Server 2003 r2 x86 Ent Ed. to VM , how can I transfer the product key to VM ?

October 15, 2018, 9:34 pm
$
0
0
I would like to migrate a Windows server 2003 to Hyper-v , how can I transfer the product key to VM machine ?
↧
Search

Memory allocated for packets in a vRss queue

January 26, 2018, 8:38 am
$
0
0

Hi there,

I can't see any other information regarding the following errors we saw in our production environment:

"Memory allocated for packets in a vRss queue (on CPU 6) on switch xxxxxxx (Friendly Name: xxxxxxxxxxxxx) due to low resource on the physical NIC has increased to 512MB. Packets will be dropped once queue size reaches 512MB."

We saw these errors on all Hyper-V servers a minute before out monitoring picked up a environment wide outage.

We've then seen errors such as on all our storage paths:

"Cluster Shared Volume 'Volume3' ('xxxxxxxxxxxxx') has entered a paused state because of 'STATUS_VOLUME_DISMOUNTED(c000026e)'. All I/O will temporarily be queued until a path to the volume is reestablished."

There isn't anything in the logs to explain the vRss queue error we saw and I can't see much online. Has anyone ever experienced anything like this or can point me in the right direction?

Thanks


↧
↧

Thin Client Network Communication Interruption

October 16, 2018, 3:28 am
$
0
0

Does anyone help in finding the root cause of the below issue

"Memory allocated for packets in a vRss queue (on CPU 10) on switch C7F0382C-8091-4600-9793-2E49DC6C8B65 (Friendly Name: Thin Client Network Secondary) due to low resource on the physical NIC has increased to67584MB. Packets will be dropped once queue size reaches 512MB."

The above messages started appearing for 15 minutes, finally the memory allocated increased to 72.9 GB and hosts rebooted by windows bugcheck utility. VMQ was enabled.

when these messages started appearing, the all thin client machines lost connectivity with the VRTX hosts. we have redundant VRTX and redundant thin client network. But non of the redundancy worked.

↧

Cannot open handle to Hyper-V storage provider - What does it mean and how to fix?

December 8, 2017, 6:25 am
$
0
0

I have a two-node Hyper-V fail-over cluster using Windows server Datacenter 2016 and storage spaces direct and I have imported some virtual servers from a different Hyper-V (2012) servers which are running Windows Server 2012/2012R2, I have configured new virtual servers which are running Windows Server 2016 and configuration version 8.0 for ALL of my Virtual Machines.No any visible problems with cluster, S2D, Live migration, etc.

But on both servers Hyper-V System log full of  "Cannot open handle to Hyper-V storage provider." EventID: 12660.

Dell PE 740xd. Latest firmware and OS updates.

Each node has following roles&features:

File Server, Data Deduplication, DFS Replication, File Server VSS Agent Service, Storage Services, Hyper-V, .NET 4.6 Features, Bitlocker Drive Encryption, Data Center Bridging, Enhanced Storage, Failover Clustering, Remote Differential Compression, RSAT, SMB 1.0, Storage Replica, Windows Defender features, Windows PowerShell, Windows Server Backup, WoW64 Support

↧

2012 Recreate collection of VMs fails, Post-patch failed"

October 16, 2018, 4:19 am
$
0
0

Windows 10 VMs - I created a new Win 10 2016 LTSB (1607) template from scratch, applied all updates, sysprepped - just like I would do with the previous template which was Win 10 ent 1804 (not LTSB). Anyway, when I execute "recreate all desktops in pool" and point to the new template, it takes a long time, then eventually fails. The first VM's status is Post-patch failed, all others are job canceled. I'm looking through the Hyper-V logs, but nothing jumps out at me. In fact, the only entry I see is for the one that Post-patch failed.

I've confirmed that the VM did export as a template.

Log: Microsoft Windows Hyper-V Worker/Admin

Event ID: 18510

'BASE-0' saved successfully. (Virtual machine ID 741112D6-0B23-4521-8C8F-7ECA9E144843)

Any idea where I should look to see what's happening?

Edit: I closed the wizard and then launched Task Status and now get a bit more information for the VM that Post-patch failed - "Failed: The virtual machine is not ready for the virtual machine-based desktop deployment."

My gut instinct is I can't downgrade win 10 VMs from 1804 to 1607, time to find out what google thinks.


↧

Hyper-V 2016 disk corruption occurs when vhdx or avhdx volumes run out of space

February 26, 2018, 5:36 am
$
0
0

We recently switched to Windows Server 2016 for all of our Hyper-V clusters. In the process we also started switching our backup processes to use the new RCT snapshot backup functionality built into the newer VM versions and 2016.

During the backup of one VM, a snapshot was taken and the avhdx ran out of space due to the amount of IO causing it to grow to fill up the CSV is was located on. Instead of the VM entering a Paused-Critical state and logging an error to the event log, it continued to try and write data to the disk, which caused disk corruption.

In additional testing, in all cases on Hyper-V 2016, when a dynamic disk or disk snapshot runs out of space, the VM continues to operate and attempts to write data to the volume. Did something change with Hyper-V in 2016 when it comes to a volume growing larger than the disk it is on? Or is there a setting somewhere I am missing that did not exist in previous versions?

https://support.microsoft.com/en-us/help/2486243/virtual-machines-enter-the-paused-state-due-to-low-disk-free-space

Performing the same tests in Hyper-V on Windows 10 (1709), when the volume is unable to grow due to disk space, the VM enters a Paused-Critical state and a log entry is created in the event log.

To test this out, create a Windows Server 2016 cluster with Hyper-V. Create a CSV of 20GB and create a VM on that CSV with a dynamic disk of 128GB. Install windows on that VM and copy +20GB of data to it. Instead of Pausing the VM, it will continue to write data and corrupt the contents of the volume.

↧
↧

Clearing avhdx files

August 26, 2017, 3:47 am
$
0
0

Hi

Windows Server 2016 std host and guest.

I have several avhdx files. Some were created automatically I think, and a few through checkpoints by me. What is the safest way to clear these?

Thanks

Regards

↧

failed to start new VM with existing vhdx: failed to change state

April 28, 2017, 5:02 am
$
0
0

Dear Hyper-v gurus

I am trying to start up a new virtual machine created with an existing virtual hard drive.

When i try to power it on , it gives me the following message:

An error occured while attempting to start the selected virtual machine(s):
*********** failed to change state.



I checked the logs and i have the following error logs:

12140

The description for Event ID 12140 from source Microsoft-Windows-Hyper-V-EmulatedStor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

AX2012 RDS DEV

735ABDE2-3815-484A-BB73-2683A2F2BE9A

F:\Hyper-V Disks\AX2012 RDS DEV\HV_AX2012.vhdx

%%2147943065

7864368

80070299

The locale specific resource for the desired message is not present

The description for Event ID 12140 from source Microsoft-Windows-Hyper-V-EmulatedStor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

AX2012 RDS DEV

735ABDE2-3815-484A-BB73-2683A2F2BE9A

F:\Hyper-V Disks\AX2012 RDS DEV\HV_AX2012.vhdx

%%2147943065

7864368

80070299

IDE/ATAPI

The locale specific resource for the desired message is not present

12010

The description for Event ID 12010 from source Microsoft-Windows-Hyper-V-Worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

AX2012 RDS DEV

735ABDE2-3815-484A-BB73-2683A2F2BE9A

Microsoft Emulated IDE Controller

%%2147943065

0x80070299

83F8638B-8DCA-4152-9EDA-2CA8B33039B4

The locale specific resource for the desired message is not present

12030

'AX2012 RDS DEV' failed to start. (Virtual machine ID 735ABDE2-3815-484A-BB73-2683A2F2BE9A)

Any help would be appreciated :)

EDIT:

The OS on the virtual machine host is windows 10:
The virtual machine's OS is windows server 2012 R2

↧
Search

Powershell Exports and Copys for Hyper-V

October 17, 2018, 6:44 am
$
0
0

As far as I can tell if you do an export from Hyper-V using powershell it is not considered a dirty copy.  Can anybody find or have documentation that can verify this?

Thanks!

Trevor

↧

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.

↧
↧

VM won't start because SCSI Physical drive Not found

November 13, 2012, 9:59 pm
$
0
0

I added a SATA hard drive to the host system, set it offline, and attached it to the VM SCSI Controller as a Physical hard disk. After starting the VM, I assigned a drive letter and copied files from the hard drive, then shut down the VM and the host, then removed the hard drive from the host.  Now the VM will not start with error: Synthetic SCSI Controller (....): Failed to restore with Error 'The system cannot find the file specified'.

In the VM Settings, the missing Hard Drive is listed as Physical drive Not found.  I cannot find any way to delete this missing hard drive from the SCSI controller - the Remove button is grayed out.

↧

Hyper-V Server 2019 - RDP not working

October 4, 2018, 7:10 am
$
0
0

Hi,

So I am testing with Hyper-V Server 2019, which I deployed to three brand new HP Proliant gen10 machines. I'll test on them for a while before putting them in production. Installation was a breeze, as with Hyper-V 2016. However, I can't seem to enable RDP on Hyper-V Server 2019. When I enable through the menu, it says it's done so, but alas, netstat -a reveals there isn't even a process listenening on port 3389.

I checked the registry, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server is correct. The required services are running. Firewall is completely disabled through netsh for testing. Remote administration is working fine, RDP is not listening at all.

Anyone else ran into this?


↧

HyperV not getting IP Address when more than 5 HyperV is turned on

October 17, 2018, 8:31 pm
$
0
0

Hi All,

Running  Win 2012 R2.

Hyper-V Manager has several machines on it. I can turn on all of it but as soon as the 5th machine is turned on, 5th and onwards will get this error :



When I turned off previous machines 1-4, the error above is the same when i connect back to machine#5.

However, if all machines are off and i restart machine#5, it will not have the error. But as soon as the 5th machine is turned on the 5th (let's say machine#3) machine is turned on, same error again.

I have even tried changing the virtual switch but that did not work.


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