I need some help.

I installed the November 2014 MS updates last night. I installed them on my lab Hyper-V box. The Hyper-V box is joined to a domain but is not a domain controller. It is Server 2012R2 with Hyper-V with all previous patches applied. I had two VMs configured on the box. The VMs were a 2012R2 server and a Windows 8.1 box. Both were running fine. In fact I shut them down before I did the Microsoft Updates on the server.

The issue I describe below was not present until I did the updates and rebooted. The server and the associated VMs had been running fine for months. These updates are the ones that my SUS server provided to this server.

After I rebooted the server I could not restart either VM. I kept getting the same error that is listed below. I tried DELETING the VM from Hyper-V manager and then building a new VM and using the old vhdx. Again NO LUCK. I even tried CREATING a new VM and I got the same problem.

(Additional Note: I appeared as though I was able to delete the VM from Hyper-V Manager. Hyper-V Manager displayed 'Destroying....' for some period of time and then the VM was removed from Hyper-V Manager. However, recreating the VM did not solve the problem.) 

Each time I get the following error displayed on screen.

'Unnamed VM' could not intiialize.

An attempt to read or update virtual machine configuration failed

'Unnamed VM' could not initialize (Virtual Machine ID)

'Unnamed VM' could not read or update virtual machine configuration: Ran out of memory (0x8007000E) Virtual machine ID B9xxxxxxxxxxxx 

=======================

I adjusted permissions on the C:\ProgramData\Microsoft\Windows\Hyper-V folder. Opened it up to "Authenticated Users" based on a couple of TechNet articles that I found. NO luck

In the Hyper-V Config log I get the following entry,

The configuration store at'' is not accessible Unspecified error(0x80004005)

==========================

I also had these errors in the Windows Application log.

ID=1000 Source=Application Error Type=1 Message=Faulting application name: vmwp.exe, version: 6.3.9600.17334, time stamp: 0x5407c751

Faulting module name: vsconfig.dll, version: 6.3.9600.16384, time stamp: 0x5215db66Exception code: 0xc0000194

Fault offset: 0x000000000001966c

Faulting process id: 0xb84

Faulting application start time: 0x01cffe274d55ea6b

Faulting application path: C:\Windows\System32\vmwp.exe

Faulting module path: C:\Windows\System32\vsconfig.dll

Report Id: d4210450-6a1a-11e4-80d6-0019b9eed814

Faulting package full name:

Faulting package-relative application ID:

Hey TechNet,

After my initial build of 2 Hyper-V Core server which took me a bit of time without a domain, I started building 2 more for another site. After the initial two, setting up the new ones went very fast until I ran into a very funny issue. And I am willing to bet it is just my luck but I am wondering if any other out there ended up with it.

So, I build these 2 new servers, create a NIC teaming on each host, add the management OS adapter, give it an IP and I can ping the world. So I went back to my station and tried to start working on these hosts but I kept getting DCed especially from one of them. Reinstalled it and remade the NIC teaming config, just in case. Same issue

So I started pinging both of the servers and I remarked that when one was pinging, the other one tended to not answer ping anymore and vice versa. After testing the firewall and the switch and even trying to put the 2 machines on different switches, did not help. So I thought, what the heck, let's just remove all the network config from both machine, reboot, and redo the network config. Since then no issue.

