Hello,

I had a problem with one vm showing status backing up.

I read on TechNet that restarting the hyper-v virtual machine management service would solve the problem.

I have tried to shutdown the service but it now says status stopping...

How long time does it take to shutdown the service? Is there anything I can do to hurry it up?

ps. I have production vm running on the host that I can't take down...

Regards

Roger

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 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

Hello,

I have an Windows 2008 Standard x64 machine. In "system event. log" appear every 10 minutes  events 1103 (source DHCP-client):

Log Name:      System
Source:        Microsoft-Windows-Dhcp-Client
Date:          ....
Event ID:      1103
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     

Description:
Your computer was successfully assigned an address from the network, and it can now connect to other computers.

Any thoughts on what could be causing this event to appear?

Thank in advance for your help.

Jazabra

Dear Sir,

I am having one DC & ADC server both on Hyper-V machine , suddenly i login and noticed that 

my ADC server is down . Please suggest what should i have to do.

Thanks,

Regards, Ravi Kumar

hi

I am having a problem with connecting virtual machine install on Hyper-v to external network.

i attached to my message a visual explanation of how my network and server are configured.

can anyone help please..

thanks

Hi,

Host 2012R2 with Hyper-V-role, Backups are done with DPM 2012R2.

While job is working, three warnings are recorded in event-log of the guest:

partmgr / Event ID 58 / The disk signature of disk 2 is equal to the disk signature of disk 1.

partmgr / Event ID 58 / The disk signature of disk 2 is equal to the disk signature of disk 1.

partmgr / Event ID 58 / The disk signature of disk 3 is equal to the disk signature of disk 0.

This happens in all guests (with different disk numbers). No corresponding error on Host or DPM. Registry of each guest is growing in these keys:

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

The popular hint "attach the VHDs, bring them on- and offline, detach" brings no solution. As Mike Jacquet from Microsoft told in this thread, it is a problem of Hyper-V and not DPM.

Has anyone a solution for this? 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?

Isaias

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?

Have followed all of the recommendations her in regards BPA Error, like adding Hyper-V into the registry. Then scheduled Server Backups that seem to be running as the date keeps changing.

So why again today I am getting the BPA error "One or more virtual machines have not been backed up in the past week.", when it has been backed up successfully the last three days according to the wbadmin console.

All of the trouble shooting documents I have read say this is so easy to schedule a server backup of the VM's and I thought it was but because I am still getting the BPA error I am thinking that either all of these articles are wrong or there is more to it that I have not found. But if I cannot find it here, where would it be?

Mark M.

Hi everyone,

I was configuring virtual switch on  my HYPERV 2012R2 CORE via SCVMM2012R2 and accidentally messed up my network connection to the host. I logged in to the host via console and found that my NIC has been replaced with vswitch. Is there any way i can revert my NIC settings to old state???  I tried using nvspscrub tool in my host to reset my network settings but it didnt work in my 2012R2 host!

IS there any other alternative or powershell commands to revert back my NIC settings to default???

What does "By default, resource meteringcollection interval is one hour" mean?

Does this mean that every hour it will collect information or it will collect data for a period of one hour? If it collects data for one hour, does the data get collected every second (like perfmon 1 second sample interval) and what happens after one hour? Does it stop collecting data?

Thank you,

Alex

I am running Windows Server 2012 R2 Essentials as a VM on Hyper-V Server 2012 R2 (server core).  In checking MSINFO32 I see "Secure Boot State" is "On" for Essentials, but given my current configuration I believe this should be "Off?"

I setup a new Hyper-V Server 2012 R2 (server core) using an Areca ARC-1224-8i RAID controller.  It was unclear to me whether or not the Areca RAID controller would support UEFI or not, but since Secure Boot was desirable I decided to try a UEFI installation. I created two volumes on the RAID controller.  C drive of 80 Gb and D drive of the remainder (about 9 Tb).  I checked the file C:\Windows\Panther\setupact.log and saw the message which told me this was an EFI installation/boot.

After Hyper-V was installed I then setup Essentials as a VM on the D drive.

When I ran MSINFO32 in both Hyper-V and Essentials and I saw the Secure Boot State was On which was expected (and desired) for both OS levels.

Several days later I started having problems.  The system seemed to have crashed and during multiple attempts to reboot the Hyper-V server couldn't seem to detect the RAID controller.  If I tried a new Hyper-V installation and loaded the RAID driver the RAID controller was seen, but when Hyper-V itself tried to boot it seemed as though the RAID driver was not being loaded and thus the RAID controller could not be found (and along with it my C boot drive was missing)?

Since I had some suspicion that the RAID controller might not support UEFI I decided to re-install Hyper-V, but this time using the Legacy BIOS.  After the installation was completed I again verified the setupact.log and saw BIOS rather than EFI (as expected).

I then re-attached my Essentials VM (which was left untouched on the D drive) and got everything running again.

But now when I check MSINFO32 within Hyper-V it showed Secure Boot State Off (expected given that UEFI was not used).  But when checking MSINFO32 within Essentials it showed Secure Boot State On.

