![]() ![]() Remember that the Hyper-V integration is in embedded in Windows 2008 R2 and above and can not there for not be uninstalled from the VM. When this is done you can delete the VM’s from the import (they have now no assigned disks). Attach those disks to the first created VM containing the VHD file for Windows C: drive for example. When import is done detach the disks from the other VM’s that a created under the imports. If your Hyper-V VM consists of more then one VHD file you need to do this task for each VHD file. Here you must use the correct Network and IP (must be on the same IP network as the OS Fixup ISO SR. Choose where you want to place the virtual disk. Choose if you want the VM to have a home server. Configure how each vNIC (virtual network adapter) in FortiADC-VM will be mapped to each vNetwork on that XenServer, then click Next. Brows to the VHD file you want to import. This did not work, I didn’t see any new untitled virtual disks after rescaning the storage. – Attach the virtual disk you copied before from Hyper-V. – Rescan the storage and you will see a new untitled virtual disk in the storage panel in XenCenter. – Copy the VHD file from Hyper-V into the NFS share. NFS VHD and using the NFS share on the Windows server. ![]() – Create a NFS share on a Windows server. Xen Server support recomended this how ever it did not work in my environment: Because XenConvert does not work on version XenServer 6.2, I need to find another way to import virtual machines running in Hyper-V (Windows 2008 R2) to XEN Server 6.2.
0 Comments
Leave a Reply. |