I have installed Hyper-v 2012 on 2 servers, hyper-v virtual machine management service working fine with "local system" account. but when i try to start the service with Domain Service account (Run  "Log on as" a service ). the mentioned below error message appear.

Hi All: We have a couple of non-virtualized servers (one SBS, one AD-integrated member server) that needed to be replicated to a remote location as part of a DR strategy. Last year our vendor set up a VMware-based solution with two VMs, but because the primary servers were not VMWare-based, needed additional software (DoubleTake) to handle replicating the primary (non-vitualized) servers to the VMs.

Jump forward to today, and we are needing to add another two servers to our domain (a terminal server and a web development server). I would like to virtualize the two servers, and they need to be added to the DR replication.

My question is, in taking a fresh look at our needs, would I be better "served" to use Hyper-V on this server, and eventually try to migrate the DR server VMWare to Hyper-V as well?

If I did migrate the DR server to Hyper-V, is there any way to replicate the existing standalone servers to the DR servers, as we're doing now with DoubleTake?

Or would I have to virtualize the existing servers to create 4 VMs, and then migrate the DR server to Hyper-V and configure replication for all 4 instances?

Hi,

I hope this is the right Forum to post my problem, because it is a little bit mixed up with hyperv and windows failoverclustering.

My problem is the following:
I have three physical server, that host some hyper-v clients. Lets call them srv01, srv02 and srv03. All three are running Windows Server 2012 Datacenter with all updates and actual drivers. All Servers are Dell PowerEdge R710. srv02 and srv03 are absolute identical except that srv02 has 288GB RAM and srv03 has 144GB RAM. srv01 has a different processor and motherboard. RAM is 288GB too.

I installed a Windows Server 2012 Datacenter on srv01 and srv02 as a hyper-v client. Lets call them hv01 and hv02. I installed all available updates via Windows Update. After this, I tried to create a Failovercluster with using the windows-feature. While creating the cluster from hv01 with hv01 and hv02 as a node, the creationprocess failed with a timeout to hv02. When I try to create the cluster from hv02, the process timed out to hv01. When I created the cluster with just one node, the creationprocess finished successful. Then I tried to add the second node to the existing one-node-cluster, but it failed again with a timeout.

After two days of searching analysing etc. I moved hv02 to srv01. So hv01 and hv02 are running on srv01. After doing this, the clustercreation with both nodes was successful. Now I moved hv02 back to srv02. That results in a not available clusternode - so hv02 was not available in the failovercluster.

Then I moved hv02 to srv03. And voila: the cluster was up. I tested some configurations and figured the following out:
hv01 and hv02 on srv01 - works
hv01 on srv01 and hv02 on srv02 - fails
hv01 on srv01 and hv02 on srv03 - works
hv01 on srv02 and hv02 on srv03 - fails

After this, I was a little bit confused, because I thought it might be the different hardware, but that doesn't make sense, because srv02 and srv03 are identical and srv02 is not workling.

So: Anyone has an idea what the problem can be?

Hi all,

I have a HyperV server (W2008 SP2 64bit) with 2 virtual machines and each of this OS is connected to domain.

In HyperV administrator/virtual network options is one virtual network as extern (joined to physical adapter).

With this settings, I am not able to connect to any shared folder in my domain, but only from Hyper-V machine. From virtual machines works all fine. If I clear this virtual network, then it works. Outside connections to HyperV shared folders are ok.

I checked all of network settings, tried to switch LAN-adapters, remove from domain, but without an succes until now.

Can anyone give me an advice, where could be the problem?

Many thanks in advance.

Robajz

Hey!

I have two Hyper V Windows 2012 Hosts, on the first host a running 3 virtual machines.
for all the 3 guests hyperV replica is activated to the second machine.

I try to do a planned failover, which didn't work (it stopped in the last step with the following message:)

'xxxxxxx' could not initialize. (Virtual machine ID D0DE6F58-101F-4F45-94A8-1AF19E4A7F1B)

'xxxxxxx' could not create or access saved state file D:\HyperV\Hyper-V Replica\Virtual Machines\D0DE6F58-101F-4F45-94A8-1AF19E4A7F1B\D0DE6F58-101F-4F45-94A8-1AF19E4A7F1B.vsv. (Virtual machine ID D0DE6F58-101F-4F45-94A8-1AF19E4A7F1B)

