I have setup hyper-v server 2012 on my server. there is only 1 VM running with 4 GB ram & 1.5 TB expanding hard drive.

I have found error in guest os "disk 1 has been surprise removed"can any one tell me what is this error exactly.  after this error i have checked hyper-v manager & found machine is showing"Merge In Progress" 

i never saw "disk 1 has been surprise removed"error. is this error occur because of hyper-v server is not configured properly.

Also i have server 2008 R2 DC x64 which is working as hyper-v host. I have checked event logs of same and found following error."The disk signature of disk 2 is equal to the disk signature of disk 1."what is this.

Akshay Pate

After a scare this past weekend, I decided to test out my backups by doing a restore of a Hyper-V guest. Good thing, because I'm running into an issue. 

We have two Windows Server 2012 servers acting as Hyper-V hosts. Both of these machines backup using Windows Server Backup to a shared drive on a Windows 7 Pro computer.

That shared drive is physically a Tandberg Data Quikstor. If you've never seen a Quickstor, it's a box that hooks up to a computer via USB and uses little ejectable hard drives for storage. Think tape drive, but little hard drives instead of tape carts.

I wanted to test a scenario where one of our Hyper-V guests was completely hosed and needed to be restored from a backup. I set up a new Windows 2012 server, installed the Hyper-V and hooked up the Quickstor directly to the server.

I fired up Windows Server Backup and tried to do a restore of one Hyper-V guest. The restore immediately fails with the error "You can only recover entire volumes from backups stored on DVDs or removable media. File recovery is not supported."

I guess the error is self explanatory but it took me by surprise. Because I stored my backups on what amounts to a removable hard drive I lose the ability to restore individual files? That seems like a strange restriction, just about any offsite backup is going to involve removable storage.

Are there any workarounds to this issue? What if I backed up directly to the hard drive of the Windows 7 machine? Could I then use that backup to restore individual files?

Hi all,

In a test environment we have a HP ProLiant DL360p Gen8 server with Windows Server 2012 R2 - Standard installed with the Hyper-V Role and no others.
On the server there is a Switch Independent network team configured with 2 of the 1GB NICs.
There is a virtual Swtich (External) configured on the Host linked to the Team with allow management selected.
The Guest VM has a single NIC (not a legacy setup) connected to the virtual Switch

The issue we are having is that once an RDP session is connected to a Guest OS, for example another 2012 R2 Server, it experiences high latency (which makes the RDP session appear to run in a very jerky way)

Using Hyper-V VMConnect, the server has no issues at all although the window is smaller.

We can verify this is being caused by an RDP session by observing ping times:

Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time=1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time=75ms TTL=127 <RDP SESSION STARTS>
Reply from 10.101.3.152: bytes=32 time=52ms TTL=127
Reply from 10.101.3.152: bytes=32 time=63ms TTL=127
Reply from 10.101.3.152: bytes=32 time=121ms TTL=127
Reply from 10.101.3.152: bytes=32 time=135ms TTL=127
Reply from 10.101.3.152: bytes=32 time=141ms TTL=127
Reply from 10.101.3.152: bytes=32 time=146ms TTL=127
......... Snipped ........
Reply from 10.101.3.152: bytes=32 time=119ms TTL=127
Reply from 10.101.3.152: bytes=32 time=2ms TTL=127
Reply from 10.101.3.152: bytes=32 time=8ms TTL=127
Reply from 10.101.3.152: bytes=32 time=14ms TTL=127
Reply from 10.101.3.152: bytes=32 time=22ms TTL=127
Reply from 10.101.3.152: bytes=32 time=72ms TTL=127
Reply from 10.101.3.152: bytes=32 time=75ms TTL=127 
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127 <RDP SESSION CLOSES
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127
Reply from 10.101.3.152: bytes=32 time<1ms TTL=127

This issue does not affect RDP sessions to the Host.

