We recently had a network traffic / virtual switch issue crop up, due to VMQ being enabled and improperly configured on Broadcom 10GbE adapters.  While that failure occurred, our backup appliances were taking backups of VMs.  Because of lost network connectivity, the Hyper-V checkpoints used for those backups remain on some of our VMs.

These checkpoints do not have the usual "Delete Checkpoint" / "Delete Checkpoint Subtree" options available to them.  How do I remove them so the virtual disks are merged and back to a single VHDX per virtual disk?

My HyperV server has two quad ethernet port cards in it and the first 4 are in a Team with the virtual Switch with a static IP, DNS and Gatway.

The other card has two of 4 nics disabled and two of those nics have a static IP without dns or gateway used for iSCSI multi-pathing. 

It is not uncommon for me to log into the HyperV box and find that it has "no internet connection" and after a reboot it may be up for a short while but eventually it fails. Also after a while it will lose time and you cannot RDP to it at all! I have to physically login to it and reboot it.

I am including screenshots of me setup to help aid in any information that may be needed to help me figure this out:

Please help me!

Thank You!

Hello All

We have a client with a Server 2008 R2 Hyper v server with 4 VM s ( 1 SBS server , 1 Windows XP VM and 2 Windows 7 VM s).One Windows 7 VM is configured with Dynamically expanding VHD with Maximum size set to 60GB and currently that drive is now 60GB and the Windows XP VM is configured with again a dynamically expanding VHD with maximum size set to 150 GB and the current size of the VHD is 119GB.Other 2 M s have fixed VHDs.

All of those VM s reside on a 1TB partition which is on a RAID 5 volume directly attached to the physical server. This partition now has just over 50GB of free disk space.

On 2 occasions the 2 VM s with dynamically expanding VHD s were paused with the following events logged on hyper v VMMS admin log

Event-1

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin

Source:        Microsoft-Windows-Hyper-V-VMMS

Date:          4/8/2014 6:37:03 AM

Event ID:      16050

Task Category: None

Level:         Warning

Keywords:     

User:          SYSTEM

Computer:      name-Host

Description:

'name of the VM' is about to run out of disk space on 'D:\Hyper-V\ Virtual Hard Disks\'. (Virtual machine ID 44798757-7590-4B31-9ED1-2F397F0ED1C0)

Event-2

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin

Source:        Microsoft-Windows-Hyper-V-VMMS

Date:          4/8/2014 9:26:31 AM

Event ID:      16060

Task Category: None

Level:         Error

Keywords:     

User:          SYSTEM

Computer:      name-Host

Description:

'Name of the VM’ has been paused because it has run out of disk space on 'D:\Hyper-V\virtual Hard Disks\'. (Virtual machine ID 44798757-7590-4B31-9ED1-2F397F0ED1C0)

When I checked the log exactly the same has happened on 3-28-2014 and one of my colleagues has resumed the VM s and the VM s were working fin till yesterday. Also there were no option but to resume the VM s yesterday as well and both VM s are working as expected till now.

I did some research and found that there is a bug on windows 2012 which can cause issues like this but no such bugs for server 2008 R2.

1. Can someone let me know how hyper v calculates the available free disk space?
2. I’m inclined to think these issues were caused by the low disk space on the partitions and dynamically expanding disks on the VM s but I’m confused as to why it started working without any issues since 3-28-2014 till yesterday and even yesterday since now.
3. If this is actually related to low disk space on the partition on the hyper v server, what are my options? Convert the disks to fixed or add more disk space?

Many thanks

Dhanushka

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012

The following guide will enable you to:

1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager

! This should also work for Core installations of server 2012, but I haven't tried.

This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.


* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.

- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.

> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)

1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.

! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012

2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.

> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
----------------------------------------------------------------------


> Next, is to get the MMC firewall snap-in working.
   The reason for this, is to have a GUI available to configure it.
   If you're happy without it, you may skip this and use a shell instead to do so.

? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)

! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level 
# (In other words: allows the firewall to be remotely managed)

! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.

? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.

! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done

! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon, 
# and choose run as admin on the bar below.

! Client: application MMC: select "file" --> Add/remove snap-in 
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)

* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.

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

! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.


! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.

! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate

# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
#
# I recommend to choose yes; unless you like to pull some more hairs...

! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
!  select yes

! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server

Done.

You can now manage your remote server through the familiar computer management GUI.

! Right-click your remote server, and select "Computer Management"

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

A few side notes:

? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.


If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.