The same message appears when i try start it manually on the second server

Hello!

We are setting a two node Hyper-v Cluster using a EMC VNX5300 storage. The servers are HP DL380p with Brocade 815 Fiber Controllers. The strange thing in this configuration is that the servers are directly attached to the storage and the Brocade controllers are set to use the FC_AL (Arbitrated Loop) instead of P2P (Point to Point Protocol) through the brocade manager (windows app not BIOS) . With the above settings I can successfully add LUNs to servers and use the storage. On the hyper-v side I have the following problem: I have successfully added the quorum and I can switch it between the nodes but when it comes to add a CSV volume I get an error when trying to change the owner node = (Element not found ) and then the CSV enters a failed state. I will appreciate any help with the current configuration!

Thank you in advance!    

I transferred my AD lab from VMware ESXi 5.1 to Hyper-V 2012 Core. I have only 1 server to act as Hyper-V host, but during the migration I wanted to join the host to my domain, so temporary I had another Hyper-V client on W8 machine, started the DC.

Everything else worked fine, I even managed to create several networks via virtual switches, and I also enabled RRAS on a Hyper-V host. Then I created last network for nodes in different pool, and after next time, when I powered up my Hyper-V host, connection the DC was lost.

I have 3 different units, lets call them:
A = Hyper-V host with RRAS, and several NICs
B = W8 client with Hyper-V client
C= DC sitting on a client Hyper-V

A can access B, but not C
D can access both
C can access B, but not C

I copied DC to Hyper-V host, thought I could start it from there, reconfigure network and access to DC there. Nope - DC will start, but console connection via Hyper-V is not possible, because of some layer of security.

Last option - I´m trying to enable GUI on Hyper-V host. Tried to used powershell, dism, server manager dashboard from B to A. Everytime the result is the same - cannot download source files, even if I specify source as DVD media or install.wim

Hello!

I have built the cluster with 4 Hyper-V cluster hosts and a storage over SMB 3.0. Everything is working fine on the hosts and storage when I copy a file of 4GB+. The problem appears when I copy the file to one of the VMs that is hosted on the storage.

Here is what I get:

The speed in this case falls to 15MBps. In the beginning it was looking good for about 10 seconds. The speed was averaging to 90MBps. I am copying the file from another physical workstation outside of the cluster but connected to the same physical switch.

Any idea on why it can happened? Have I created the SMB Share wrong? Configurations? The same host can accept the same file with the full 1Gbps speed.

Thank you!

Hi guys I'm looking to setup a Hyper -V environment containing a domain controller which will have WDS/DHCP/DNS server which is completely private of the Host Domain.

The Host is not on the domain but has a static IP with DNS pointing to our network.

My Virtual DC and clients can communicate together using a "private virtual machine network" however they do not have access to the internet.

I don't want to assign a internal network as that then allows the Virtual DC and client see our HOST Domain. (Can ping the domain name as DNS is on the HOST Server.)

Any one have any ideas how I can route only internet to the vm's without them seeing the host domain or even the domain seeing those Virtual clients?

I understand External network will provide full visibility to the domain

Internal will allow visibility via the HOST Server (which is off the domain) but DNS will allow visibility to the network?

