VMware switch – migration to Hyper-V

I wood like to migrate VM hosted on ESX servers. Problem is, that when i choose VM, and try to migrate, it is saying, that it network does not exist on destination host, but i can not create network with the same name on destination
host ?
How to create network in VMM so that I can do migration without using other tools. I have SCVMM 2012 R2.

Hi Sir,
One method to convert a VMware ESX virtual machine to a Microsoft Hyper-V virtual machine is to migrate the virtual machine from the server that is running ESX to a server that is running Hyper-V. Before you migrate a virtual machine from a server that
is running ESX to a server that is running Hyper-V, ensure that the source server that is running ESX has the OK status in VMM, and that the virtual machine is turned off. If the host has OK (Limited) status, additional security configuration is required to
enable file transfers to the server that is running Hyper-V. You must provide credentials for the server that is running ESX; in addition, if you manage your VMware infrastructure in secure mode, a certificate and public key might be required.
Alternatively, you can perform a virtual-to-virtual (V2V) conversion on the virtual machine files to convert a VMware virtual machine to a Hyper-V virtual machine.
You can try to create new standard switch for the hyper-v host .
Open the properties of the hyper-v host which you want to migrate to then click virtual switches tab , at the right pane click "new virtual switch" to add standard switch :
For V2V please refer to following article :
https://technet.microsoft.com/en-us/library/gg610672.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Similar Messages

How to migrate the Hyp financial report 11 from dev to test on aix

Hi All,
I need to migrate 3 Hyp Fin Reports 11.1.2.2 from dev to UAT. I am new to this. Can any one tell me the steps or the link to the documentation??
Thanks !!!!!
Edited by: 940841 on Mar 29, 2013 9:16 PM

Hi Celvin,
Thanks for the reply. Could you please let me know how to perform the LCM migration for HFR.
I am having some issues with my HFR server and so I cannot open the reports. So I am thinking if I can use LCM and export and migrate the reports to another server.
The steps I am performing to do this:
Login to HSS > Application group> Reporting and Analysis> Repository objects> report folder name> select reports> Hit on Export
Now in the exported folder I see three things:
RnA-Reporting and Analysis (Its a folder)
Export.xml
Import.xml
Now under RnA-Reporting and Analysis folder I see sub folders
resource\Repository Objects\Under this folder, I see for every report there is one .xml file and 5 other files for the same report.
Can anyone tell me how to import these reports back into the new environment?
Thanks,

Trying to migrate to Hyper-V

Hi I am trying to find the best way to migrate from ESXi to Hyper-V with Server 2003 DC with two hard drives. I know I should not snapshot the DC so I guess what's the best way to do this. Here is the one catch I only have on physical host.
Should I uninstall the VMware tools, shutdown all my servers, export the vm to an OVF, uninstall ESXI, install HyperV, convert the OVF to use with HyperV, import the machine and than boot up?

Hi jmiller1981,
"What if i place a Hyper-V VM in Esxi, install a new DC on that machine, transfer the roles and retire the old DC, shutdown the DC and then export it to my local machine. Next I uninstall Esxi from the box than install Hyper-V than import the DC"
Regarding "retire the old DC" , I would suggest you refer to following link to remove the old one after FSMO transfer：
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Vmware esx 4 to hyper-v 2012 e2