I have seen posts about disabling VMQ on the host/guest servers as there may be an issue with this model - this has had no effect at all, the issue persists after changing VMQ and restarting both the guest and the host OS.

I have seen another fix for a similar issue by running these commands: bcdedit.exe /set USEPLATFORMCLOCK on and this also has not resolved the issue.

I have also set the Guest VM to use 256Mbps minimum (512maximum - also tried with no maximum) bandwidth allocated, but again this does not resolve the issue.

There are no backup jobs or reporting jobs running on these servers (they are in test).

Is this caused by the specific hardware we have chosen or is there further diagnostics that can be performed? Any help would be appreciated.

Hello. I have just enabled Hyper-V on my Windows 8.1 laptop.
Dell Latitude E7440 i7-4600U @ 2.10GHz
I can create a Virtual-Switch but I am unable to create a new Hard Disk or Virtual Machine within Hyper-V. I get the same error for both processes.

Error: The Virtual Machine Management Service encountered an error while configuring the hard disk on virtual machine New Virtual Machine.
Failed to create the virtual hard disk.
The system failed to create C:\Users\user\Documents\Test\New.vhdx .
Failed to create the virtual hard disk
The system failed to create C:\Users\user\Documents\Test\New.vhdx . A Virtual disk support provider for the specified file was not found. (0xC03A0014).
I have ran all Dell Client System updates and all of windows updates.
I have attempted to create a virtual machine on the current SSD and also an external drive. The same error appears.
I have also attempted to create a virtual hard disk via Hyper-v with a Base vhdx, still the same error occurs. I've tested the base image on other laptops of the same model and windows 8.1 without issue.
Any thoughts on how I can fix this?

Thank you,

-Jake

I've got two machines,

Windows Server 2008 R2 Enterprise

Windows Server 2012 R2 Datacenter

Assuming everything is correctly set up in terms of connectivity and the Hyper-V Management agent service, is there a known compatibility issue with remote management through Hyper-V Manager from 2008 R2 to 2012 R2?

2012 to 2012 R2 works correctly

2008 R2 to 2012 works correctly

But 2008 R2 to 2012 R2 on ANY 2012 R2 machines does not work correctly.

Anyone have any idea what's going on?

Hi,

I currently have a Windows Server 2012r2 HyperV host, within which I would like to set up multiple networks for the purpose of testing the following subjects for my studies;

-VPN/Routing and Remote Access

-Network Policy Server

-Direct Access

Can somebody please explain how to configure a virtual device for carrying out the routing within a single physical host?

The Host is a Dell PowerEdge 1950 and has two physical NICS

Regards

Leon

Hi all, currently I just started to provide more support for Hyper-V server and all this while I been working at the data centre which uses VMware visualization. 

For our Hyper-V, we are using two HP physical host and while working with the Hyper-V administrator I was told the following-> The HP Hyper-V is able to only support 4 VMs with 2 core each and would need to buy additional server if we go beyond 4 VM machines. 

I'm not too sure how Hyper-V visualization is different from VMware but I think what I heard is very wrong. 

I'm also curious is that on VMware I could see the amount of CPU & RAM the ESX Host is using but I don't see it on Hyper-V Manager unless using the Task Manager->Performance monitor is the only way.

HP Proliant DL360e Gen8

CPU: Intel Xeon CPU E5-2403 1.80GHz (8 core)

RAM:16 GB DDR3

SAS Hard Disk

OS: Win 2012

when I try to get the vm details using GET-VM <vmname>cmdlet I get the attached error. what could be the issue ?

but when I give just >get-vm I get all the vm's running on the host.

I have few queries : where does the collected log files of vm-resourcemetering get stored ? Default window is every 1hour for collecting the data,how to increase it ?

without enabling resource metering can we get the vm usage details with just "measure-vm"  cmdlet  ?

Command : > measure-VM -VMName <vmname>

<vmname> : what should be the name here .. whether it's the computer name or the name displayed on the hyper-v manager ?

Thanks

Sparky_Maker

