Hi,

I would like to realize an infrastructure with Hyper-V or other.

In this infrastructure I would have a master and children, but I would like to modify the master (update, new software ...) when I want without that links with the children breaks.

I tried to create differential hard drive with Hyper-V, but off course the like break when I perform a modification in the master VHDX :s

Could you help me ?

Hi All,

I already have VM's running on the physical hypervisor. I have two hosts, both with VMs on. I'd like to use an iSCSI Lun and setup HyperV Failover. I will obvously have to move some of the VMs at some point. Can I set this up with the VMs spread accross two machines already? Or do I have to move them first?

Kind regards,

Hi!

Hyper-V on 2012.

I've got a Ubuntu, 12.10, server installation which i try to add some storage to. I've created 64GB harddrive (VHDX) as the 1st drive. And then a 2nd drive 4TB (VHDX). Thin.prov on both.

Creating and formating: Using gdisk, parted or gparted (livecd) on ubuntu I'm not able to partition, GPT, and initiate a filesystem on the the large VHDX.

Is there a problem with Hyper-V 2012 and drives (VHDX) >2TB when used by guests?

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!

Hi everyone,

We have a 2008r2 server which has 2 Hyper-V VM's running on it.  Hyper-V settings for the Virtual Hard Disks and Virtual Machines is set to the D drive. We have a real time replication of the VM's through a piece of software called DoubleTake to a server in a data centre.  One of the prereqs for Double Take is that nothing related to the VM's can sit on the system drive (C drive).  Unfortunately on trying to setup the replication, Double Take, complained that the VM was on the C drive.  After talking to the suppliers of the software they informed me that this folder also needs to be moved from the C drive to another partition:

C:\ProgramData\Microsoft\Windows\Hyper-V

The above folder contains the following folders and file:

Snapshots
Snapshots Cache
Virtual Machines
Virtual Machines Cache
InitialStore.xml

Can anyone please advise me how to correctly move this folder without harming the 2 VMs?

Thanking you in advance for your help and time.

Best Regards,
Jazz

Hello All,

I am trying to transfer a web application hosted on a pair of Hyper-V 2008R2 VMs from one site to another with minimal downtime. The problem I'm encountering is that the time it would take to export the machines, transfer them to the other site, import, and spin up is unacceptable in the eyes of management. I am wondering if it would be possible to simply

• export the VMs a week ahead of time
• import at the new site

Then, on migration day, 

• take snapshots of the past week on the original two
• copy the differencing disks over
• and apply the snapshots to the two new VMs

However the only snapshot export functionality offered merges the snapshot tree down into the vhd, making that export the same size as a full export. Can I just copy over the AVHD files after I've taken the snapshots? What would that process look like?

Thanks in advance for your advice!

Michael

Hi Guys,

Got a bit of a strange issue that I've not come across before (on either R2 or v3)

Configuration is a two node cluster using shared storage (Equallogic). Had an issue initially with the nodes not registering their SPNs thus live migration was failing... registered them manually which fixed live migration but still getting the 14050 errors in the VMMS log. Both servers running Windows Server 2012 and are fully up to date. The physical servers are a R710 and R720 (slightly different processor models) - and are fully up to date with the dell management s/w and firmware. 

Now having an issue creating fixed VHDs or VHDXs (makes no difference) from either the Failover Cluster MMC or the Hyper-V MMC. The operation 'seems' to work however the progress bar that you usually sit and watch when creating a large fixed VHD appears then disappears on the screen. Sometimes you don't see it, sometimes you see it but the progress bar goes up rapidly. Have tried different size VHDs to no avail. Have tried creating the VHD via PoSH however the same happens, the progress bar in the PoSH command line goes up really fast... whereas when I do it on a functioning cluster it goes up slowly. 

I suspected something may be up with the LUNs/CSVs, however I can browse to the ClusterStorage volumes and copy a large amount of data in to them with no issues.

Has anyone come across this before I blow the cluster away and rebuild the OS on the nodes? 

Thanks
Steve

Hi,

I need to build a new server that uses Hyper-V and provides very good file read/write speeds for a database application. The database is a flat file database and doesn't have any SQL component or anything like that.  It just uses a shared folder.   Currently it's running as a HyperV server on a 7.2k RAID1 hard drives and it's very slow.

The scenarios I have in mind are:

1. Install the OS on 7.2k RAID1 drives, then keep the database shared folder on an attached Static VHD that resides on an SSD in RAID1.

