how to move VM from vmware workstation to hyper-V
-
Although we should not that several contributors here that are quite active like @Carnival-Boy and @Breffni-Potter and @akp982 are British, not American, and while @dominica and I are American citizens we do not primarily live there. @joy and @nadnerB are busy contributors too, also not American. @MattSpeller is Canadian. @Ambarishrh is in the UAE. @nic lives in the US but isn't an American. Just some examples that I thought of quickly. I'm sure there are tons of non-Americans here that are busy posting. Certainly more American than not, but probably not as dramatically American as it can seem.
-
@scottalanmiller said:
Although we should not that several contributors here that are quite active like @Carnival-Boy and @Breffni-Potter and @akp982 are British, not American, and while @dominica and I are American citizens we do not primarily live there. @joy and @nadnerB are busy contributors too, also not American. @MattSpeller is Canadian. @Ambarishrh is in the UAE. @nic lives in the US but isn't an American. Just some examples that I thought of quickly. I'm sure there are tons of non-Americans here that are busy posting. Certainly more American than not, but probably not as dramatically American as it can seem.
So true @scottalanmiller , I find a lot of people here are very helpful not only from US, but from different parts of the world lols. Just make sure to explain your problem loud and clear, to get the best answer.
PS. I'm still in the process of learning
-
finally i solve the problem, thanks to this article : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2037891
i had to change the MAC address in ifcfg-eth0 because it retained the old one (issued by vmware), when i move the VM to XenServer, the MAC address changed in the VNIC but was not changed in the config file, i changed and it work fine, now i can ping and everything
but the weird thing is still i have unknown on the ip address in the networking tab in XenCenter even if i restart the host and the guest more than one time ?!!?!?!?
-
@IT-ADMIN said:
but the weird thing is still i have unknown on the ip address in the networking tab in XenCenter even if i restart the host and the guest more than one time ?!!?!?!?
Sounds like the Xen PV driver(s) is missing.
-
yes they are missing, i can't install them
-
i tried to mount the xenserver tool iso but it looks like my centos version is not compatible with xenserver
-
@IT-ADMIN said:
Now i have trouble with my VM, the IP is shown as unknown
, after doing some research i found out that i have to install xenserver tools, the bad news is i have to run CLI in both centos (for my freePBX VM) and freebsd (for my pfsense VM) to mount the iso located in my virtual DVD,
well i start with centos and do the following :
mkdir /mnt/DVD
in this stage the iso was mounted, isn't it ? i think yes because the directory contain the setup files for xenserver tool like this image show :
after that i launch the installer but i get a shitty message
i guess my centos version 6.5 is not supported, this is what a get
-
@IT-ADMIN said:
yes they are missing, i can't install them
They are needed for that kind of functionality. It is the PV drivers that allow the guest to communicate with the host.
-
@IT-ADMIN said:
i tried to mount the xenserver tool iso but it looks like my centos version is not compatible with xenserver
That does not sound right. What version of each are you running? We've used every modern version of CentOS on XenServer.
Ideally you install CentOS as PV, not as virtualized and then add PV drivers. CentOS is Linux and has a level of Xen support that exists in no other OS family.
-
Oh, because you brought over from VMware Workstation (which is a different architecture) you broke the compatibility for Xen. I'm not sure how difficult it will be to convert now.
Just do a fresh install.
-
@IT-ADMIN said:
i guess my centos version 6.5 is not supported, this is what a get
XenServer's own Dom0 is built on 6.5. It's the most compatible version. The issue is the P2V from VMware which can't do paravirtualization that is the problem.
-
oh i see, so the next frech install i should do it from the begining PV right
-
is there any differance btw virtualized and PV ??
-
@IT-ADMIN said:
oh i see, so the next frech install i should do it from the begining PV right
Yes, a fresh install is quite important here for multiple reasons that you have encountered.
-
@IT-ADMIN said:
is there any differance btw virtualized and PV ??
Yes, very different. That's why there are two names and why you are having problems here
-
-
do you mean by PV driver ::: the xenserver tool ??
-
@IT-ADMIN said:
do you mean by PV driver ::: the xenserver tool ??
that is the XenServer name for their PV drivers, yes.
-
what about the PV driver of the guest, what we call them ???
-
maybe front-end drivers