Private is completely private which is ideal but no internet access :(

any ideas please

I have now had 4 Server 2012 VMs fail to boot after a hardware failure in the cluster, requiring the servers to be rebuilt. This has happened in a span of 2 months since we started deploying this configuration and using Server 2012.

This has happened at 3 different locations, meaning it is NOT tied to a specific SAN, switch, or server.
-The first and second failures was when the Hyper-v servers both BSOD at the same time, causing the guests to die. BSOD was due to a network driver issue, and both systems receiving the same bad packet.
-The third failure was in our lab as we were building the cluster prior to production deployment. We had a power outage that killed the SAN, but left the storage and switch running.
-The fourth failure was when we had the switch doing iSCSI reboot on us. None of the Server 2008 machines were effected, but 1 of our 2012 Domain Controllers BSOD and needed to be rebuilt from scratch.

Here's the hardware setup for each location. I have this setup in 15+ locations, the problem has happened in different locations, so it is not specific to one location's hardware.

-2 Cisco UCS servers running Server 2012 Datacenter with Hyper-V in a cluster.
-Nimble storage array for iSCSI volumes.
-HP switch for iSCSI backbone.
-All hardware and drivers are being updated at the time of the build.

The dead systems all share these things:
-Running Server 2012 standard
-Domain controller
-created from the same template VHDX file

At this point I have no faith that any VM will survive any sort of hardware crash or power outage. I can see it occasionally causing a VM to not boot after a crash, but we've had 5 system crashes, and of those 5, 4 of them have caused me to rebuild a Server 2012 guest VM. That's an 80% failure rate.

Anyone else experiencing this level of failure?

I've been doing iSCSI VMs on VMware for 6+ years, seen countless crashes, and never had to rebuild a VM because of it. This is my first go at hyper-v. I'm not trying to bash it and say VMware is better, I'm just amazed at what I'm seeing, as it's not expected.

I've followed all the guidelines of MS and the storage vendor for iSCSI configuration. The problem doesn't appear to be storage related though. The VM will boot, so the VHDx file is not corrupt,it just seems that Server 2012 as a VM is not very crash resilient.

I have some systems in the lab now getting ready to ship, I am going to see if I can BSOD a Server 2012 guest running on local storage.

Over the past couple of months I have experienced 4 dead 2008 R2 SP1 domain controllers after power failure on Hyper-V 2012 hosts. The domain controller VMs will start after power failure and have varying degrees of file system corruption. In each instance the corruption has rendered the domain controller unusable. The problem has not occurred with every power failure, but in testing the failure rate has been over 10%.

The Hyper-v 2012 hosts are as follows:

• Dell PowerEdge r720 with flash backed write cache on Raid controller
• Dell PowerEdge T710 with battery backed write cache on Raid controller
• Dell PowerEdge T310 with a single SATA hard drive and write cache disabled
• Generic system with a single SATA hard drive and write cache disabled

The VM configuration experiencing corruption is as follows:

• Each VM was created from a base 2008 R2 SP1 syspreped VHDx image template file (40 Gigs)
• The image template was originally created as a VHD and was then converted to a VHDx
• The VHDx file has 512k sectors instead of the native 512e of VHDx files (a result of VHD - VHDx conversion)
• Each VM was assigned 1024 Meg RAM and 1 virtual processor
• The domain controllers were created by promoting the base 2008 r2 install to a DC after base image deployment
• Only one corrupt VM was not running the 2012 integration components. The rest were running current 2012 integration components

I have done extensive testing on this issue and the problem for me seems to revolve around the VHDx file format. I have managed numerous Hyper-v installations since the original 2008 server version was released and I have never seen corruption like this until 2012 and VHDx.

For the past few days I have been testing fixed sized VHD VMs on a 2012 host and I have not been able to reproduce the data corruption issue. I seem to only be able to reproduce the problem when using dynamic VHDx files. I have not done any testing on 2012 hosts with fixed size VHDx files or dynamic VHD files.

It would be great to hear from anybody else experiencing similar issues so that we can compare notes and hopefully get to the bottom of this problem.

Hi everyone,

I have a question to ask. I'll setting up a 2 host Hyper-V 2012 Datacenter with Replica function and 4 VM's inside them. I would like to know if it's good practise to configure the Virtual Machine Disks in a shared location located in a physical File Server.

- Is there any problem or consideration to setting up this shared storage in a Replica infraestructura based in certificates?

- It's better to have the Virtual Disks in the same Virtual machine location or it doesn't matter if I put the virtual disks destination to an external File Server?

I've read many TechNet Articles and forums but I haven't got the correct explanation.

Thanks in advance.

Best Regards,

Tecnico Superior de Sistemas

I've been trying to get this going without luck, still getting this error message:

Failed to add device 'virtual hard disk'.

The machine account 'Hyper-V virtual machine management service' or the user initiaing the VM management operation or both do not have the required access to the file share.

is it possible, from a hyper-v machine, to create a virtual machine in a shared drive (win2012 server) but in a workgroup environmenent ? It seems not possible after everything that I tried...

thanks

Hi all,

I am new to Hyper-V, and my Server is 08 R2, It is a HP DL360 G5, build-in have two NIC port, I call it P1 & P2.

The P1 is connect to a LAN switch and setting a FIX IP for it such as 192.168.1.159/24 etc.

The P2 haven't connect to any switch and setting any IP on it.

OKay ..

Then on R2 Roles, I choose install the Hyper-V Wizard, following up the screen, one of it stop at NIC screen in the wizard, it suggestion don't using the P1 for management using. (Yes, I see two NIC on this list there).

So... for a new like me, stop at this screen, will have one question, if I choose the P2 for the Hyper-V, do I need plug it in the switch and give it a FIX IP like 192.168.1.21/24 etc on same sub-network, or I need give it IP like 10.10.10.21/24 etc to make it indv and security etc.

If on above case the answer is yes and 192.168.1.x/24m, then under this Hyper-V install other Server 08 R2 or Server 2012 in it, how many NIC card can for the server using? They share the same NIC card or I need buy more NIC card for one VM by one VM? And if one NIC can work for all VM in Hyper-V, then they all share the same 192.168.1.x/24 network or something I can setting under the VM in Hyper-V?

I ask too many questions, but real want to starting learning this new technical for me.

Thank you of your time and help

Best Regards,
Jimmy Chan
http://explorerhome.dyndns.org/blog

Hi.

I'm trying to install hyper-v on windows server 2012. After the install of the hyper-v roll is done the server need to be restarted. After the restart i cant log in. I try to hit ctrl+alt+del but nothing is happening.

Any one have a solution to this?

Best regards,

Marcus 

Zorky HPC

hi all

using disk2VDM

I have successfully converted 2003 to hyperv that had a hardware raid but just 1 volume.

Now I am trying to p2v a 2003 (non dc) server that has 2 X 250 Gb with software mirror but partitioned as 2 drives C +D

Disk2vhd creates 2 drives but when I start up the VM it hangs as detect errors on D: and runs the repair but goes nowhere.

If I remove the D drive it does boot off C very OK.

So tried to p2v just the D drive but see it create 2 files xxxx0.vhd and xxxx1.vhd  with different sizes !!!! What gives and why?

neither work

As the D is just a data drive I could just create a new one in my hyperV instance and copy the data over, manually recreate shares etc  and go that way if I don't succeed or get help from all the clever guys out there.

thanks for any comments help you can throw my way :)