HA host machine start chkdsk and reboot when one of the cluser is drained(down). !

MVP in SharePoint Server 2007 ?

Hello,

I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:

IBM x3650 M4

x2 Xeon E5-2609

32GB RAM

x2 480 GB SSDs

Server OS: Windows server 2012

I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop and so far the only error logging I'm able to find is in the hosts event log. 

Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
Source:        Microsoft-Windows-Hyper-V-Worker
Date:          7/8/2014 2:14:48 PM
Event ID:      18560
Task Category: None
Level:         Critical
Keywords:      
User:          NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
Computer:      CCSTS1.cnet2k.cornerstonecredit.net
Description:
'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" /><EventID>18560</EventID><Version>0</Version><Level>1</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" /><EventRecordID>159</EventRecordID><Correlation /><Execution ProcessID="1512" ThreadID="3536" /><Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel><Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer><Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" /></System><UserData><VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events"><VmName>LegacyTS</VmName><VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId><Rax>0x0</Rax><Rbx>0x0</Rbx><Rcx>0x0</Rcx><Rdx>0x0</Rdx><Rsp>0x804de00c</Rsp><Rbp>0x0</Rbp><Rsi>0x0</Rsi><Rdi>0x0</Rdi><R8>0x0</R8><R9>0x0</R9><R10>0x0</R10><R11>0x0</R11><R12>0x0</R12><R13>0x0</R13><R14>0x0</R14><R15>0x0</R15><Rip>0x80547c7c</Rip><Rflags>0x10046</Rflags><FpControlStatus>7F030000000000000000000000000000</FpControlStatus><XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus><Cr0>0x8001003d</Cr0><Cr2>0x804ddffc</Cr2><Cr3>0xa02000</Cr3><Cr4>0x20</Cr4><Cr8>0xf</Cr8><Xfem>0x1</Xfem><Dr0>0x0</Dr0><Dr1>0x0</Dr1><Dr2>0x0</Dr2><Dr3>0x0</Dr3><Dr6>0xffff0ff0</Dr6><Dr7>0x400</Dr7><Es>0000000000000000FFFFFFFF2300F3C0</Es><Cs>0000000000000000FFFFFFFF08009BC0</Cs><Ss>0000000000000000FFFFFFFF100093C0</Ss><Ds>0000000000000000FFFFFFFF2300F3C0</Ds><Fs>00F0DFFF00000000FF1F0000300093C0</Fs><Gs>0000000000000000FFFFFFFF00000000</Gs><Ldtr>00000000000000000000000000000000</Ldtr><Tr>90685580000000006800000050008B00</Tr><Idtr>000000000000FF0700F4038000000000</Idtr><Gdtr>000000000000FF0300F0038000000000</Gdtr><Tsc>0x148e4294</Tsc><ApicBase>0xfee00900</ApicBase><SysenterCs>0x0</SysenterCs><SysenterEip>0x0</SysenterEip><SysenterEsp>0x0</SysenterEsp></VmlEventLog></UserData></Event>

My VM config