I only forgot to do one thing before removing the network configuration, I forgot to check if the MAC address on the Management OS adapters were the same. Even if it is a small chance, it can still happen (1 in 256^4 i'd say).

So to get to my question, am I that unlucky or might it have been something else ?

Enjoy your weekends

I have a 2012 host running Hyper-V. There are 3 guest VMs all running Server 2012. One of them has started experiencing a problem where it will lock up with the only way to get at it is to do a Turn Off in Hyper-V Manager.

The problem always occurred during the nightly backups. Windows Server Backup is used and the destination is a VHDX file located on a removable cartridge on the host server. This is the same setup for all 3 VMs. The other two do not have any problem with this and this one has operated for about a year without a problem with this. I can do a one time backup using the same parameters as the scheduled backup and they all complete successfully with no lockup of the server.

I finally deleted the VHDX file and created a new one. I also deleted the backup job and created a new one. Backups ran fine for just over a week, then the lockups of the server started again.

The only seemingly consistent evidence I can find is 153 Disk warnings in the System log. These seem to occur during the backup process. My research indicates some sort of disk system problem.

Any ideas?

Jonathan

Hi, 

I'm going to need to configure a NIC team for the LAN traffic for a Hyper-V 2012 R2 environment. What is the recommended load balancing algorithm? 

Some background:

- The NIC team will deal with LAN traffic (NOT iSCSI storage traffic)
- I'll set up a converged network. So there'll be a virtual switch on top of this team, which will have vNICs configured for each cluster, live migration and management
- I'll implement QOS at the virtual switch level (using option -DefaultFlowMinimumBandwidthWeight) and at the vNIC level (using option -MinimumBandwidthWeight)
- The CSV is set up on an Equallogics cluster. I know that this team is for the LAN so it has nothing to do with the SAN, but this reference will become clear in the next paragraph. 

Here's where it gets a little confusing. I've checked some of the Equallogics documentation to ensure this environment complies with their requirements as far as storage networking is concerned. However, as part of their presentation the Dell publication TR1098-4, recommends creating the LAN NIC team with the TrasportPorts Load Balancing Algorithm. However, in some of the Microsoft resources (i.e. http://technet.microsoft.com/en-us/library/dn550728.aspx), the recommended load balancing algorithm is HyperVPorts. Just to add to the confusion, in this Microsoft TechEd presentation, http://www.youtube.com/watch?v=ed7HThAvp7o, the recommendation (at around minute 8:06) is to use dynamic ports algorithm mode. So obviously there are many ways to do this, but which one is correct? I spoke with Equallogics support and the rep said that their documentation recommends TransportPorts LB algorithm because that's what they've tested and works. I'm wondering what the response from a Hyper-V expert would be to this question. Anyway, any input on this last point would be appreciated.

Hey guys!

Got a very weird one for ya! So the details:

 - Server 2012R2 Hyper-V Core

 - Microsoft remote management document followed to enable remote access

 - John Howard's HVRemote config utility run several times

 - Manually opened ports, enable firewall rules, DCOM permissions, remote permissions, etc, etc

 - Installed COREFIG (for 2012, not 2008 version), open source Hyper-V management utility to verify all is enabled and working.

 - Changed RPC dynamic ports to 50000-50100 to no avail

What works:

 - Remote server management works (user, groups, event logs, disk management, etc)

 - Can RDP into host machine, no problem.

 - Can see file shares localy and over the web

 - Can use third party software (Corefig and 5nine Manager) to control machine

What doesn't work:

 - Hyper-V manager

However, install 5nine manager (free client) and have full admin control over host (create VM's, start/stop/pause, VLAN management, etc)

Even if I disable software and hardware firewall's, no change. The Hyper-V manager will not connect with error "RPC server unavailable"

What's even weirder, if I start the Hyper-V manager, I get the RPC error. If I then click the "refresh" button (on the right Actions panel) it then connects and shows me status, but I cannot change or interact with anything. It's almost like it's ignoring the RPC error and trying to connect anyway.

I have spent weeks on this and am no closer to a solution. If it wasn't for the 5Nine Hyper-V FREE client, I'd be seriously boned! :P

Any advice would be welcome, and thanks in advance.

:D

Hi,

I'm running windows 8.1 as a host machine. I've installed Hyper-V feature and then I installed a windows 7 in a virtual machine.

But the pain point is it does not get full screen because it just hasn't the screen resolution I'm looking for. So changing the resolution is not an option since it says that my total available graphics memory is 8 mb. How can I increase this memory ?

My Hyper-V vistual machin configuration for windows 7 is :

RAM: Dynamic 1024 , CPU: 4 virtual 

Hi, I'm currently experiencing a problem with some VMs in a Hyper-V 2012 R2 failover cluster using Fiber Channel adapters with Virtual SAN configured on the hyper-v hosts.

I have read several articles about this issues like this ones:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/baca348d-fb57-4d8f-978b-f1e7282f89a1/synthetic-fibrechannel-port-failed-to-start-reserving-resources-with-error-insufficient-system?forum=winserverhyperv

http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx

But haven't been able to fix my issue.

The Virtual SAN is configured on every hyper-v host node in the cluster. And every VM has 2 fiber channel adapters configured.

All the World Wide Names are configured both on the FC Switch as well as the FC SAN.

All the drivers for the FC Adapter in the Hyper-V Hosts have been updated to their latest versions.

The strange thing is that the issue is not affecting all of the VMs, some of the VMs with FC adapters configured are live migrating just fine, others are getting this error.

Quick migration works without problems.

We even tried removing and creating new FC Adapters on a VM with problems, we had to configure the switch and SAN with the new WWN names and all, but ended up having the same problem.

At first we thought is was related to the hosts, but since some VMs do work live migrating with FC adapters we tried migrating them on every host, everything worked well.

My guess is that it has to be something related to the VMs itself but I haven't been able to figure out what is it.

Any ideas on how to solve this is deeply appreciated.

Thank you!

Eduardo Rojas

I get

[Window Title]
Hyper-V Manager

[Main Instruction]
An error occurred while attempting to start the selected virtual machine(s).

[Content]
'SEPMw8' could not initialize.

The virtual machine could not be started because the hypervisor is not running.

[Expanded Information]
'SEPMw8' could not initialize. (Virtual machine ID 150A0669-9CA8-4C4D-A272-88A9FBF34D31)

The virtual machine could not be started because the hypervisor is not running.  The following actions may help you resolve the problem:

1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer.  (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.  Resetting the physical computer is not sufficient.)

3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.



[V] See details  [Close]

but all hypervisor services are running and virtual disk imaging also running,

1),2) were performed long time ago. Did not change the boot config data store

what do I need to do?

Die Installation des Hyper-V unter Windows 8.1 Professional schlägt immer wieder fehl. Obwohl das Hyper-V Feature auswählbar ist und es bei Neustart installiert wird, erfolgt kurzt darauf die Mitteilung, dass die Installation der Feature nicht erfolgen kann und die Installation rückgängig gemacht wird.

System: i7 4770K, ASUS Z97Deluxe, RAM 32GB, INTEL VT aktiviert, Windows 8 Pro Upgrade auf 8.1 Pro, alle Treiber und Windows Updates installiert

Ursache + Lösungen?

NEU!
Interessant ist, wenn INTEL VT im BIOS deaktiviert wird kann Hyper-V installiert werden! Bei der System-Info-Abfrage über die Konsole wird auch die Deaktivierung angezeigt.

Frage: Weshalb kann ich Hyper-V bei deaktivierten INTEL VT installieren, aber umgekehrt nicht?

I'm using Windows Server 2012 R2 Std as Hyper-V Host....

Can any one tell me, Is it necessary to Harden each & Every Virtual Machine (Linux or Windows) on Hyper-V host server if we harden the Hyper-V host.

I have a Windows 2008 server with two NIC's (Intel PRO/1000 PL and Intel PRO/1000 PM), and one virtual external switch connected to each NIC.

With the 01/14/08 network driver, I get very low throughput on both NIC's (~10KB/sec when downloading from my server when it should be around 11MB/sec).

I've found that disabling "TCP Large Send Offload (IPv4)" on the virtual switch and "Large Send Offload v2 (IPv4)" on the physical adapters solves the problem.

Is this a bug in the driver?

Thank you,

Ricardo Costa

We have a Hyper-V 2012 Cluster, with 2 nodes Windows Server 2012. The Shared Storage is an HP Storage. We configured Failover Cluster, and everything works well. We configured SAN, and everything seems to be in working order.

On the Hyper-V Cluster, we have 3 Virtual Machines. They all work well, and they can move from one node to another no problem.

From the HP San, we allocated a 40GB drive for each virtual machine, all WWPN's are allocated correctly, tripled checked that. When we connect to the virtual machines, the drives appear as you expect, and you can use them ass you wish. So we configured certain applications.

Here's the thing. After we restart a VM, the drive allocated from the SAN no longer appears, neither in Windows Explorer or Computer Management. And here is the weird thing, if we live migrate that virtual machine to the other node, the drive automagically appears again like nothing ever happened. Restart the VM again, it disappears, live migrate, it reappears.

Any ideas on how to fix this? I mean I want that drive to be permanently attached to the VM. Here's a screenshot how it appears in Hyper-V and HP Storage Manager

Hi,

My HyperV server (GUI) host has 3 virtual machines guests - all  of them are critical servers, suddenly the host is unable to connect to local server and thus I am unable to manage 3 virtual machines, however all 3 guests are online are accessible.

I have checked the VMM service and is running fine, i am receiving same error when logged in as a local admin instead of domain admin. Now one of the virtual machines is having problem and I am unable to manage i cannot connect to HyperV from remote system as well. When i logged on to the Server Manager, the automatic refresh is failing as per below,

Manageability from Server Manager is showing following error, Online - Data retrieval failures occured.

Moreover when i click add remove features I receive following error, Server Manager is collecting inventory data. The wizard will be available after data collection finishes. I have not shut down the guests and restarted the host, i fear i might not be able to connect to them as they are critical.

Please note that the host is not in any type of high availability yet, any help on this would really be appreciated, thanks.

Hi Hyper V Expert,

I have the VM Test environment using Hyper V. I am using Windows Server 2012 as the Hyper V Host. Within this Host, I have configured one VM as the AD with preinstalled Windows Server 2008 SP2. This AD is up and running properly. this VM is connected to a virtual switch called "Switch1". It is internal network, means that there is no connection to the external network. Now, I would like to do a test of intersite AD replication using my VM Test environment. in this case, I have created another virtual switch called "Switch2" and I have built another VM attached to "Switch2". how should I create the routing to allow both of the VM connected to different virtual switch to communicate with each other just like the VPN over WAN? However, need to ensure that the routing won't disturb or affect any routing in the external network. it must be within the VM test environment only.

Please advise.

Thanks.

Regards,

Henry

Hi Hyper V Expert,

We have one Hyper V host server running windows server 2012 standard. there are 2 VMs that are each connected to different virtual switch, called "switch1" and "switch2". both of the VM has different subnet "192.168.10.x" and"192.168.20.x". how do I doing routing between two different virtual switch? Since it is the internal virtual switch, the traffic should not leaked to the external physical network.

Thanks.

Regards,

H

Hi All,

Recently I have got server failure. Info from memory dump is following. Cannot find the reason of failure. Please help.

6: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041289, The subtype of the bugcheck.
Arg2: 00007fff141f4000
Arg3: 000000000000007b
Arg4: 00007fff141f4c01

Debugging Details:
------------------

Page 42459e not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR:  0x1a_41289

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  vmwp.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801429ec412 to fffff801429c2ca0

STACK_TEXT:  
ffffd000`2796eaf8 fffff801`429ec412 : 00000000`0000001a 00000000`00041289 00007fff`141f4000 00000000`0000007b : nt!KeBugCheckEx
ffffd000`2796eb00 fffff801`428e2c47 : ffff0000`00000000 ffffe000`0559e568 ffffd000`2796ed00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x19282
ffffd000`2796eb60 fffff801`4292f933 : 00000000`00000000 ffffd000`2796ed00 fffffa80`00000000 ffffe000`0559e568 : nt!MiLocateWsle+0x2b
ffffd000`2796ebb0 fffff801`4292f62e : 00000000`00000000 ffffd000`2796ed00 fffffa80`00000000 ffffd000`2796ec70 : nt!MiTerminateWsle+0x2f
ffffd000`2796ec00 fffff801`428e3c41 : 00000000`00000000 00000000`00000000 fffff580`10804638 00000000`00000000 : nt!MiDeletePageTableHierarchy+0xd2
ffffd000`2796ed70 fffff801`42934989 : ffffffff`ffffffff ffffffff`ffffffff ffffe000`0559e568 ffffe000`019db080 : nt!MiDeleteAddressesInWorkingSet+0x4e1
ffffd000`2796f660 fffff801`42c4e7ab : 00000000`00040000 ffffd000`2796f800 ffffe000`019db080 ffffe000`0559e080 : nt!MiBeginProcessClean+0x9d
ffffd000`2796f6a0 fffff801`42c83ce8 : 00000000`00040000 ffffd000`2796f800 00000000`00000000 fffff801`42cbffca : nt!MmCleanProcessAddressSpace+0x67
ffffd000`2796f700 fffff801`42c18504 : ffffe000`0559e080 ffffc000`0b5f4930 ffffd000`2796f800 00000000`00000000 : nt!PspRundownSingleProcess+0xac
ffffd000`2796f790 fffff801`42d22fc4 : 00000000`c0000005 ffffe000`019db080 ffffd000`2796fb00 ffffe000`019db128 : nt!PspExitThread+0x4c8
ffffd000`2796f8a0 fffff801`428b481a : ffffe000`05393bb0 00000000`00000000 00000000`00000000 00000000`0000000c : nt!KiSchedulerApcTerminate+0x18
ffffd000`2796f8d0 fffff801`429c7bc0 : 000000fb`b5ca40a0 ffffd000`2796f950 fffff801`429694e8 00000000`00000000 : nt!KiDeliverApc+0x2fa
ffffd000`2796f950 fffff801`429ce55a : 00000000`00000000 000000fb`b5d39aa0 ffffe000`00600d00 ffffd000`2796fb80 : nt!KiInitiateUserApc+0x70
ffffd000`2796fa90 00007fff`142165ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000fb`b652fac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`142165ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+19282
fffff801`429ec412 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+19282

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  52341cf4

BUCKET_ID_FUNC_OFFSET:  19282

FAILURE_BUCKET_ID:  0x1a_41289_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x1a_41289_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41289_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {e01cf37e-0b3f-17aa-251b-4e0e5b8f0b0f}

Followup: MachineOwner

Installing Windows 2012 R2 under Hyper-V virtual machines, the disk size in the end is around 9 GB but in case the BlockSize is set to :268435456. It goes above 11 GB.

Then doing the same operations on a differencing disk the size goes to 4 GB in case the block size is 2 MB but 14 GB when the BlockSize is 256 MB.

Any ideas why?

yup