2. Same as above, but instead of using an attached VHD, use the internal hard drive pass through feature to give the VM access to the SSDs directly.

3. Install the OS and application server on the SSDs on a single VHD.

Option 1 and 2 use the same hardware, but option 3 would require buying 200GB SSDs instead of 100GB SSDs.  So does anyone have a preference or perhaps another option that I haven't thought of?

Hi,

I have a Windows Server 2008 R2 failover Cluster and I installed a new VM running Windows Server 2012. When I configured the backup to this VM using DPM 2012, the backup is offline (Saved State). 

I've checked with diskshadow and the Hyper-V vss writer, always gives me the same thing, backup to this VM will be using saved state.

Why can't I run an online backup, using snapshot? Is'it a problem with Hyper-V R2 and Windows 2012 Child VM?

Note: I already checked all the conditions why the backup of a VM could be running on saved state and none of them are applicable to my scenario.

Regards,

Carlos.

I really need some help here!

Here is my setup:

1. Two Windows Hyper-V server 2012 joined to our domain.
2. Firewall on Hyper-V server disabled
3. Windows 8 Enterprise Workstation “client” with RSAT installed.
4. DCOM access permissions set for anonymous

From the client I am able to connect via Hyper-V manager and Server manager. No issues or errors.

Problem:

When I try to create a VM on either of the two servers, the wizard gets hung on “Creating the new virtual hard disk” stage. There is no animation shown…I mean the blue bar which goes from left to right.

The same thing happens if I try to create a virtual hard disk [either expanding or fixed, VHD or VHDx].

Interestingly, this behavior is exhibited only on these two domain joined servers. I have another server which is standalone…that works fine.

I have been pulling my hair out for the past three days on this problem. Searched on ‘net , tried all scripts, workarounds etc etc. I suspect there is something in our GPO which is causing this. I don’t have permissions to modify GPOs here.

Where should I look to solve this issue? I really need to start using those two Hyper-V servers for new server VMs.

I  have already looked at these threads:

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/c97354f8-3f39-4ae0-969d-0c34b9e3f67b

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/6f791bbc-a683-4495-934e-e2c7d81ef9dd

Note:

1. I know running them with firewall disabled is a no-no…but I had so many issues enabling rules in the firewall that I gave it up…and disabled it altogether.
2. I am running the Hyper-V 2012 server, not the Hyper-V role on a Windows 2012 server. I guess someone people call it the free Hyper-V also. It looks like the Hyper-V on a 2012 Core.
3. I installed Hyper-V 2012 on these servers without using SmartStart CD or similar tools.

Hi, I'm trying to set up VDI across Windows Server 2012 VMs running on Hyper-V 2012.

The wizard's compatibility check for the Virtualization Hostserver failed with "Hardware-assisted virtualization is not present on the server".

I'm running an FX-8120 CPU and have the ASUS M5A97 motherboard. 

I know I'm supposed to enable No-Execute (Hyper-V Hardware Considerations) but Icannotfind that or any other synonyms of it in my motherboards UEFI BIOS (NX, XD, EVP, XN... nothing). 

I found this:

PAE/NX/SSE2 Support Requirement Guide for Windows 8

which in short says "Windows 8 and Windows Server 2012 requires that systems must have processors that support NX, and NX must be turned on for important security safeguards to function effectively and avoid potential security vulnerabilities."

this leads me to believe NX is on by default if I was able to get this far and install Hyper-V 2012 and Windows Server 2012..

Also I tried to disable AVX in cmd with "bcdedit /set xsavedisable 1". Did not resolve

My processor is Zambezi FX-8120 and also supports RVI/SLAT:
processor: Newegg Processor FX-8120
support proof: AMD Processors with Rapid Virtualization Indexing Required to Run Hyper-V in Windows® 8

What going on here? I bought this CPU specifically after I had the same problems with an older AMD Athelon II and made sure to buy one with AMD-V and RVI.
I'm aware my MB is not a server motherboard, but I was trying to spend as little as possible to retrofit my home rig into a lab deployment. I've read a VMWare thread where someone successfully set up nested virtualization using ESXi5 with an FX-8120 and a cheap $65 Gigabyte GA-78LMT-USB3 ... Hyper-V has been a pain the whole way through from setting up remote management and now this. 

If someone suspects it's my MB can you also make a suggestion as to what features I should be looking for in a new one? NX, IOMMU, some other virtualization feature?
If you've had  similar set up, perhaps recommend an MB? Not looking to spend that much $150 max.