<?xml version="1.0" encoding="UTF-16" standalone="yes"?><configuration><_24984ed0-bdad-4b90-82b2-5d59f874e91e_><ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid></_24984ed0-bdad-4b90-82b2-5d59f874e91e_><_7d80d3db-61ee-4879-8879-5609f1100ad0_><address type="string">5353,00000000,00</address><version type="integer">1</version></_7d80d3db-61ee-4879-8879-5609f1100ad0_><_83f8638b-8dca-4152-9eda-2ca8b33039b4_><controller0><drive0><pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname><pool_id type="string"></pool_id><type type="string">VHD</type></drive0><drive1><pathname type="string"></pathname><type type="string">NONE</type></drive1></controller0><controller1><drive0><pathname type="string">SCSI\CDROM&amp;VEN_IBM_SATA&amp;PROD_DEVICE_81Y3681\4&amp;1864BF9E&amp;0&amp;010000</pathname><pool_id type="string"></pool_id><type type="string">ISO</type></drive0><drive1><pathname type="string"></pathname><type type="string">NONE</type></drive1></controller1><version type="integer">5</version></_83f8638b-8dca-4152-9eda-2ca8b33039b4_><_8e3a359f-559a-4b6a-98a9-1690a6100ed7_><port0><connection type="string"></connection></port0><port1><connection type="string"></connection></port1><version type="integer">2</version></_8e3a359f-559a-4b6a-98a9-1690a6100ed7_><_8f0d2762-0b00-4e04-af4f-19010527cb93_><controller0><drive0><pathname type="string"></pathname><type type="string">VFD</type></drive0></controller0><version type="integer">1</version></_8f0d2762-0b00-4e04-af4f-19010527cb93_><_a80e9c62-750a-4a6b-9548-d46677e806be_><ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid><Connection><AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName><AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName><AuthorizationScope type="string"></AuthorizationScope><ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight><Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166><DisplayName type="string"></DisplayName><Flags type="integer">0</Flags><Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814><Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=</Data><Version type="integer">256</Version></Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814><Settings><Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id></Settings></Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166><Features><Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id></Features><HostResources><HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource></HostResources><PoolId type="string"></PoolId><PreventIPSpoofing type="bool">False</PreventIPSpoofing><TestReplicaPoolId type="string"></TestReplicaPoolId><TestReplicaSwitchName type="string"></TestReplicaSwitchName></Connection><FriendlyName type="string">Network Adapter</FriendlyName><IsConnected type="bool">True</IsConnected><MacAddress type="string">00-15-5D-01-18-02</MacAddress><MacAddressIsStatic type="bool">False</MacAddressIsStatic><PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName><SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName><VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid></_a80e9c62-750a-4a6b-9548-d46677e806be_><_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_><base_board><serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number></base_board><bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid><bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number><boot><device0 type="string">Optical</device0><device1 type="string">HardDrive</device1><device2 type="string">Network</device2><device3 type="string">Floppy</device3></boot><chassis><asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag><serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number></chassis><num_lock type="bool">False</num_lock><version type="integer">2</version></_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_><_db8b9818-b4bb-4725-b99d-b4612716b6b4_><version type="integer">0</version></_db8b9818-b4bb-4725-b99d-b4612716b6b4_><global_settings><devices><allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy><generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id><storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set></devices><disk_merge_pending type="bool">False</disk_merge_pending><metrics><devicetype><deviceinstance><guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid><metric><enabled type="bool">False</enabled><lastcomputedtime type="integer">0</lastcomputedtime><peaktime type="integer">0</peaktime><poolid type="string"></poolid><resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid><starttime type="integer">0</starttime><typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode><value type="integer">0</value></metric></deviceinstance><guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid></devicetype><devicetype><deviceinstance><guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid><metric><enabled type="bool">False</enabled><lastcomputedtime type="integer">0</lastcomputedtime><peaktime type="integer">0</peaktime><poolid type="string"></poolid><resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid><starttime type="integer">0</starttime><typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode><value type="integer">0</value></metric><metric><enabled type="bool">False</enabled><lastcomputedtime type="integer">0</lastcomputedtime><peaktime type="integer">0</peaktime><poolid type="string"></poolid><resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid><starttime type="integer">0</starttime><typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode><value type="integer">0</value></metric><metric><enabled type="bool">False</enabled><lastcomputedtime type="integer">0</lastcomputedtime><peaktime type="integer">0</peaktime><poolid type="string"></poolid><resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid><starttime type="integer">0</starttime><typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode><value type="integer">0</value></metric></deviceinstance><guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid></devicetype><devicetype><deviceinstance><guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid><metric><enabled type="bool">False</enabled><lastcomputedtime type="integer">0</lastcomputedtime><peaktime type="integer">0</peaktime><poolid type="string"></poolid><resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid><starttime type="integer">0</starttime><typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode><value type="integer">0</value></metric></deviceinstance><guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid></devicetype></metrics><owner><sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid></owner><power><host_shutdown><action type="integer">1</action></host_shutdown><host_startup><action type="integer">1</action></host_startup></power><snapshots><list><size type="integer">0</size></list></snapshots><unexpected_termination><action type="integer">1</action></unexpected_termination><vhd_path_acled type="bool">True</vhd_path_acled></global_settings><manifest><size type="integer">11</size><vdev001><device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device><flags type="integer">1</flags><instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance><name type="string">Microsoft Synthetic Mouse</name></vdev001><vdev002><device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device><flags type="integer">1</flags><instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance><name type="string">Microsoft Synthetic Keyboard</name></vdev002><vdev003><device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device><flags type="integer">1</flags><instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance><name type="string">Microsoft Synthetic Video</name></vdev003><vdev004><device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device><flags type="integer">1</flags><instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance><name type="string">Microsoft Heartbeat Component</name></vdev004><vdev005><device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device><flags type="integer">1</flags><instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance><name type="string">Microsoft Key-Value Pair Exchange Component</name></vdev005><vdev006><device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device><flags type="integer">1</flags><instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance><name type="string">Microsoft Shutdown Component</name></vdev006><vdev007><device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device><flags type="integer">1</flags><instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance><name type="string">Microsoft Time Synchronization Component</name></vdev007><vdev008><device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device><flags type="integer">1</flags><instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance><name type="string">Microsoft VSS Component</name></vdev008><vdev009><device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device><flags type="integer">1</flags><instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance><name type="string">Microsoft RDV Component</name></vdev009><vdev010><device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device><flags type="integer">1</flags><instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance><name type="string">Synthetic Ethernet Port</name></vdev010><vdev011><device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device><flags type="integer">1</flags><instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance><name type="string">Synthetic SCSI Controller</name></vdev011><version type="integer">260</version></manifest><properties><global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id><highly_available type="bool">False</highly_available><last_powered_off_time type="integer">130493284127496105</last_powered_off_time><last_powered_on_time type="integer">130493284065876653</last_powered_on_time><last_state_change_time type="integer">130493284127496105</last_state_change_time><name type="string">LegacyTS</name><notes type="string"></notes><type_id type="string">Virtual Machines</type_id><version type="integer">1024</version></properties><settings><global><logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id></global><memory><bank><dynamic_memory_enabled type="bool">True</dynamic_memory_enabled><limit type="integer">1048576</limit><priority type="integer">5000</priority><reservation type="integer">512</reservation><size type="integer">4096</size><target_memory_buffer type="integer">20</target_memory_buffer></bank><vnuma><max_size_per_node type="integer">14770</max_size_per_node></vnuma></memory><processors><count type="integer">1</count><features><limit type="bool">False</limit></features><limit type="integer">100000</limit><limit_cpuid type="bool">False</limit_cpuid><reservation type="integer">0</reservation><vnuma><count_per_node><max type="integer">4</max></count_per_node><node_per_socket><max type="integer">1</max></node_per_socket></vnuma><weight type="integer">100</weight></processors><stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown><vnuma><enabled type="bool">False</enabled></vnuma></settings></configuration>