I have virtual machine on windows server 2012 Hyper-V with 1 virtual hard disk and 2 partitions(C and D)

how i can extend C partition?

i tried to extend the virtual hard disk but when i login to virtual machine i found 3rd partition added to the disk 0 unallocated space.

is there any way to do that ?

Thanks,

Hi,
I enabled Hyper-V role in the Microsoft Windows Server 2012 on testing computer (PC with i7 CPU and 16GB RAM). I found very strange behavior. The sleep mode was enabled and after command “powercfg /hibernation on” the hibernation is also working.

I tested sleep (S3) and hibernation with started hypervisor and with running virtual machine. I tested sleep and hibernation triggered by power button and even with time-out that was set in the Power Options (I set sleep after 1 minute and later hibernate after 1 minute and wait).

Sleep and hibernation is working! I do not understand why. Sleep and hibernation should be functional only on Client Hyper-V on Windows 8 and not on the Server 2012.

Some examples:
--------------------------------
Testing workstation (i7, 16GB RAM) with Server 2012 and with started hypervisor:
--------------------------------
C:\Users\Administrator>powercfg /a
The following sleep states are available on this system:
    Standby (S3)
    Hibernate
    Fast Startup

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.

    Standby (S2)
        The system firmware does not support this standby state.

    Standby (Connected)
        The hypervisor does not support this standby state.
        The system firmware does not support this standby state.

    Hybrid Sleep
        The hypervisor does not support this standby state.

--------------------------------
My laptop (i5, 8GB RAM) with Server 2012 and with started hypervisor:
--------------------------------
>powercfg /a
The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        An internal system component has disabled this standby state.
                Hypervisor

    Standby (S2)
        The system firmware does not support this standby state.
        An internal system component has disabled this standby state.
                Hypervisor

    Standby (S3)
        An internal system component has disabled this standby state.
                Hypervisor

    Hibernate
        An internal system component has disabled hibernation.
                Hypervisor

    Standby (Connected)
        The hypervisor does not support this standby state.
        The system firmware does not support this standby state.

    Hybrid Sleep
        Standby (S3) is not available.
        Hibernation is not available.
        The hypervisor does not support this standby state.

    Fast Startup
        Hibernation is not available.
--------------------------------

R. Revil

Relef Revil