Hi,
We need to do a convert from Vmware esx 4.0 which is managed by vsphere 4.1 to hyper 2012 R2 Cluster
I did look at SCVMM but 2012 does not support hyper-v 2012 R2 I believe
SCVMM 2012 sp1 Does not support vmware esx 4.0 (http://technet.microsoft.com/en-gb/library/gg697603.aspx)
What are the options available here as we just need to do a virtual to virtual migration but google did not help.

Hi,
The MVMC Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1, and VMware vSphere 4.1 hosts Hyper-V virtual machines.
You can get the detail information at the download website(you can expand the Details).
Microsoft Virtual Machine Converter 2.0
http://www.microsoft.com/en-us/download/details.aspx?id=42497
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Event Logs of VMs Migration in Hyper-V Cluster

Hello All,
We're running Failover Cluster of Win Server 2012 R2 Hyper-V hosts. If any host gets down unexpectedly (due to any reason power/bugcheck/hardware failure or what so ever), then the VMs on that host, of course, get migrated (either quick or live) to some
other host within the cluster.
I want to have logs/events of this VMs migration. I want to know that which of the VMs were residing on that host at that time of failure. Of course, we can't have this info in the Cluster events is Failover Cluster Manager. I am unable to find this info
anywhere. I have searched in Event Viewer --> Administrative Roles --> Hyper-V. I have searched a lot in the SCVMM, but no success. We're using SCVMM 2012 R2 with UR5.
Please help me in finding the exact location of these logs/events. I would also like to know that if the VM was quick migrated or live migrated, and to which host the VM got migrated.
I'd be highly grateful.
Thanks in anticipation.
Regards,
Hasan

You have posted this same question in two different forums. The answer on where to look is posted in the other forum.
https://social.technet.microsoft.com/Forums/en-US/7f0da2a8-debc-4dd8-9214-72ed46e3c76b/event-logs-of-vms-migration-in-failover-cluster-of-hyperv-hosts?forum=winserverhyperv
In the future, forum etiquette requests that you do not cross-post.
Again, when a host fails, there is no migration, quick or live, to another node of the cluster. There is a restart. When a host fails, the VMs on that host also fail. The cluster detects the failure and the resources (VMs) that had
been running on the failed node are restarted on another node. You will see different events entered into the event log for a resource start than for a quick/live migration.
The easiest way to see this is to do it. Open up the event viewer on a host to which you plan to migrate a VM. Perform a quick/live migration. Refresh the event viewer and note the events that were logged.
. : | : . : | : . tim

VM Migration from Hyper-V 2008 R2 to 2012 successful but leave duplicate source VM with "Incomplete VM Configuration"

We are in the process of moving VMs from our legacy 2008R2 Hyper-V cluster to our new Hyper-V 2012 cluster using VMM 2012 SP1 CU3. Most VM migrations go just as expected and are completely successful. I have had a couple of VMs however that appear to successfully
migrate but leave behind the VM on the source 2008R2 in the VMM configuration with a status of "Incomplete VM Configuration." Using the VMM shell, I get the following:
Get-SCVirtualMachine | where { $_.Name -EQ "<VM>"} | fl name, status, VMId
Name : <VM>
Status : IncompleteVMConfig
VMId : <DuplicateID>
Name : <VM>
Status : Running
VMId : <DuplicateID>
If you use failover cluster manager on both the 2008R2 and the 2012 clusters the VM shows it is gone from the 2008R2 cluster and just fine on the 2012 cluster. I have tried everything I can think on short of removing the cluster from VMM to try
and resolve this issue and I really don't want to have to do this everytime I run into this issue. I've tried just right-clicking the VM in the VMM console and selecting "Delete" which does remove it but then it pops back in once the VMs refresh
on the 2008R2 nodes. I have tried to force the removal using "Get-SCVirtualMachine | where { $_.Name -EQ "<VM>" -and $_.Status -EQ "IncompleteVMConfig"} | Remove-SCVirtualMachine -Force" and it again pops right
back into the console. It seems to me like during the migration, SCVMM isn't cleaning up after itself and updating its database to reflect where the VM now resides. How can I permanently remove this VM that is leftover when migration between clusters without
having to remove and read the cluster to VMM?

Since nobody replied, I opened a case with MS.
The resolution to this issue is to use Hyper-V manager to connect to the node you migrated the VM from. Here you will see a VM that has only a GUID for a name and is in an incomplete state. Right click this leftover VM and delete it using Hyper-V manager.
Then go back into SCVMM and refresh both your source Windows 2008R2 and then your target 2012 clusters. This will reconcile the SCVMM database and the duplicate VM. According to MS, there is some process that didn't complete deleting this VM as part of the
migration and performing these steps cleanly resolves the issue.

SAN Storage Migration with Hyper-V 2008 R2 CSV

Dears
Our customer has configured 2 node Hyper-V Cluster with CSV   connected to an Old SAN Storage The Host Operating System is Windows 2008 R2.
We are planning to migrate the data from the old storage to the new storage. ( Both Storage boxes are connected via Fiber)
With regard to the Migration can we do the below if so please provide some guidelines related to the Hyper-V queries.
(We are trying to avoid the Storage based migration)
- Connect the new storage   to the servers
- Create the LUN same as in the old storage and assign it to the servers
- Create a new CSV and point it to the new luns in the Failover Cluster Manager
- Use the export/import function to move the VM's from the new storage to the old storage
- Once all the vm's are moved create a new LUN for the quorum and re-configure the cluster to use the new quorum
Are the above steps will perform a error-free migration if so
- Can we delete the old CSV and dismount the old storage at this stage.
Also these VM's (Exchange and SQL) has seperate LUN's assigned for the Exchange and SQL data , Does these data will be exported when we use the export/import feature of the Hyper-V to migrate the virtual machine
Your Valuable response in this regard is highly appreciated.
Regards
Muralee

Dear All
Thanks for your valuable reply.
And I was able to successfully migrate the cluster and below are the steps i performed
* Initialized the SAN storage and assigned the LUN to both servers.
* Logged in to the server which is the current owner of the csv's and disks
* Initialized the disks as GPT and formatted the LUN without a drive letter.
* Added to the Hyper-V Cluster as disks
* Added to the CSV
* Exported the VM to the new disks
* Deleted the VM from Hyper-V console(Which will not delete any VM files)
* Imported the VM (chosed the default settings in the wizard)
* Added the VM as a service Failover Cluster Manager.
* After completely moving the VM's created a new LUN for the quorrum and changed the quorrum      configuration to the new disk.
* Removed the Old Storage and restarted the cluster checked for the VM's functionality everything was fine.
NOTE1 :- I faced a difficulty in multipathing software as he was using the EMC Powerpath and I had to remove it and enable Widows MPIO .
Anybody who are facing a similar scenario please send a note I would be glad to share the experience.
NOTE2 :- I tried all the SAN migration options from the storage Vendor but this method was able to do the migration in a much easier and confident manner.
Regards

ESX/VMWare Switch Port Configuration

Does anyone know how to configure a 3560 switch port that is connecting to an ESX host with multiple VM's??

Hi Jason,
Most of the time people will configure the port as a trunk to the ESX host. So on the 3560 you can just do:
switchport trunk encap dot1q
switchport mode trunk
This will allow your VMs to be in different vlans if you would like.
Chad Peterson
CCIE 23213
Network Consulting Engineer
.:|:.:|:.
CISCO
PDI Data Center
http://www.cisco.com/go/pdihelpdesk

Enabling VM Guest NLB w/Multicast IGMP on 2012 Hyper-V host w/ converged SCVMM fabric switch

What a mouthful.
As short as possible:
WHAT I'M ATTEMPTING:
I'm trying to build a new NLB cluster for a 2008 R2 SP1 Remote Desktop Services farm. And I'm trying to do it the right way, with multicast igmp, not unicast.
The two guest VMs with NLB install converge fine. VIP gets this:
IP: 192.168.100.157
MAC: 01-00-5e-7f-64-9d
NLB NIC is on the same VLAN & "Converged switch" in VMM as our mgmt/server traffic (That is to say it's on production VLAN, not on a separate vlan)
PROBLEM:
Can't ping 100.157. From VM guest itself, from host, or from Cisco 6509 switch.
Cisco show mac address lookup does not see that MAC anywhere
show ip igmp groups shows not igmp traffic at all. Clearing counters show sno multicast increment.
FURTHERMORE:
Host is setup thusly:
- Dell R810
- 8x1GbE Broadcom 5709c in a Server 2012 LACP/HASH team built via VMM powershell cmdlets
- On the physical switch side, those 8 nics are in a Cisco port-channel, trunked, all VLANs allowed
- Host has no "physical" nics per se, as in a 2008 R2 hyper-v host. Instead Host has these:
Set-VMNetworkAdapter -ManagementOS -Name "Live Migrate" -MinimumBandwidthWeight 35
Set-VMNetworkAdapter -ManagementOS -Name "MGMT" -MinimumBandwidthWeight 25
Set-VMNetworkAdapter -ManagementOS -Name "CSV" -MinimumBandwidthWeight 40
Set-VMNetworkAdapter -ManagementOS -Name "iSCSI #1" -MinimumBandwidthWeight 0
Set-VMNetworkAdapter -ManagementOS -Name "iSCSI #2" -MinimumBandwidthWeight 0
Set-VMNetworkAdapter -ManagementOS -Name "Aux" -MinimumBandwidthWeight 0
Get-VMSwitch outputs this on the converged v-switch:
ComputerName : My-host
Name : My awesome switch
Id : e2377ce3-12b4-4243-9f51-e14a21f91844
Notes :
SwitchType : External
AllowManagementOS : True
NetAdapterInterfaceDescription : Microsoft Network Adapter Multiplexor
Driver
AvailableVMQueues : 0
NumberVmqAllocated : 0
IovEnabled : False
IovVirtualFunctionCount : 0
IovVirtualFunctionsInUse : 0
IovQueuePairCount : 0
IovQueuePairsInUse : 0
AvailableIPSecSA : 0
NumberIPSecSAAllocated : 0
BandwidthPercentage : 0
BandwidthReservationMode : Weight
DefaultFlowMinimumBandwidthAbsolute : 0
DefaultFlowMinimumBandwidthWeight : 1
Extensions : {Microsoft NDIS Capture, Microsoft
Windows Filtering Platform, Microsoft
VMM DHCPv4 Server Switch Extension}
IovSupport : False
IovSupportReasons : {This network adapter does not support
SR-IOV.}
IsDeleted : False
Question:
Aside from a few of my favorite MS MVPs (shout out to
WorkingHardInIt for having this same question), I can't find much documentation on employing 2008 R2 NLB on guest VM within a fabric-oriented, VMM-built 2012 Hyper-Visor converged switch (no network virtualization...yet).
Yes I know all about VMM NLB but 1) I'm trying to wedge NLB in after building these VMs without a service template (NLB is the audible, essentially) and 2) MS NLB is configured in providers & I've created requisite VIP templates.
Even so, I ought to be able to create an NLB cluster without VMM's assistance in this scenario correct? Suboptimal, I know but possible, yes? Essentially I've put to synthetic NICs on each VM, set IPs manually, and assigned them to the same vlan. I can ping
each synthetic NIC, but not the cluster IP.
And yes: these particular vNICs have Mac Address Spoofing enabled.
Cisco:
I have a TAC case open with Cisco, but they can't quite figure it out either. IGMP Snooping enabled across the switch. And they insist that the old static arp entry to resolve this problem is no longer necessary, that Microsoft now complies with relevant
RFCs
Possible SOlution:
Only thing I can think of is flipping MulticastForwarding param below from disabled to enabled. Anybody ever tried it on a converged virtual switch on the Hyper visor? Is my virtual converged switch protecting
me from multicast igmp packets?
PS C:\utilities> Get-NetIPv4Protocol
DefaultHopLimit : 128
NeighborCacheLimit(Entries) : 1024
RouteCacheLimit(Entries) : 128
ReassemblyLimit(Bytes) : 1560173184
IcmpRedirects : Enabled
SourceRoutingBehavior : DontForward
DhcpMediaSense : Enabled
MediaSenseEventLog : Disabled
IGMPLevel : All
IGMPVersion : Version3
MulticastForwarding : Disabled
GroupForwardedFragments : Disabled
RandomizeIdentifiers : Enabled
AddressMaskReply : Disabled
Thanks for any thoughts.
Robert

Sorry for the poor follow-up Steven. We are using Server 2012 Hyper-V, not VMWare, on the hosts. You can close this but for the benefit of anyone who comes across it:
After working with Cisco, we decided not to implement multicast IGMP. Cisco says you still need to create a static ARP entry on the physical switch, though my cluster IP address & Microsoft NLB 2008 R2 were set up with igmp multicast, not multicast or
unicast. Here was his email:
Yes, we will need the static mapping for the NLB server in this case because the NLB mac address is multicast and the IP address is unicast. I was under the impression that even the server would be using IGMP but that’s not
the case. We won’t need to do the mapping for the nodes though if they use IGMP. To this end, following is the configuration that should make this work.rp 192.168.100.157
0100.5e7f.649d arpa
<u5:p></u5:p>
mac address-table static 0000.0000.649d vlan <> interface <> disable-snooping
ßThis is the switch interface where the NLB server is located<u5:p></u5:p>
interface vlan<>
<u5:p></u5:p>
ip pim sparse-dense-mode <- This is needed for the switch to elicit IGMP joins from the nodes<u5:p></u5:p>
end<u5:p></u5:p>
I don't think it got through to him that there was a virtual Layer 2/3 Hyper-V switch on top of 8 teamed GbE interfaces in LACP/hash. "Where the NLB server is located" = 1)a Cisco port-channel bound to one of six physical hosts; the NLB VM itself could be
on any of those port channels at any given time (We have a six node Hyper-V cluster).
Once I enabled pim I did see activity; but we killed this later as we realized we'd have to implement the same on 40+ managed routers globally
Anyway we further would have had to implement this across managed routers at 40 sites globally according to Cisco.
Robert

Hyper-V Server 2012 Migration Questions

Hello All,
This is my first post here, but I have used these forums many times for information. Sorry in advance for the long post.
I have a few questions regarding migration to Hyper-V server 2012 for my production environment. I have done quite a bit of reading, but I have a few direct questions and I would like to get some direct answers.
My current production environment consists of one PowerEdge 2900 with 2 Xeon X5460 Quad Core 3.16GHz CPUs, 24 GB of RAM and a RAID 10 consisting of 8, 500 GB HDDs for a total of 2TB of storage. I am currently running Server 2008 R2 Enterprise w/ GUI as the
Hyper-V host OS. I have 4 virtual machines all also running Server 2008 R2 Enterprise. The 4 virtual machines consist of 1 domain controller, 1 Exchange Server with Exchange 2010 Standard, 1 Server running SharePoint 2010 Enterprise and the remaining server
running IIS with FTP and HTTP.
The network topology is as follows….
Hopefully it is clear from my diagram that the Hyper-V host OS is connected to the same physical network as the domain, but is not a joined to the domain. I set it up this way because I had concerns about connectivity and manageability because the domain
controller is a guest VM. Also, the IIS server is on a completely different physical network independent of the domain.
What I would like to accomplish is the migration of the above environment to Hyper-V Server 2012 as is. I want to keep my existing guest VMs unchanged and running Server 2008 R2 for now as well as keep the existing network topology intact.
I have 3 additional servers in a separate test environment that would be able to serve as temporary storage or whatever is needed for the migration process.
Here are the two main things I would like to accomplish with this migration…
1. Make the transition from Server 2008 R2 to Hyper-V Server 2012 as a host OS.
2. Migrate virtual hard disks from .VHD to the new .VHDX format.
All that being said, I have finally come to my questions regarding this process.
First and foremost, I would obviously need to back up my current setup in case something goes horribly wrong during the migration. My question regarding the initial backup is would it be better to do a bare metal backup of the Hyper-V host or should I do
individual backups (bare-metal?) of the Guest VMs from within their operating systems?
Second, since I plan to use Hyper-V Server 2012, I will have to manage the host OS using the RSAT from a domain joined client running Windows 7 Professional. How much of a pain is it going to be to setup RSAT and manage the non-domain joined host from a
domain joined client? Is there a better way without using SCVMM or using Server 2012 w/ a GUI as the host OS?
Third, are there any concerns I should have, precautions I should take or procedures I need to do before, during or after the migration regarding the existing VMs and the new virtualized hardware environment on the same physical host?
Forth, should I use the trial version of SCVMM 2012 SP1 (or another previous version) to perform the migration? What should I be aware of using SCVMM for the migration and then discontinuing its use after the migration is complete and moving to management
using the RSAT?
Fifth, if I don’t use SCVMM for the migration, what is the best procedure for moving the VMs? Should I just copy the VHDs to a temporary storage location, install Hyper-V server 2012, copy the VHDs back, create new VMs and attach the VHDs or should I use
the export/import process?
Number six, when is the best time to migrate the VHDs to VHDX format and what would be the best method?
And finally, do I need to worry about USN rollback with a single domain controller? From my reading, this seems to be a point of disagreement. Some people say it could happen while others say it won’t. Is there any point during the migration process where
it could occur either during the copying of VHDs or from the switch to VHDX?
Again, sorry for the long post and thanks for staying with me this far. Any information would be much appreciated

1) As Jens said below with Windows Server 2012 you can simple copy the configuration files and VHDs from a 2008 R2 server to a 2012 server and import them - they one caveat to this is that any vlan configuration is lost and you have to simply re-create it.
Optionally you can also export the virtual machines from Windows Server 2008 R2 and then import them on Windows Server 2012.
2) Remote management in a workgroup does have some caveat's associated with it - take a look at
http://blogs.technet.com/b/jhoward/archive/2009/08/07/hvremote-refresh.aspx. Generally I would recommend joining the Hyper-V management operating system to the domain - not just because of these issues but for a number of other features to work properly
(see below)
3) I always recommend validating the hardware and environment after the installation before migrating critical workloads to it - testing networking, backup etc... to make sure they function as expected. Also ensure that you upgrade the integration
components in the VM's after the migration.
4) That is an option - though you might find you like SCVMM
5) Recreating VM's using existing VHD's has some issues for example the BIOS GUID changes, all of the NIC's are re-plug and played etc... When possible copying the configuration or using export is much better.
6) The sooner the better - VHDx has a number of significant advantages, you can do the migration using the Hyper-V manager UI (edit disk) or via powershell with Convert-VHD. Do keep in mind that during the conversation you need 2x the space (for the
original and the new VHDx).
7) In the past you could get into trouble if you for example snapshotted an AD virtual machine and than reverted it - taking one offline and then brining it back online was never a problem. In Windows Server 2012 we addressed this with a feature called
generation ID's.
Domain considerations... A few things to keep in mind regarding the choice to not domain join the Hyper-V server.
- You can't live migrate virtual machines
- You can't utilize Hyper-V over SMB
- Management is more difficult and less secure
-Taylor Brown -Program Manager, Hyper-V -http://blogs.msdn.com/taylorb