Cheers!

Hello,

I have a poweredge T610 with a 1GB Cache controller in RAID 50 with 6 fast drives.  I have the cache policy turned on.   If I copy a VHD file on the host from the same volume to the same volume on the host, it copies with an average speed of 700MB/s (starting out around 800 and finishing around 500 keeping at around 750 most of the way).

If I try to copy from the host to a share on a VM (fixed drive 500 GB on the partition - hosted on the same volume that the I got 750MB/s copying from host to the same host) - I get about 75MB/s.     If I try to copy from the VM to the host I also get about 75MB/s average.    If I turn off the windows firewall (I'm not using any other software firewall on the server) I get about 105MB/s on average.       I have the nics on the host and VM in a trunk and I got about the same speed when the Nics were set up as single nics so that didn't change performance much.    I tried turning off IPv4 large send offload - no difference.  I tried just about every single option in the hyperv nic settings - no significant difference.

The host server and the VM are on the same subnet, on the same switch.    It is after hours and there is no backup or any user activity on the network.   I've tried Broadcom and intel server nics with the latest firmware and drivers.

Is there some trick to getting better performance/throughput on the VMs?

I am new (really new) to virtualization and this is my first few hours with Hyper--V.  So bear with me.

I am on a standalone PC running windows 8.1.  The machine is on a local network but in workgroup NOT domain.  Currently the machine runs a web server on IIS.

I added the Hyper-V as per the instructions and have the Manager up.  I followed the steps to create the VM and all seemed to go very well.  UNTIL I tried to connect to the Virtual machine.  I get a dialog "YOUR CREDENTIALS DIDN'T WORK".  It then shows my machine name and wants a password.  (My machine is Edge 2 and the VM is VMTest)  It wants the credentials for Edge2.  Edge2 is NOT a user on my machine, it is the Machine name.  There is only one user on the machine and that is me as the administrator.

I cannot find an answer that gets me away from this situation.  I know its likely pretty simple but please point it out to me as it eludes me.

Hi, I have several Windows 2012 VM's running on a 2012 R2 host. None of these VM's can do an online backup. They both have a SCSI controller installed, and all the HyperV integration services installed. For a 2008 R2 HyperV host, theHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\ScopedSnapshots registry entry needed to be added.

Does this also need to be added when 2012 R2 is the host?

friends i am looking for a panel or tools which can give me web based access to provision VMs... i am not sure what options i have available in case of opensource...

and also wants to understand how it works... as there are few doubts which i am carring since long .. like when from a panel provider provisions the VMs.. i can understand it takes the computing and things relatied to OS but i am not able to understand how it manager the network layer.. like public IP/ domain name / VLan things.. on the fly... can some one put some light on this..

and at last... this is more over a question for azure team but as this is for virtualization also putting it here also : i understand the processors whch are available in market at max 8 cores.. so how Microsoft or other vendors proving VMs which are of around 20 cores or even more.. how they are doing this.. i want to understand the content and technology both..

thanks for the time ..

I have a Hyper-V node with 32 GB of system memory and 6 cores (12 logical processors with hyperthreading) running Windows Server 2012 Datacenter.  On this node I have a virtual machine with 4 GB of system memory and two logical processors running Windows Server 2008 R2 Standard.

On the virtual machine, Task Manager show that 3.62 GB of memory are being used and 109 MB are free.  This is despite the fact that nothing is installed or running on the vm except the operating system.  The memory usage for all processes for all users as reported by Task Manager is under 100 MB.

Any ideas on what can be causing such a huge discrepancy between the memory usage reported by Task Manager and reality?  The host OS reports 9.8 GB out of 32 GB memory usage (expected since several VMs are running on the host), but I would not think that the guest OS would be pegged.

Hi guys

on my host i have 3 NIC ( 1GB each ) i want to team them to one NIC.

so all the traffic and management and VM traffic go throught this NIC Team.

can you help me how to do this ?

Hardware previously had Windows Server Essentials 2012 running fine.

Current setup, base is Hyper-V 2012 with Windows Server Essentials in a VM, which has been installed a few weeks ago and is stable, but only on the main SSD.

I decided to try to configure so that the physical disks were available directly to WSE, hoping that the management of them would be easier.

I had one SCSI in the VM, and aside from the SSD boot disk, I was able to add 1 3TB drive, and it all works.  If I add a second 3TB drive,  the WSE VM will not start.   It tries to start, but goes back to off in a few seconds. 

I then decided to put the 3TB drives on a second virtual SCSI within the VM, to see if that was better.

No change, one drive ok, but two  and the VM will not start.

Then I booted the VM with the 1 3TB drive that worked, and then while the VM was on, I was able to add 3 more 3TB drives, and the VM stayed up.  I was able to create a storage space from the 4 drives, mirrored, thin provisioned, the standard WSE 2012 settings (I kind of wish it would give you a choice on these, but...).   Everything seemed to be working fine.

But, when the VM was stopped, it will not now restart.   I suppose I have to delete the 3 extra drives, which will cause storage pool disaster I presume.  

Seems odd that I can add them, and use them in WSE2012, but then it will not restart.   And they were on a separate virual SCSI controller from the "boot" drive.  

Any ideas?    (or let me know if this is the wrong forum... since the VM would not start, I am blaming Hyper-V...)

Thanks!

Ross

I am running a home Server with 2012 R2 with the Hyper-V role installed, with about 5 Windows 8.1 VM's.  I'm trying to get RemoteFX working, here's my hardware config:

• E5-4610 Processor (Supports Slat)
• Nvidia GTX 770 (Driver supports WDDM 1.3 with direct X 11)
• Gigabyte GA-X79-UD5 (All bios virtual settings enabled)

When I install the Video card driver (tried different versions using windows 8 and windows 8.1 drivers) initially it shows me the checkbox to "Use this GPU with RemoteFX" However after a reboot it says no supported video cards are available.

Before the reboot after installing the driver when it shows the GPU is capable of remote FX, I am not able to add a RemoteFX 3d adapter to a virtual machine because it is greyed out.

After I reboot, if i uninstall and re-install the driver the GTX 770 is available to use again but I still cannot add the RemoteFX adapter to a virtual machine's hardware.

I have done the following:

1. Verified in DXdiags that the direct X version is 11
2. Verified in DXdiags that the driver model is WDDM 1.3
3. Verified the E5-4610 Proc supports Slat or Extended Page Tables
4. Enabled all the Virtualiztion VT-x settings in the Bios
5. Verified the video card is supported and certified in 2012 R2
6. Verified the Remote Desktop Virtualization Host Agent is started in Services.msc
7. Tried the newest and oldest video drivers for 8.1, and newest for windows 8
8. I am using Generation 1 vm's as i heard Generation 2 is having problems with RemoteFX
9. Tried Generatino 2 VM's, there is no option to add RemoteFX hardware
10. Tried a different GTX 550Ti video card, same issue
11. Performed all Windows updates for server 2012 R2

Please advise on the next steps to be taken to get RemoteFX working, or if any of the hardware I mentioned above does not support RemoteFX in 2012 R2.

Thanks.

I'm experiencing some packet loss to all of our VMs that we didn't have before we made some changes to our Hyper-V implementation (Windows 2008 R2). Most of the VMs also run 2008 R2 - with 3 that run Server 2003.

The host server is a Dell R610 with three 4 port NICS - two Intel quad port gigabit and a quad port Broadcom. We us the individual ports of the Broadcom for host management and live migration - no problems here. We use the Intel cards for both iSCSI and VM networks. Calling the two intel cards “A” and “B”, and the ports P1-4 we've used AP1, AP2, BP1, BP2 (ports 1 & 2 of both Intel NICs) for iSCSI connections, and we've created a NIC Team with AP3, AP4, BP3, and BP4 (ports 3 and 4 of both Intel NICs). The team type is "Virtual Machine Load Balancing". We then created a Hyper-V switch based on this team for use with all of the VMs created on the host. (as a side note: prior to implementing the NIC team, we just had 4 Hyper-V switches, one associated with each of these 4 ports.)

The 4 ports of the NIC team are connected to two different Cisco SG200 switches - AP3 and BP3 are connected to switch1, and AP4 and BP4 are connected to switch2 (in an attempt to maximize redundancy). The two Cisco SG200s are simply connected to the rest of our network - each to a different switch within the subnet. There is minimal configuration done to the SG200s (for example NO link aggregation); spanning tree is enable however.

My question is: can the network cables be connected to different switches (as they currently are) and if so is there some configuration piece (either on the switch or within Windows) that I'm missing? What are the options here if this configuration is incorrect? The packet loss is in the range of 0.1%, but we've had odd spikes where a VM was essentially unavailable for a brief period (a few minutes) then returned to "normal" (0,1% loss). Pinging a device (like the SG200 itself) or another physical server (for example our domain controller or the hyper-v host itself) results in essentially 0 loss; maybe one or two packets during the course of a 12 hour ping (this was the “normal” ping response to VMs before we created the NIC team, so I’m quite sure this has something to do with it).

Thanks in advance!

I have just embarked on a project to v2v 250 VMs from vSphere 5.1 to Hyper-V 3.0. I thought I'd start a discussion string on v2v experiences. I have used the native v2v conversion with in VMM, 5nine's Easy Converter, Starwind's Converter and MVMC. I'm not happy with any of them. They are so inconsistent and frustrating, I see this project as literally taking years. Sometimes the VMM converter works, sometimes it just fails with crypt error messages. At the beginning it would crash the management interfaces on the ESXi servers but a ticket with VMware and increasing some system values solved that.

Most of the time, it will run for an hour or two, then just fail with no explanation. Same for MVMC. Occasionally I have some luck doing a p2v instead of a v2.

5nine usually fails, but gives me the VHDX files so I can create the VM from there. Ditto for Starwind.

Even if I could get a product that works consistently, the fact that 5nine and VMM actually make 2 or 3 copies of the VMDKs during the conversion process is pretty ridiculous. I have had to carve out terabyte LUNs to attach to a Hyper-V host just to have enough scratch disk to convert, then watch the conversion take literally hours.

All in all, a very frustrating experience. Have others been faced with similar issues? And if so, how did you tackle it?

Thanks.

Hello,

I recently created a remote desktop collection using windows server 2012 R2 on an HP ProLiant BL620c G7 Blade Server (which has completely up to date firmware and drivers). There are 30 VM’s running on the server, and it is running great – for the most part. My issue is that, it seems to be at random (maybe once every 48 hours), users will be disconnected from their session, and they are unable to log back into their session remotely. I can log into their session as a local user by going through hyper-v, however once I am in there I notice that I have no internet or network access. To solve this problem, I have to go onto the network adapter of the VM, disconnect the virtual switch assigned to the VM, and reconnect it again. Doing this provides remote access to the VM again.

I initially thought the issue came from the configuration of the virtual switch. The HP Blade Server has 4 10 gig NIC’s, and they were teamed into two teams (each team having 2 physical NIC’s). I created two separate external network virtual switches from each Team. I also had “allow management operating system to share this network adapter” checked. I noticed a warning on the server side when a disconnect would occur which was Event 16945 “MAC Conflict: A port on the virtual switch has the same MAC as one of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver.” Because this error occurred at the same time as a disconnect, I assumed that this warning message was causing the problem, and I was able to resolve it by redoing the NIC team to where there of the physical NICs were teamed together and a virtual switch was created from them without the checkbox that allowed management operating systems to share the network adapter. This left one NIC available for management purposes, and I haven’t seen the error message since, however disconnects still continue occur.

I do not see any helpful information in the event logs of the client VM when one of these disconnects occur, and the users are doing nothing out of the ordinary that would cause it to happen. In fact this problem has happened when a user has been disconnected from their machine for over 10 hours.

Anyone have any thoughts as to what is going on here?

Hi all

I have a lab consisting of 2 Mac Mini Servers, late 2009 model, most often running Hyper-V on the newest evaluation versions of Windows Server. With Windows Server 2012, everything was running smoothly.After upgrading to Windows Server 2012 R2, all VMs that are assigned to a VLAN lost network connectivity (aka "Enable virtual LAN identification" in the VM NIC settings). VMs using no vlan id work as expected!

While doing research it seems like there are some network-related problems with W2K12 R2 floating around, but I was unable to find any useful info matching my problem.

Installing W2K12 R2 Update 1 did not help in any way. After quite some hours with eliminating possible problem sources, I seem to end up with this behavior being a BUG in Windows Server 2012 R2.

Here some details for anybody willing to doublecheck that I did not overlook anything:

: both servers are configured identically. The build-in NIC is assigned to a virtual switch of type "External", and is shared with the management OS. Each host has an additional FastEthernet USB adapter, which is also configured as virtual switch of type "External", but not shared with the OS.

is configured to send untagged traffic for the management network, and tagged traffic for all VM networks, on all ports that are connected to the lab server (meaning both for the built-in and for the USB network adapter). The switch config was not touched in the OS upgrade process.

1. When setting "Enable virtual LAN identification for management operating system" and re-configuring the switch to send tagged traffic also for management network, then the management OS also looses network connectivity.

2. Un-checking the "Allow management operating system to share this networking adapter" does not help either. When running Get-NetAdapter I see that the physical adapter (Ethernet) has the same MAC-address as the virtual adapter (vEthernet), as somewhat described here.

3. Attaching the VMs to the vitual switch using the USB network adapter does not help either, so I am inclined to rule out a driver related problem since the problem show on two completely different NICS - unless Microsoft somewhat has made changes to VLAN traffic handling in Hyper-V/virtual switch!

as VEN_10DE / DEV_0AB0, and according to pcidatabase.com this is the "NForce 9300 LAN/SATA/SMBUS/SMU/GPU" controller. Device Manager reports it as "NVIDIA nForce Networking Controller Properties", driver version 7.3.1.7336 from 23.02.2012. When checking the NIC configuration (Device Manager/NVIDIA .. Network Controller, Properties, Advanced), I see that the propertyPriority & VLAN with value ofPriority Enabled. When changing this toPriority & VLAN Enabled, management OS also looses network connectivity. The VMs still do not have any network connectivity. - In short: it seems like Window Server 2012 R2 has - at least in my lab scenario - a serious problem handling any VLAN-related traffic. Windows Server 2012 was working flawlessly. Any hints appreciated, or some feedback if other are experiencing similar issues.

hi guys

i tried to create a Virtual HDD on Hyper-2012R2 Core however it won't allow me to !

new-vhd : Failed to create the virtual hard disk.

any suggestions ?

Hello, 

I realized this strange problem with Windows 2008 R2 VMs running on Hyper-V Server 2012. My Hyper-V Server 2012 host has been running mix of VMs just fine. I've a Linux VM running, a couple of Windows 2012 R2 VMs, a Windows 8. 

I created three new VMs, gave them decent hardware. 4 GB of RAM each. A fixed VHDX file of 40 GB. I left processor allocation to Hyper-V. Windows 2008 R2 ISO was mounted to all three. Installation started. The VMs were plugged into an external network to access internet for Windows activation and software updates. 

Installation went smooth. I could log on and kick off windows updates installation. it took a reboot but when it came back, strange things started happening. 

First, after VM won't respond to CTRL+ALT+DEL command from the VM console; saying 'VM doesn't did not respond to command'. I inserted integration start up disk from Media Menu on VM's console window. It allowed me to log on this time. I continued to download/install windows updates to update and complete that. All important updates were selected (even in first step above) and none of optional update was selected.

This round of updates download/install updates finished and VM rebooted. Again, when it became available it stopped responding to any of commands sent to VM, Reset, Stop,Shut down, Turn off and won't allow CTRL+ALT+DEL. Strangely this time it didn't like accepting mounting integration services start up disk. The message displayed; when any of these actions were performed, is "RPC service not available".

What could go wrong with Windows 2008 R2 VM created just now behaving like this?

Did someone experience issues like this with just built Windows 2008 R2 VMs? Please share and advise.

Thanks.

Regards, 

Shahzad.

Hi,

small business <10 people with a small server running 2012 R2 doing DC, file serving and hyper-V with 2 guest VMs, 1 running a small db app on one of the guest VMs (quickbooks enterprise DB) and the other running an old internal single-user progam we need for (!)

as the root is acting as a file server (although this is easy enough to change but I dont want too many VMs as its not exactly a monster of a server or anything), the guest VM needs to access a largeish shared file which is currently stored on the root and is accessed via a share.

This file is currently 450MB and is the quickbooks company file (no, it wont shrink any more).

Whats the best way to setup this file ?

1) as it is on a share on the root, that the guest VM accesses as a share using the virtual adaptor

2) inside the guest VM vhdx ?? (a bit scary).

Will #2 faster or slower (assuming it were all to end up in the same RAID array as it it were on the root but now inside a vhdx) than accessing via virtual switch to a share on the root (same physical raid array but over the virtual switch layer as opposed to the vhdx layer)

if #1 is faster, I assume I get better performance if the guest VM access the shared file from the HOST via an internal virtual switch vs dedicating a GB NIC (via a virtual switch that does not include the host NIC) to the qb guest VM and having it communicate via actual wires to the host (surely the internal virtual switch has to be faster)

what if guest vm and host share an external virtual switch, is there any performance difference in terms of guest accessing host if the host is also using external switch for other network jobs ?

should I setup a) internal virtual switch for just guest -> host operations and then b) use "dedicated" NIC for guest -> external and another for host->external ?

is there another, better way ? i.e. qb server on the root, not in a vm, accessing local file on the root