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

Error: 0x80071A90. Problems with Hyper V Configuration (for virtual machine, Windows Phone).

$
0
0
Hi dear comunity.

I go to work with Visual Studio 2013 for the creation Windows Phone apps. When I installed the Visual Studio, the setup told me that I need install or configure to Hyper-V. I followed all the steps for that. Control Panel -> Programs ->Turn Windows features on or off -> Check all Hyper V components -> and OK. And then this error appear: Error: 0x80071A90.

Somebody can help me with this problem. I want to work very soon with Windows Phone Apps for my institute.

Thanks  for all :)

How to decommision Hyper V VM?

$
0
0

Dear Hyper V Expert,

We are running Windows Server 2012 Standard as the Hyper V Server and there are some VMs running Windows Server 2008 R2 inside. One of the VM will need to decommission as it is old server and we have done the backup. What is the best procedure to decommission the server? is it just by deleting the VM then all the VM related file such as .VHD/.VHDX or XML will be deleted?

Thanks.

Regards,

H

Dynamic Memory is not working all the time

$
0
0

We are in the process off moving our 2008R2 VM's from the 2008R2 HyperV servers to new Server 2012R2 Hosts.

We shut down the VM's copy the files and VHD's to the new CSV's en import the VM in the Hyperv Manager. Then we make them high available in the Failover Cluster Manager (Configure role - Virtual machine). We mount the integration tools and update the VM to version 6.3.9600.16384

For a specific type of VM (mostly RDS Host servers) we always had Dynamic Memory configured (when they were hosted on de 2008R2 platform), so we are using the same settings on the 2012r2 platform. The memory settings were;

Startup memory: 1024 MB

Minimum memory: 1024 MB

Maximum memory: 12288 MB

These VM's reboot every morning, this is done for specific reasons. But now once in a while (once per week/2 weeks) we notice that the VM's are not using more memory then 1024 MB while the demand is much higher. Rebooting the server helps most of the times, live migrating to another host also helps. In the VM we see that memory usage in the taskmanager is 99-100%, and after the move it immediately starts using more than the minimum configured amount.

Until the failover the memory usage was 1024 MB and it did not get any higher.

This happened several times. Last week we changed the Memory configuration to:

Startup memory : 2048 MB

Minimum memory: 2048 MB

Maximum memory: 12288 MB

But this morning we had a call about the performance of one of the VM's, We saw that it was only using 2 GB memory while the demand was much higher. After live migrating it to another host it started using more memory immediately.

The 2012R2 hosts are not overcommited, there is a lot of memory still available for the VM's. Those VM's never had this problem on the 2008R2 Hyperv platform.

Any idea why this happens?

Peter Camps


bitlocker in a VM

$
0
0

can you bitlocker a guest? I remember in a recent talk that windows 10 allowed this but I cant find anything on it?

-Nex6

Hyper-V Machines stuck in "Stopping" and "In Service" state when rebooting

$
0
0

All the VM's hosted on the Hyper-V server 2012 are stuck on "stopping" when I reboot/or shutdown from the Hyper-V manager. I cannot kill the process either (Permission Denied) in process Explorer. Also tried restarting Hyper-V related services, only solution is to reboot the host. Where is the issues and what is the VM trying to do that is preventing it from restarting?

Windows 10 Build 10240 Managing Hyper-V on 2012 R2 Datacenter Cannot Connect

$
0
0

So, we have a total of six Hyper-V servers in our environment. All six were installed from the same Server 2012 R2 Datacenter ISO. I have been managing these from my Windows 8.1 machine with no issues. I got ahold of Windows 10 build 10240, and I am running into an issue connecting to the servers now.

The strange thing is that I CAN connect to one of them. I cannot figure out what is different on this one server from the other five. Windows updates maybe? I migrated all the VMs off one of the servers I cannot manage remotely, performed all Windows Updates, and I still cannot connect to it.

I am reading that Windows 10 should be backward-compatible with managing Hyper-V on 2012, but on connection, it appears a WMI namespace is missing that the Windows 10 tools are trying to connect to.