If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation. 

As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?

Thanks,

D

I am building a Windows Server 2012 R2 Hyper-V Host that will house (2) Virtual Machines running Windows Server 2012 R2 for a SMB.  The server has a LSI PIKE 2208 RAID Controller and (8) 600GB 15K SAS drives that I plan on placing in a RAID 10 array providing my 2.4TB of storage.  The software vendor has provided me the following specifications to guide my decisions in setting up storage:

SQL Server (15K Drives): 

RAID Channel 1 (320GB x 2) - RAID 1 - (C) OS + SQL Server App - (D) SQL Server Log Files
RAID Channel 2 (500GB x 3) - RAID 5 - (E) SQL Server Data Files

RDS Server (10K Drives):

RAID Channel 1 (500GB x 2) - RAID 1 - (C) OS + Application Files

I know I should use the RAID controller to setup a smallish Virtual Drive for the Hyper-V host.  This will allow me to keep the host operating system on a drive separate from the VMs VHDXs and configuration files.  The next part is where I am at an impass.

I don't know if I should create separate Virtual Drives using the RAID controller for the different VMs, then place the respective VHDXs and configuration files on those drives <OR> create one big Virtual Drive for all the VMs and just put all the VHDXs and configuration files on that drive.  Here are the two configurations I am thinking of:

Configuration 1:

• RAID Controller Virtual Drive 1
• - 150GB (Windows Server 2012 R2 Hyper-V Host Operating System)
• RAID Controller Virtual Drive 2 (VM1 - SQL Server)
• - 320GB (Houses the VHDX and CF for (C) OS + SQL Server App - (D) SQL Server Log Files)
• RAID Controller Virtual Drive 3 (VM1 - SQL Server)
• - 1TB (Houses the VHDX for (E) SQL Server Data Files)
• RAID Controller Virtual Drive 4 (VM2 - RDS Server)
• - 500GB (Houses the VHDX and CF for (C) OS + Application Files)

Configuration 2:

• RAID Controller Virtual Drive 1
• - 150GB (Windows Server 2012 R2 Hyper-V Host Operating System)
• RAID Controller Virtual Drive 2
• - 2TB (Houses all of the VHDXs and CF for all of the VMs)

Is there any benefit to separating the Virtual Drives at the controller level or should I use Configuration 2 and let the host work out out optimizing the performance?

Thank you all very much for your input.  I sincerely appreciate it!

We have continual problems with losing network connectivity to the virtual machines hosted on a Hyper-V host (the host is running Hyper-V Server 2012 R2), it goes down 2 – 3 times per week.

Situation:

• All 3 Windows 2008 R2 virtual machines on the host lose connectivity to the outside world at the same random time (they are the only 3 on the host).
• When this occurs the host can still ping the 3 virtual machines and the host is reachable.
• When this occurs the 3 virtual machines can ping the host and each other, but nothing else outside of the host (request timed out followed by destination host unreachable)
• Nothing in the hardware or Windows event logs on the host indicates there is a problem. No indications of issues in the VM event logs either.
• Restarting the virtual machines does not fix the issue
• Brand new HP hardware, Broadcom nic drivers were upated early on
• VMQ is disabled on the VM's
• We are not using nic teaming or clustering
• Restarting the host temporarily resolves the problem (during the restart the vms are just placed in a saved state).
• The host is running Hyper-V Server 2012 R2
• The switch ports that the 2 network cables are plugged into (1 for RDP access to host and 1 for the VM traffic) show no errors on the switch.
• This sounds like an issue with the Virtual switch but I can't find anything in the logs that gives me a hint.

Hi,

Hyper-V single node with Windows 2012 R2 Datacenter - the VM had its Integrated Services update and rebooted properly. After that, Windows 2008 start and shows BSOD as listed below - safe mode doesn't work. Any tips?

Vinicius Deschamps

Hi,

Since we installed the new version of Data Protection Manager 2012 R2, we get issue messages while backing up Windows Server 2008 R2 or 2012 R2 virtual machines. 

At every backups we will find the followings in Event Viewer:

Log Name:      System
Source:        partmgr
Date:          18.2.2014 21:40:34
Event ID:      58
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server01.domain.local
Description:
The disk signature of disk 2 is equal to the disk signature of disk 0.

This last line is repeated for each disk.

Sometime this line is preceded by the following:

Log Name:      System
Source:        VDS Basic Provider
Date:          20.1.2014 20:08:58
Event ID:      1
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server01.domain.local
Description:
Unexpected failure. Error code: D@01010004

The registry is growing up with remaining entries under:

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