I thought one purpose of Secure Boot was to create a chain of trust.  Given that Hyper-V can no longer verify this chain (since UEFI is not used) I would have expected any VM running above Hyper-V to be in the same state, i.e., Secure Boot State Off? When the underlying Hyper-V layer changed I would have expected that to change Essentials view of the world?  So it looks to me as though this is not being handled correctly?

Thanks for any assistance you can provide.

P.S.  In case this makes any difference I am using a motherboard with a TPM and both the C and D drives were encrypted with BitLocker.  The C drive used a TPM key and the D drive had a password and was setup to autounlock.

After I re-installed Hyper-V on the C drive I then manually entered the BitLocker password in order to access the Essentials VM on the D drive.

Theokrat

Started happening after tried to add external switch using WiFi.

Now, VSM shows 'Load Failed' for the switch. Immediately after stating s/w manager VMM service crashes. I am unable to add a new virtual switch.

Any help will be appreciated.

Thanks

Jas

Hello Members

(I am a VMware guy. First attempt at a Hyper-V Deployment).

Here is a brief outline of my new Hyper-V infrastructure which has been setup for a very small branch office:

1. 1 HP DL380p G8 Rackmount. 2x Intel Xeon Quadcore Procs. 32GB RAM. 4 Port 1GBps NIC.
2. IBM Storwize v3700 iSCSI SAN. 4x 500 GB SAS Drives on RAID5.
3. Microsoft Windows 2012 Hyper-V. This is standalone with no clustering at the moment.

*********************************************************

Here's the Hyper-V Networking Design which has been currently configured between the HP Host and the IBM SAN

1. 2 NIC Cards TEAMED for Service LAN and Hyper-V Management.
2. 2 NIC Cards TEAMED for iSCSI SAN Connectivity.
3. NIC TEAM configured for Service and Management is on 10.40.0.0 /16 Subnet & configured with 10.40.0.1 gateway
4. NIC TEAM configured for iSCSI is on 10.50.0.0 subnet with no gateway.
5. NIC Ports configured on the IBM SAN are on 10.50.0.0 subnet with no gateway.
6. The Switch to which both the HP Server and the IBM SAN connects is on the universal VLAN (default).
7. The Switch is connected to an uplink router (10.40.0.1)
8. Hyper-V vSwitch is connected to the Service LAN TEAM (MS Network Driver Multiplexor Driver).
9. Hyper-V VMs are configured with Dynamic MACs (default) and Hyper-V Integration Services.

*********************************************************

Here's the issue i am currently encountering

1. The 1st Virtual Machine boots up. IP is Static and belongs to 10.40.0.0 subnet. NIC connectivity to the External network and Internet is fine.
2. The 2nd Virtual Machine boots up. IP is Static and belongs to 10.40.0.0 subnet.NIC connectivity to the gateway fails and times out. No connectivity to the internet as well (understandably).
3. I power the 2nd virtual machine OFF followed by the 1st.
4. I power on the 2nd Virtual machine first. IP is Static and belongs to 10.40.0.0 subnet. NIC connectivity to the External network and Internet is fine.
5. I power on the 1st VM following the 2nd VM. IP is Static and belongs to 10.40.0.0 subnet. NIC connectivity to the gateway fails and times out. No connectivity to the internet.

*********************************************************

I researched the Forums and the KBs.

1. Few of the forums suggest that this is an issue with MAC Address Filtering being 'enabled' on the switch.
2. Can anyone confirm if this could be the problem or should i be looking somewhere else ?
3. If it is indeed the issue, is this feature (MAC Address Filtering) configured on a Switch or a Router (I am not a networking guy) ?
4. Also - if someone could guide me on how i could disable this feature on the switch/router (i will have to find out the priviledge mode password and everything for the router/switch i believe).

I am running on a tight schedule here (when are we not .. ? )

THANKS A LOT TO ANYONE WHO COULD HELP!

We have a 9 blade Hyper-V cluster and unfortunately, each blade was only specced out with 2 x 10Gbps NICs. Right now each is configured in a team, with Live Migration, VM, and iSCSI traffic all flowing equally.

I'm going to separate them out tonight by breaking the team and assigning one for VM and Live Migration traffic and the other dedicated for iSCSI traffic.

Is there any reason I shouldn't configure it this way, are there any other tweaks I should make?

I had Both Virtual Box and Hyper-V on the same machine, I decided trying to shut down Hyper-V all the time was too much trouble so I removed VirtualBox.

Since then no machine can get a local IP address from the router.

I have even setup the virtual connections again:

I have various CentOS installs which I installed with generation 1.

I even tried changing the LAN Adapter to a "Legacy" one, but it still fails.

Any advice as to what is going on with this?

Thanks

I'd like to share an issue which occurred during one of my recent configurations as well as the associated solution which worked for me.

While configuring Hyper-V Manager on a non-domain joined Windows 8.1 Enterprise client, to communicate with a non-domain joined Microsoft Hyper-V Server 2012R2, I received the following enjoyable message:

Hyper-V encountered an error trying to access an object on computer '.....' because the object was not found. The object might have been deleted. or you might not have permission to perform the task. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.

As it turns out I forgot to change the machine name on the Hyper-V server. It's worth noting that it's also necessary to add an entry in the client machine's HOSTS file which matches the computer name of the Hyper-V server.