I am not trying to use alternate credentials (I read this will NOT work from 10 to 2012 R2). Any ideas why this is not working? Several Google searches have not told me anything so far. I realize Windows 10 has not officially been released yet, but a few of us are testing the waters for compatibility issues.

I would appreciate any help anybody can offer.

Eric

Clusterd Hyper-v, Can network outage trigger failover?

$
0
0

Is it possible in a Clustered 2012 R2 Hyper-V environment to fail-over virtual machines if the network goes down? Meaning that if a VM does not have network access or say it cant ping its gateway to fail-over to another Host that can.

I have a scenario where one VM Host lost access to a VLAN 2, where VLAN 1 still works. Though all the VMs using Vlan 2 lost network connection. Could these live migrate in this sort of failure?

Thx

General Access Denied Error 0x80070005 creating .VHDX in a SHARED FOLDER

$
0
0

I have 2 windows 2012 servers (WIn2012 Standard File Server / Shared Folder  and Win2012 Standard + Hyper-V)

The shared folder have users, admins, system, everyone full control permissions for shared + NTFS permissions (i added also the HYPER-V$ computer account)

I´ve tried PROCMON to see the error in detail, filtered out useless things and aded keyword VHD to ctach the write attempt.. nothing, no itens captured...

But when i try to create the .VHDX file, i got the error message

"Failed To Create Virtual Hard Disk" and "General Access Denied Error 0x80070005 creating .VHDX " error

I´m trying to create using the new disk wizard and typing \\server\sharedfolder as destination for the VHDX file

Any ideas?


Expanding virtual disk

$
0
0

Hi there,

I am new at Hyper-V, and was a bit strict when setting the size of the main disk on my first WM. I selected vhdx and set the size to 20GB max. Then I installed Windows Server 2012R2 resulting full disk and no space left for SQL Server 2014 (Drive C: 6028 MB required, 637 MB available). "Insufficient space available in directory C:\..."

I expected the disk to grow dynamically, but it is not.

When I check the disk inside the WM it states 920MB free of a total of 9.48GB. Checking the vhdx using inspect in Hyper-V Manager v6.3 the current size is 9.04GB and max size is 21GB.

If I use the Edit, Expand tool I am able to set the max size - but the current is not changed.

Any advice? Do I have to delete the WM and start all over again?

Espen


ESXI on Hyper-V

$
0
0

Hi,

I'm trying to install ESXI 6.0 on Hyper-V machine but getting an error message saying 'Not enough memory to start virtual machine' but I have allocated 5GB for ESXI 6.0. My Hyper-V machine got 16GB memory . Can someone please help me to sort this?

Thanks

Anton

How to delete snapshot/checkpoint WITHOUT applying ANY changes? How to get rid of snapshot/checkpoint FOREVER?

$
0
0

How to delete snapshot/checkpoint WITHOUT applying ANY changes? How to get rid of snapshot/checkpoint FOREVER?

If I apply snapshot/checkpoint, ok, i´ll go back in time, but the snapshot/checkpoint will be there, am I right?

If i delete the snapshot/checkpoint, the snapshot/checkpoint will gone, bt all changes will be applied, am I right?

hypotetical scneario:

Developers ask for a snapshot/checkpoint, so i create, now i have a snapshot/checkpoint

developers did a lot of changes and one month later, they decide: you can go back in time, reverting snapshot/applying it, making the VM as it was before.

But the developers are satisfied and they don´t want to create any further snapshot/checkpoint, they don´t need extra modifications, the need to keep things as ever be,.

I need to get rid of the snapshot/checkpoint, without applying and making sure that the snapshot/checkpoint will be gone and making NO modifications at all in the VM.

What is the best way?


Unable to connect to Hyper-V Child Partitions over Network

$
0
0