May someone help me? Thank you

Regards,

Samuel

Edit

I am quite sure now this is a bug. The ARP proxying does not work for VMs if the packet-recipient is not directly attached to the external vswitch that is bridged to the wifi-nic!

/Edit

I am running a test lab on my Windows 8.1 using Hyper-V.

My problem is, that the virtual LAN has limited connectivity, when the external vSwitch is configured to use the wifi interface, instead of the cable interface. I am troubleshooting this issue for hours now and I reached the point where I believe the Network Bridge, that is created by the Hyper-V Virtual Switch Manager, is not forwarding packets.

Pings are delivered from 192.168.178.2 to 192.168.178.1 and back again.

Pings from 192.168.0.10 are delivered to 192.168.178.1, and the reply does reach the wifi interface …

== Trace on the WiFi interface ==
Here you see a log of the trace on the WiFi interface of the Hyper-V-Host,
while 192.168.0.10 is pinging 192.168.178.1
No  Time        Source          Destination     HW Source           HW Destination      Protocol    Info
3	0.003340000	192.168.0.10	192.168.178.1	24:65:11:cc:c0:9e	24:65:11:2b:35:e4	ICMP	    Echo (ping) request  id=0x0001, seq=44/11264, ttl=127 (reply in 4)
4	0.006094000	192.168.178.1	192.168.0.10	24:65:11:2b:35:e4	24:65:11:cc:c0:9e	ICMP	    Echo (ping) reply    id=0x0001, seq=44/11264, ttl=64 (request in 3)
5	0.006152000	192.168.178.1	192.168.0.10	24:65:11:cc:c0:9e	24:65:11:2b:35:e4	ICMP	    Echo (ping) reply    id=0x0001, seq=44/11264, ttl=64

… but is never forwarded to the Network Bridge interface.

== Trace on the Network Bridge interface ==
Here you see a log of the trace on the Network Bridge interface of the Hyper-V-Host,
while the Hyper-V-Host is pinging 192.168.178.1 (#1)
and the 192.168.178.2 is pinging 192.168.178.1 (#7)
-> Note: The ping-reply from 192.168.178.1 to 192.168.0.10 is missing!
1	0.000000000	192.168.178.1	192.168.178.21	24:65:11:2b:35:e4	24:65:11:cc:c0:9e	ICMP	    Echo (ping) reply    id=0x0001, seq=9/2304, ttl=64
7	7.852500000	192.168.178.1	192.168.178.2	24:65:11:2b:35:e4	00:15:5d:b2:21:18	ICMP	    Echo (ping) reply    id=0x0001, seq=439/46849, ttl

How do I solve this problem?

Hello there.

I'm starting to deploy a virtualization environment based on a server core installation of windows server 2012 R2.

But, I just faced the following doubt: Is there some way to install an OS on a VM at that environment without use the Remote Hyper-V Manager?

It's important to say that I've already installed the Hyper-V role and created the VM on the quoted server.

I thanks in advance.

Lucas Gustavo.

Lucas Gustavo

I am on a physical box with Windows Server 2012 R2. All updates have been applied and the Hyper-V role is installed.

My motherboard has four network interface ports. All of which get valid IP addresses from the DHCP server (and have Internet access). When trying to create a virtual switch on one of these NIC's, it doesn't work. Take a look at the screenshots below:

Hi,

I've configured hyper-v replica on both of my win 2012 servers. Initial replication has started successfully and the replica vm is created correctly on the replica server. Now I'm trying to simulate an unplanned failover. I turned off the production vm and enabled "failover" under replica VM. Now i'm able to select a recovery point and the vm is start up now on the replica server. Now i bring the production vm  up now. Then i tried to restore the  latest changes on "replica vm" by using "reverse replication" on replica vm. But i'm getting  error, please see the attached screen-shot to see the error.

Server is reachable on both sides. Port 443 is opened and telnet to 443 is working.

--

Regards,

Jaffer Amin

Jaf