Hyper-V Live Migration Compatibility with Hyper-V Replica/Hyper-V Recovery Manager

Hi,
Is Hyper-V Live Migration compatible with Hyper-V Replica/Hyper-V Recovery
Manager?
I have 2 Hyper-V clusters in my datacenter - both using CSVs on Fibre Channel arrays. These clusters where created and are managed using the same "System Center 2012 R2 VMM" installation. My goal it to eventually move one of these clusters to a remote
DR site. Both sites are connected/will be connected to each other through dark fibre.
I manually configured Hyper-V Replica in the Fail Over Cluster Manager on both clusters and started replicating some VMs using Hyper-V
Replica.
Now every time I attempt to use SCVMM to do a Live Migration of a VM that is protected using Hyper-V Replica to
another host within the same cluster,
the Migration VM Wizard gives me the following "Rating Explanation" error:
"The virtual machine virtual machine name which
requires Hyper-V Recovery Manager protection is going to be moved using the type "Live". This could break the recovery protection status of the virtual machine.
When I ignore the error and do the Live Migration anyway, the Live migration completes successfully with the info above. There doesn't seem to be any impact on the VM or it's replication.
When a Host Shuts-down or is put into maintenance, the VM Migrates successfully, again, with no noticeable impact on users or replication.
When I stop replication of the VM, the error goes away.
Initially, I thought this error was because I attempted to manually configure
the replication between both clusters using Hyper-V Replica in Failover Cluster Manager (instead of using Hyper-V Recovery Manager).
However, even after configuring and using Hyper-V Recovery Manager, I still get the same error. This error does not seem to have any impact on the high-availability of
my VM or on Replication of this VM. Live migrations still occur successfully and replication seems to carry on without any issues.
However, it now has me concern that Live Migration may one day occur and break replication of my VMs between both clusters.
I have searched, and searched and searched, and I cannot find any mention in official or un-official Microsoft channels, on the compatibility of these two features.
I know vMware vSphere replication and vMotion are compatible with each otherhttp://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-8006BF58-6FA8-4F02-AFB9-A6AC5CD73021.html.
Please confirm to me: Are Hyper-V Live Migration and Hyper-V Replica compatible
with each other?
If they are, any link to further documentation on configuring these services so that they work in a fully supported manner will be highly appreciated.
D