I'm trying to make the switch from ESXi over to Hyper-V. I've just set up my first Hyper-V host, and I've hit an issue that's had me stumped for a couple of days.  I can connect to the parent partition successfully, and connect from it to the rest of the network.  However, I can't connect to the guest partitions over the network at all.  The guest partitions can connect to the rest of the network OK, (can ping other servers, and joined the domain successfully), but no matter what, I can't seem to connect into them from the LAN (ping, or RDP).

My Hyper-V host has two Physical NICs, one of which I've dedicated to storage (via a separate, physical switch), and one which connects to the LAN.  Not ideal, I know, but it's what I have to work with, and it's the same setup as I've used successfully in ESXi for several years.

Storage is working fine over an SMB3 share, but I can't get the LAN interface to work.  I'm trying to follow the recommended configuration, as shown in Figure 1 (Source), but with VLAN 11 for the parent partition, and VLANS 11, 21, 31, 32 and a couple of others for Guest partitions.  I have created an external Virtual Switch, bound to the Physical NIC which connects to the LAN, which has the VLAN ID for the host operating system set as 11.  I've created a couple of VM's, with their virtual NIC's connected to this virtual switch, and the VLAN ID's 11 and 21.  The physical switch port that the LAN-facing interface is connected to is in trunking mode, and is a member of all the necessary VLANs.  I've verified that VLANs are supported enabled in the NIC's properties.

I'm completely out of ideas at this point, as far as I can see, everything should be working. Are there any suggestions or ideas I've not tried yet?

Many thanks.

Cannot enable Replication on any new Virtual Machines

$
0
0

I apologize in advanced for the upcoming wall of text. I have been working on this issue for almost a week now so I have collected a fair bit of information.

The Situation: I have two Hyper-V servers, both in the same Active Directory domain. There is no clustering or SCVMM, it’s a fairly simple straightforward setup. One of the servers runs all of our VM’s, the other is just a replica destination. Currently there are 9 Virtual Machines on the primary host, of which 7 are currently replicating over to the replica host without an issue.

The Problem: While the existing 7 Virtual Machines are currently replicating without any problem at all, I cannot initiate replication on the other two, or on any newly created virtual machine.

The Errors: Attempting to initiate replication on any VM comes up with the following errors (Only one error per attempt, the last error repeats indefinitely for further attempts):

First Attempt: Hyper-V failed to enable replication for virtual machine ‘Main’: An unexpected error occurred. (0x800300FD). (Virtual Machine ID F12E84F3-A789-4AEA-AAA8-81D64109CD66).

Second Attempt: Hyper-V failed to enable replication for virtual machine ‘Main’: Cannot create a file when that file already exists. (0x800700B7). (Virtual Machine ID F12E84F3-A789-4AEA-AAA8-81D64109CD66).

Subsequent Attempts: Hyper-V failed to enable replication for virtual machine ‘Main’: Operation aborted (0x80004004). (Virtual Machine ID F12E84F3-A789-4AEA-AAA8-81D64109CD66). ‘Main’ failed to perform the operation. The virtual machine is not in a valid state to perform this operation.

If you look on the replica server, you will find that the XML was successfully copied over and directories were made for the Virtual Disks, but no virtual disk files are present. Deleting all the directories and XML files from the failed replication, restarting the hyper-v management service on the replica server and trying again will bring you back to the original Unexpected Error message and the sequence begins again. I suspect it is the Unexpected Error (the first message) that is the root of this problem. The other two messages are ones I have seen before when a piece of a VM already exists on the replica (which it does after the first failed attempt) so those are more or less expected.

I get this sequence of errors attempting to replicate either of the two currently un-replicated VM’s or on any newly created virgin VM. Other than the failure to initiate replication I have had no other problems. I can create new VM’s on either host with no problem, I can Live Migrate VM’s both storage and configuration from one host to the other and back. I have tried both Kerberos and Certificate authentication. And all the currently replicating VM’s are still replicating without an issue.

I have scoured the event logs, however the events listed don’t tell me even so much as a single word more than the error messages themselves, on either the primary or the replica. Any help or direction would be greatly appreciated, thanks in advance.



