Good day!
Can you help me. What's the best way to rollback from 2012R2 Hyper-V Cluster back to to 2008 R2.
We plan to migrate from 2008R2 to 2012R2 Hyper-V cluster with FC Storage.
We have very nice instruction about migration here.
But we have no info how to rollback if smth will going wrong.
Thank's a lot.
Hi
I've just hit a problem configuring hyper-V server 2012 using powershell and I'm hoping someone can help
Scenario:
The vnic is created with a mac address of 00-15-5d-00-00-00 on every server.
assigning a static address solves the immediate problem but is not an acceptable solution.
Any ideas ?
Hi all,
What I am looking for I believe is quite simple, but I have had no experience configuring anything other than basic networking, so would need some help.
In a nutshell we have some Hyper-V servers configured in a cluster/cloud - and I would like the VM's created by VMM in the cluster/cloud to have automatically assigned IP's on a subnet that does not affect production (in my case, 10.101.50.0/24 would work) whilst maintaining access to our external network. Our currently configuration is detailed below:
A cluster has been created containing 4 Hyper-V servers. The Hyper-V servers have manual IPs in 10.101.3.0/24.
The 4 Hyper-V servers are connected to a physical Switch which in turns connects to the company network & gives external access.
On each Hyper-V server, we have a virtual switch called, "VirtualSwitch", the VM's have 1 adapter each connected to this switch (with manual IP's currently also in the 10.101.3.0/24 range)
As you can see it's a really basic setup, but if someone could help me configure this, it would be great. I probably haven't given enough information here as I don't know what else is needed. I will be happy to provide more information if requested! Thanks in advance.
Hi,
I am trying to Export VM's on WS2012 R2 Hyper-V Host.
If VM is configured without Virtual Fibre Channel, the Powershell Command "Export-VM" works fine, but fails with VM's where vFC is present.
The command: Export-VM -Name "Test-VM" -Path c:\temp
Outputs the error:
----------
Export-VM : "Test-VM": Fehler beim Export (ID des virtuellen Computers 987F1E1B-8C68-4BBA-97B7-17FC5D044B2B).
Für "Test-VM" konnte kein Prüfpunkt erstellt werden, da mindestens ein synthetischer Fibre Channel-Controller
angeschlossen ist. (ID des virtuellen Computers: 987F1E1B-8C68-4BBA-97B7-17FC5D044B2B)
Der Vorgang wird nicht unterstützt.
In Zeile:1 Zeichen:1
+ Export-VM -Name "Test-VM" -Path c:\temp
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotImplemented: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Export-VM], VirtualizationO
perationFailedException
+ FullyQualifiedErrorId : NotSupported,Microsoft.HyperV.PowerShell.Commands.ExportVMCommand
---------
Is there another way to get a vFC featured VM exported / copied (Online)?
Regards,
Markus
Hello all, I will be setting up a Datacenter 2012 cluster and be adding Hyper-V services to it.
My question is, can I install Datacenter on a single node, install Hyper-V role, migrate some virtual machines to it, use it for a while, and still be able to add another host so that I can setup the server cluster and the Hyper-V cluster?
The reason that I ask is because I am migrating two servers that have separate stand alone hyper-v environments. I have a single 'extra' server that I can beef up and use for the first half of the cluster, but nowhere to move the VM's until I get the SAN up and running.
Thanks!
Steve W. MCSA,CCNA,MCP,A+,SEC+,CIW
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&VEN_IBM_SATA&PROD_DEVICE_81Y3681\4&1864BF9E&0&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 have a WIn2k12 server with Hyper-V running. While removing the vSwitch configured in Hyper-V, the server got rebooted. In the event logs below mentioned error was notices.
he computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000024, 0x00000000000000f2, 0x0000000000000001, 0xfffffa800b9ba6c0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072314-20248-01.
The Windows has generated a MEMORY.dump which is ~570MB in size. Is it possible to analyze the MEMORY.dump and find the cause for a server reboot.
Can you please someone help me to narrow down the root cause of this issue and how to avoid this issue in the future.
I've found a few postings on Event ID 157 for Windows 2012 R2, but no answers
We've upgraded from Server 2012 to 2012 R2. Hyper-V Role. Event ID 157 occurs when Windows Backup is running to backup Hyper-V machines. People have reported the same issue I am having. They have ID 157 occurring only during the Windows Backup process or if they use VSS Snapshots to backup hyper-v virtual machines.
I've found event ID 157 was designed for 2012 R2 Storage Groups when a disk is removed, so it seems like it is a bug showing up during Windows Backup.
One time (out of about 10 now - once each day) that this event was logged, a software RESET was sent to the LSI Mega Raid controller for half of the array and consistency checks were immediately done. I hope this does not happen again.
Everything worked fine before we moved from 2012 to 2012 R2. I've done a clean install and it still happens.
I've looked through the event logs on the virtual machines and we have one Windows 2008 Server running SQL 2008 R2 and it chokes through the entire backup process with hundreds of errors, starting with the SQL VSS Writer receiving a command that it does not understand. From then onward it says tables and data are corrupt, but the normal SQL maintenance job we have running for SQL Server backs up the databases and performs consistenacy checks without issues.
I've just remove the SQL Server from the Windows Backup and will see how it goes tonight.
In case this is related to the SQL Server, here's the error that is 1st logged as soon as the Windows Backup on the host begins:
Event ID 513, CAPI2, Error, Cruptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details: AddCoreCsiFiles: BeginFileEnumeratrion() failed.
System Error: Access is denied.
After that it freezes the databases, gives dozens of errors for each table, and then restores each table to normal operation.
The Guest SQL server appears to always be the 1st VM to get backed up, so I doubt this has anything to do with it, but thought I should provide as many details as possible, especially when everyone else has discovered it is VSS related and this guest is reporting VSS errors.
What do you think?
thanks
John
P.S. there are no hard drive errors, so running check disk will not help.
Hi
We have a cluster running on Windows Server 2012 R2 with Hyper-V feature.
One VM that has Windows 2012 R2 Standard OS installed (generation 2) was corrupted via restart.
VM has 3 virtual disks (VHDX) - first for system (dynamic size), second for SQL_data (fixed size) , third for SQL_logs (fixed size)
Yesterday, I restarted VM and VM didn't come up, I got error
- 'Boot Failed. Windows Boot Manager'
- 'Boot Failed. EFI SCSI Device'
Looked all three VHDX we noticed that the first one (system) was corrupted - partition and MBR are gone inside VHDX.
Second and third one are OK, we can mount them and access all data on it.
It looks like on first VHDX (system with SQL 2014 installed) partition was corrupted, so we can't do repair because it's says unknown partition.
There were no updates applied to VM, corrupted partition is 40GB size (dynamical) with 18GB of data used.
This is first generation 2 VM that we have, all others are generation 1 without any problems.
Can anyone please explain us, how can this happened, since we did nothing inside VM, also cluster reports no errors, checking VHDX looks fine, just partition inside got corrupted.
We like to find out what happened, before we deploy more Win2012 R2 VM (gen2) in production envirionment.
Thank you in advance
Regards
Mike
Hi all, I have done some reading up and have understand the difference between Hyper-V Snapshots and VSS Snapshots..
What I do need some assistance is on a basic solution for a small Hyper-V environment of 6 servers with just important services (basically 8-10 hours recovery).
1) All the Hyper-V servers already have replication and under the VSS option "Only the latest recovery point" is selected. I was exploring if I should change to Additional recovery points which would take up more space. Does "Additional recovery points" gives me more backup volume snapshots to choose to recover from ?
2) I understand that to backup specific VM, all the associated volume must be backup. Does it means under the Replication option all volume are covered ?
3) There's also Windows Server Backup which gives an extra edge over volume VSS as it can restore files while VSS only can recover the whole disk volume. So on a file server, does the Windows Server Backup be a better option than VSS ?
Dear Microsoft,
We have install an PFX certificate with private key, but in Hyper-V we cannot select the certificate.
the certificate is visibel in the screen......and in certificates. error: Install a valid certificate and try again. What can be the problem?
When I migration the virtual machine with synthetic FC HBA in windows server 2012 R2 Cluster,it fails
but I do it in the style of quick migraton ,it secceed!
The error event here
Live migration of 'Virtual Machine PTSCSQL01' failed.
Virtual machine migration operation for 'PTSCSQL01' failed at migration destination 'PTCLS0106'. (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
'PTSCSQL01' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
'PTSCSQL01' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
My virtual machine's synthetic FC HBA setting here
做微软的先行者，享受用户体验
I have this scenario:
Server 1 (Primary Hyper-V)
Drive 1 (Current VHD storage)
Drive 2 (New VHD storage)
Server 2 (Replica Hyper-V)
I am moving a couple of VM from drive 1 to 2 using live storage migration. These VM have active replication to Server 2. The move seemed to go fine and replication resumed properly once the move was finished. The strange thing is the primary VHD seem to still be on Drive 1. I thought that the final step of the live storage migration would be to delete the old VHD? Once I verify the VM are using Drive 2 I assume I can just delete the files on Drive 1 right?
Hi..
we use a two node hyper-v cluster.
On each node running 5 vm that shared the 64GB system memory.
The vms are configured to use dynamic memory. The sum of the startup (min) memory of the 10 vms are currently 50 GB.
So now our problem:
If we try to drain roles on node A for maintenance purpose two vms are still on node A because they wasted currently each 25GB memory and so on node B is not enough free memory to host this vms.That soundslogical
But as all vms configured to use dynamic memory they should shrink their memory to get enough space for all vms? If we shutdown all vms, move it to one node, then everything works fine.
Is it by design that live migration do not trigger the vm to shrink their memory?
Best regards, Alexander Zirbes
Hi, we have a Hyper V 2012 R2 Core cluster of three servers.. We have separate NICS for iSCSI/MNG/LAN/Cluster traffic etc... All is working really well until we create a vSwitch of teamed NICs. As soon as we do that the A record for the Host is updated with the DHCP assigned IP. We have tried using nvspbind to force the ms_tcpip protocol for the MNG NIC to the top of the binding order, but we still have our A records being overwritten by the DHCP enabled Team...
It isnt easy to see the config of these 'adaptors' with the Core version, and I have also searched to see if I can turn of DNS registration, but the articles I have found are not applicable because the Hyper V Team/Switch cant be accessed in the same way - if you know what I mean...
I am sure I have left out a few critical points which you may need to help me answer this issue, so please feel free to come back with further questions and options.
Thanks very much for any help.
Hello all
Im running Windows 8.1 Pro. It has Hyper-V on it, I use it and ive been able to install alot of os on it vista, xp, linux, etc.
I got an educational copy of windows server 2008 r2 with cd key. From MS dream spark
when i try to install it on Hyper-v it always finishes the installation process and when its about to restart for the first time it gives an error of not all components where installed pls restart computer and restart installation. I do this and it just goes on a vicious cycle of restarts and always erroring out.
ive tried re downloading the .img file from Microsoft today and when i attempt to install it again i get he same error
My pc specs are 8 gigs of ram 1600 mhz and a I5 4670k plus i have plenty of space on ssd/hdd
i set the virtual os to have 2 GB of ram and 127 GB of hd space when im configuring it in hyper-v manager
can some one help me? or has anyone had a similar issue?
Hello there,
I recently went through the 410, 411, and 412 classes, have passed the 410 exam, and am now looking forward to reproducing the lab environment I had in the MS Certified training boot camp I attended. With the class behind me, I have the SkillPipe books, but not the Hyper-V environment to work through the labs associated with these courses.
The SkillPipe books give some hints as to how things are configured, and I have some good notes on the lab configuration which has taken me a fair way to being able to reproduce the Hyper-V VM configuration, but there are certainly gaps.
How does one go about properly building\configuring the environment used in these labs so that the labs may be practiced over and over again ? Are there no PowerShell scripts to accomplish this ? Is MS unwilling to share these lab environments, or is it just that it's a romp through the labyrinth to get to the treasure ?
My last serious study with MS networking was my MCSE training and testing in NT4.0. Now that MS has finally got REAL product, are they still going to dangle the carrot just out reach like this ? I find it hard to believe, especially with Technet Virtual Labs.
Am I missing the obvious ? or is it just not there ?
Thanks,
Glennzone
Hi,
I backup all replica VM using Symantec backup , Once the backup start , The replication was suspended and set in failed state
as the below alert the status of replica VM is"Backing up..."
Hyper-V failed to replicate changes for virtual machine 'VMOOWEB' (Virtual Machine ID 24FB4E40-654D-4C8C-99EF-118033903B03). Hyper-V will retry replication after 5 minute(s).
'VMOOWEB' failed to perform the operation. The operation cannot be performed for this virtual machine while it is in its current state. (Virtual machine ID 24FB4E40-654D-4C8C-99EF-118033903B03)
Do you have any idea how to recover it ?
Ramy