Thank you

I know grouping can be done via SCVMM but looking for a FREE tool. Especially now Hyper-V is available on Windows 8 and I have many test VMs that I like to manage easily with grouping rather looking all at once.

Can anyone recommend such a tool?

Thanks

Hi!

Just moved from VMWare Workstation to Hyper V cause' i thought that now when it comes with Windows 8 i could just as well use it! Well, no, not just as well because i cant figure out how i can easily set up a NAT Switch/Network in Hyper-V. What i can see on google therse two options:

1. Create a dedicated server that acts like Router / Nat -server. I dont have so much spare hardware resources.

2. Create internal switch and share your physical network adapter via ICS. This could work if i would have the option to disable the DHCP. At least change the DHCPScope. I Found some guides on how to hack this in the registry but it was not applicable on Windows 8...

Any ideas of what i could do? I actually like Hyper-V, much better interface but i really need the NAT-function and i dont want to go back to VMWare workstation.

Thanks!!

Surprisingly, none of the related topics were exactly what my situation is, nor did their suggestions translate well to my issue.

I have an HP server with dual NICS running Windows Server 2008 R2 Std and the Hypervisor role. The #1 NIC is assigned to this host, and its IP is 192.168.0.252/24, with a DGW of 192.168.0.1. It can ping any host on the network and with the aid of my remote management software is accessible from the Internet. it runs flawlessly.

The one and only guest is running Windows 2011 SBS with all its assorted roles. Its assigned exclusively to the #2 NIC, and its IP is 192.168.0.7/24 with a DWG of 192.168.0.1. It can ping itself, but nothing else. It doesnt see the router (an ASA) or anything else on the network. No amount of tearing down and rebuilding the network connection has helped.  Ive turned off the various offloading functions described in the other articles, and tried assigning other IP addresses in the same subnet, but nothing helps.

Hi guys,

Is it possible to have a VM on HyperV with NUMA configuration even if the Host machine's hardware is not NUMA? The host machine is SMP with 4 cores.

Hi everybody!

I wish to virtualize Windows Server 2008R2 (IBM 7947K6G System x3650 M2 и WinServer 2008R2) via disk2vhd v1.63 (just disk С). All is ok and after progress I have a VHD file.

I copy this VHD to new location and attach it to fresh created VM (Hyper-V 2012). 

After I try to start this new VM I see black screen and blinking white cursor on left upper left corner. That's it!

I've tried lots of ways to solve the problem:

1. I try to boot from different ERD and DART, they all say that the this version is NOT compatible with your system (and they are certainly working on dozens of previous servers).

2. I try to boot from the installation image of WinServer (from this iso I install this system before) when attempting to enter the recovery mode it is displays a message similar to paragraph 1.

3. I tyr to boot from different LiveCD (3rd party), there I see what this VHD really has a working system (drive C has a NTFS partition and another section in RAW format plus one part in fat32. They both 100 mb, but the C drive partition is not marked as active).

4. I try via Diskpart make C drive active, and I get error that it is can not be made ​​active GPT to MBR. I tried to make convert MBR, and I got an error that this type of disc can not be converted to MBR.

5. Tried to virtualize this server using MS SCVMM 2012. But agent is not start on the target physical server (but that's another story.)

I have investigation via internet and I understood that the problem is faced with the fact that my physical server have uEFI and Hyper-V have BIOS. But I havent found any proof that this is my problem.
At this point, the server successfully migrated to a new virtual machine (data transferred using standard tools and wizards), so the problem is not so urgent.

Just for the future, I would like to find out why the VHD does not start correctly (VHD to the C drive I have so I can make some tests now)?

ps http://social.technet.microsoft.com/Forums/ru-RU/virtualizationru/thread/a31151f9-1afc-4b9b-b106-f408cc7e2f37/

I have a new Hyper-V Server running in GUI Mode, with 6 NICs across two cards. The goal is to setup Host then add three Guests for various Windows Server Roles (Exchange, RDS, DC).

Being very new to this Virtual World I have a question about NIC Teaming and Virtual Switches. I understand the basic concepts of both and was working on the assumption that I could create a NIC Team for Host OS to use (using two NICs), then I would use the remaining four NICs for Hosts connectivity. When going about this I thought I would create the NIC Team for hosts then create the Virtual Switch and would of thought I was binding the NIC Team to the switch, but this was not an option in GUI.

Perhaps my strategy is all out, so what is the best solution with amount of NICs? Do I simply bind individual NICs to each VM?