How does 2012R2 CSV 2.0 handle backups?

$
0
0

Hello,

Just wondering how backups should work with a failover cluster running on 2012R2. From what I have read Direct I/O should be used in 2012R2 when running a virtual machine backups instead of redirected access in 2008. I am expecting that when a backup is taken that the VM backed up will access the data from its local ISCSI connection no matter which node the CSV is owned by.

What I am seeing is that if the VM and CSV are on different nodes the disk access is run over the management network connection from the CSV iSCSI owner to the VM owner and then sent to the backup server. This causes a reduced backup speed. The CSV stays in online mode and running Get-ClusterSharedVolumeState shows all volumes in direct access still. We have no 3<sup>rd</sup> party hardware VSS providers and this is happening on 2 separate clusters.

What I am trying to figure out is this how it is supposed to work or not? Is anyone able to help me with this? I have spoken to Symantec who now say it is a Microsoft issue but have not confirm this is expected or not.

Hyper-V Replica - Enabling Replication Failed

$
0
0
Hi,



I have two 2012 R2 Hyper-V servers with few VM’s running on them and when I’m trying to enable replica on one of the VMs I recieve the error below:

Enabling replication failed.

Hyper-V failed to enable replication.

Hyper-V failed to authenticate using Kerberos authentication.

Hyper-V failed to enable replication for virtual machine 'servername': The target principal name is incorrect. (0x80090322).(Virtual machine ID 33B2EBCC-B3A0-AA80-4DBCFCF923A5)

Hyper-V failed to authenticate the Replica server servername.domain.com using Kerberos authentication. Error: The target principle name is incorrect. (0x80090322)

I have looked at the SPN for both of the hyper-v servers and it seem to have the correct SPNs including. Both Hyper-v server are not in the same domain. I added the IP and servername in the hostfile for dns resolving.

Hyper-V Replica Service/servername
Hyper-V Replica Service/servername.mydomain.com
Microsoft Virtual Console Service/servername
Microsoft Virtual Console Service/servername.mydomain.com
Microsoft Virtual System Migration Service/servername
Microsoft Virtual System Migration Service/servername.mydomain.com

Any help would be appreciated!


Kind Regards

Alexander




SMB Multichannel for CSV I/O redirection and Live Migration, without SOFS cluster

$
0
0

I am trying to wrap my head around the configuration of SMB Multichannel on a Hyper-V cluster that is NOT using a SOFS cluster - so, using SMB Multichannel for Live Migration and CSV I/O redirection only.

I am seeing a lot of guidance online that says the possible NICs for SMB Multichannel should be restricted.  On the cluster, I would expect the restriction to only allow the Cluster/CSV and Live Migration networks for SMB Multichannel.  How is this achieved?  Everything that I see on setting a constraint with New-SmbMultichannelConstraint is setting the constraint against an SMB file server.  I do not have one to specify.

Additionally, I am using a converged network configuration, with teamed physical interfaces, a Hyper-V virtual switch, and virtual adapters off of that switch for management, cluster/CSV, and live migration networks.  Are these constraints only set on physical NICs?

Strange, when I run Get-SmbMultichannelConnection on any of my hosts, on the client IP it shows connections coming from the management network (10.1.80.x/24), connecting over to the cluster network (10.1.81.x/24) on other hosts.  The Live Migration network (10.1.82.x/24) appears to be functioning as expected.

Server Name    Selected       Client IP      Server IP
-----------    --------       ---------      ---------
fe80::ecad:... True           10.1.82.15     10.1.82.16
fe80::ecad:... True           10.1.80.15     10.1.81.16

Am I overthinking this?  I just don't want an I/O redirection to occur, with the redirection happening on a management interface that impedes our access to the system.

Loss of a single LACP link results in LACP group traffic failing

$
0
0
Hi


Can anyone explain this one?

I have the following setup:

- Switches:

    3 x Cisco 3750X-24TS and 1 x 3750G-24TS-1U in a stack
    s/w: 15.0(2)SE on all
    Etherchannel groups created as LACP/Active with 4 to 6 links per group


- Servers #1

    4 x Dell servers with Broadcom NICs in a Hyper-V 2012 r2 cluster
    NIC teaming configured using MS Hyper-V Load Balancing (i.e. not using the Broadcom utility to aggregate the NICs).
    There are 6 NICs per LACP group on each server connected to the 3750(x) switch stack.
    The NICs are connected across all 4 members of the stack. LAG created as LACP/Active

- Servers #2

    2 x Dell servers with Intel NICs running Windows 2012 r2 in a cluster (used as a HA file cluster).
    NIC teaming created using Win2012 load balancing. LAG created as LACP/Active
    There are 4 NICs per LACP group on each server connected to the 3750(x) switch stack
    The NICs are connected across all 4 members of the stack. LAG created as LACP/Active


Issue:

On Thursday a helpful telecoms engineer knocked out power to switch #2 of the 3750(x) core switch stack and caused a reboot of that switch. When this happened it appears that, rather than just losing connectivity on the LACP links connected to that single switch, the entire LACP interface went down causing both the Hyper-V cluster and the HA file cluster to start throwing roles around and denying the existence of the other nodes. Chaos ensued.

Once switch #2 had rebooted it joined the stack correctly and normal service, in terms of the network connectivity resumed. The file cluster started operating without assistance but all of the VMs had rebooted and were in various states of chaos.

So the question is what could have happened to the LACP LAG interface on the switches or the Loadbalancing on HyperV to cause the entire group to fail when one / two links went down?

Thanks in advance - any help very greatfully received!
 
Martin

UEPALS MS Forum data

Turn Off... Shut Down... Save

$
0
0
Hi,
I am using hyper-v, can any one tell "what is the difference between turn off... shut down... and save in hyper-v, and which is the best option to choose?" 

Windows 10 enterprise ltsb Hyper-v virtual: switch not working, Cannot uninstall hyper-v.

$
0
0

HI all

I cannot get hyper-v virtual swich up and running .  ( It ran for a day or so, and then maybe some update made it malfunction)

Switch telling that I should "attach cable" ( or the like :-< )

version : Windows 10 Enterprise 2015 LTSB

I've tried to uninstall through -> control-panel -> programs... -> windows programs  ->  uncheck hyper-v 

This seems to do   ( my guess)
1:  an uninstall  
and then to my surprise 
2:  an install of hyper-v 
or maybe it just fails. 

Because after a reboot .. hyper-v is still alive and kicking ... to my utter frustration. 

I could throw away windows 10 , but I find that this would be a terrible waste of work ... so I'll ask here first.

Move AD-DS off of physical Hyper-V Host/remove AD-DS role from Host instead of demoting???

$
0
0

I walked into a situation where a previous individual installed Hyper-V, ADDS, DHCP, DNS, IIS, Network Policy and Access Services and Print and Document Services all on the same machine as well as a RDS VM! The host is running Windows Server 2012 R2 Standard, 8 GB RAM, Intel Xeon CPU E5-2430 v2 @2.50 GHz (6 cores, 12 logical processors).

What I would like to do for the customer is remove ADDS, DHCP, DNS, IIS, Network Policy and Access Services and Print and Document Services from the Hyper-V Host and leave the Hyper-V role enabled. My first thoughts are to:
1) Do a P2V image of the computer (Host).
2) Remove the ADDS, DHCP, DNS, IIS, Network Policy and Access Services and Print and Document Services from the HOST leaving only the Hyper-V role on ther host.
3) Install the image created of the host as a VM on the host (of course removing the Hyper-V role).

***My question is can this be done safely?  It makes sense to me but am I missing something here? Rather than demoting the current DC running on the same box Hyper-V is running, can I just remove the role along with the other roles listed, visualize and run as a VM?

Thank you for your help!

Viewing all 19461 articles
Browse latest View live




Latest Images