This can be considered as a minor GUI bug.
Let me explain. Live Migration and Hyper-V Replica is supported on both Windows Server 2012 and 2012 R2 Hyper-V.
This is because we have the Hyper-V Replica Broker Role (in a cluster) that is able to detect, receive and keep track of the VMs and the synchronizations. The configuration related to VMs enabled with replications follows the VMs itself.
If you try to live migrate a VM within Failover Cluster Manager, you will not get any message at all. But VMM will (as you can see), give you an
error but it should rather be an informative message instead.
Intelligent placement (in VMM) is responsible for putting everything in your environment together to give you tips about where the VM best possible can run, and that is why we are seeing this message here.
I have personally reported this as a bug. I will check on this one and get back to this thread.
Update: just spoke to one of the PMs of HRM and they can confirm that live migration is supported - and should work in this context.
Please see this thread as well: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/29163570-22a6-4da4-b309-21878aeb8ff8/hyperv-live-migration-compatibility-with-hyperv-replicahyperv-recovery-manager?forum=hypervrecovmgr
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

No migrated network IP / Removal VMware Tools

Hello guys! good night!
I'm trying to convert about 100 VMWARE VMs to my Hyper-V 2012 R2 environment. I'm using the new MVMC 2.0.
After converting the VM, I realize that the network IP address was absent. The NIC was using the DHCP config. (The source VMWARE VM was configured with Static IP).
Other point is that the VMWARE tools wasn't removed.
In addition, during the migration process, the source VMWARE VM was power on and the MVMC did the snapshot and turned it off.
None of this itens has occured after the VM migration complete process. Even the VLAN ID in the VM settings on the Hyper-V was blank. No error message was returned. The whole migration process has completed successfully (green check mark).
On the link http://blogs.technet.com/b/privatecloud/archive/2014/04/08/migration-automation-toolkit-for-mvmc-2-0.aspx
states that with this tool is possible to:
MVMC removes VMware tools;
MVMC migrates network IPs;
But none of this itens has occured after the VM migration complete process. Even the VLAN ID in the VM settings on the Hyper-V was blank.
Besides this issues, the whole migration process has completed successfully (green check mark).
I would like to confirm that steps should I take to do a troubleshooting (for example, where can I find the verbose logs, etc).
Best regards,
Leandro
Leandro Soares - MCP/MCSA/MCTS

I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
Did you make any progress ??
Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
Makefile:120: recipe for target 'vmblock.ko' failed
Last edited by crankshaft (2014-01-10 11:32:32)

Hyper-V can't create a network switch in Windows 8 enterprise evaluation

Hello
I have a problem with creating a new virtual network switch in windows 8.
it's the error:
[Window Title]
Virtual Switch Manager for HYPER-VISOR
[Main Instruction]
Error applying Virtual Switch Properties changes
[Content]
Failed while creating virtual Ethernet switch.
[Close]

Hi,
If you are using Wireless network adapters.
Virtual switches can only be created that are bound to wired NIC's
Best regards,

Vmware fusion to hyper-v on Windows 8

I am trying to figure out if I can convert my VMWare Fusion images to Hyper-V images. I want to move from my Mac OS X running VMWare Fusion to Windows 8 running Hyper-V, I want to take my VMs with me. Is there a tool or method to do that. The only references
I have found are out of date.
Thanks
Matt

I assume you are doing this on a Mac.
keep in mind you will lose some functionality going to Hyper-V.
Hyper-V was designed for server virtualization and is missing features you may take for granted:
Sound support, 3d graphics, usb redirection, etc.
Yes, there is a "work around" (more like a hack in my opinion) that allows some of this functionality if you connect to the Hyper-V VM through RDP as opposed to the console directly. But that solution has it's own problems: You must enable RDP
on the VM and ensure network connectivity between host and guest (depending on the reason for the VM this is not always desirable or even acceptable).
Furthermore, if this is a MacBook Retina (with no Ethernet port), keep in mind you will need to share your wireless connection between host and guest. Bridging wireless connections does not work reliably under Hyper-V, resulting in network connectivity for
both the host and guest dropping periodically. Again, there is a work around for this by creating an 'internal' hyper-v network between the host and guest and then enabling windows internet sharing on your wifi adapter. This has some strong limitations, i.e.
the guest will be NAT-ted and the host will act as dhcp server and dns relay for the VM and is for all practical purposes, not configurable.

Migration of VMs from WS2012 Hyper-V Hosts Cluster to WS2012 R2 Hyper-V Hosts Cluster

Hello All,
We’re currently running our production VMs on a Failover Cluster of Windows Server 2012 Hyper-V Hosts. We’re planning to migrate these VMs to the cluster of
Windows Server 2012 R2 Hyper-V Hosts.
I have created a failover cluster of Windows Server 2012 R2 Hyper-V Hosts, and successfully tested the HA of my new test VMs on this new cluster.
Anyone please tell me the procedure, steps and best practices to migrate these VMs from Windows Server 2012 Hyper-V Hosts to Windows Server 2012 R2 Hyper-V
Hosts.
Thank you.
Regards,
Hasan Bin Hasib

Hi Hasan Bin Hasib,
You can refer the following related cross-version live migration KB:
Hyper-V: Migration Options
https://technet.microsoft.com/en-us/library/dn486792.aspx?f=255&MSPPError=-2147217396
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

VMware switch – migration to Hyper-V

Similar Messages

Maybe you are looking for