ESXi to XCP-NG
Windows:
Export from ESXi as a single OVA file…save it,
Export from ESXi as a single OVA file…save it,
Import the OVA into XCP-NG
Wait for it…..
|
|
And start the VM once it’s imported…..
It should come up fine.
You *may* have to setup a new NIC and/or check / NIC’s and IP addresses. It’s possible that they will not be set up correctly.
Once the NIC is installed on the VM…install the XCP-NG windows tools/drivers.
That’s it.
It should come up fine.
You *may* have to setup a new NIC and/or check / NIC’s and IP addresses. It’s possible that they will not be set up correctly.
Once the NIC is installed on the VM…install the XCP-NG windows tools/drivers.
That’s it.
Linux:
Export the VM as an OVA file. (as above)
Import VM into XCP-NG (as above)
You *will* have to reset the NIC up (pretty much guaranteed)
It will be slightly different depend on each flavor/distro. You will probably need to find the directions for your specific version. You may have to mess with network config files etc…..
But roughly:
ip a --- look for any ip address
Export the VM as an OVA file. (as above)
Import VM into XCP-NG (as above)
You *will* have to reset the NIC up (pretty much guaranteed)
It will be slightly different depend on each flavor/distro. You will probably need to find the directions for your specific version. You may have to mess with network config files etc…..
But roughly:
ip a --- look for any ip address
If eth0 exists:
Sudo ip link set dev eth0 up
Sudo ip addr add 10.27.1.219/16 dev eth0
Ip address show dev eth0
Sudo ip route add default via 10.27.0.254
So far, the NIC is the only issue I have ever had with *nix based VM’s. Everything else “just works”.
For *nix based VM’s…. usually I don’t even bother installing the XCP-NG tools (unless it’s easy and they are already included in the distro)…I really haven’t noticed a difference in the machines at all. Admitted…my Linux boxes are all fairly low use, so it’s hard for me to judge. This also means that some of my machine information doesn’t show up in the XCP-NG dashboard…but it’s not a big deal to me.
Windows VM’s on the other hand….. I install the drivers. It makes a difference you can feel.
Sudo ip link set dev eth0 up
Sudo ip addr add 10.27.1.219/16 dev eth0
Ip address show dev eth0
Sudo ip route add default via 10.27.0.254
So far, the NIC is the only issue I have ever had with *nix based VM’s. Everything else “just works”.
For *nix based VM’s…. usually I don’t even bother installing the XCP-NG tools (unless it’s easy and they are already included in the distro)…I really haven’t noticed a difference in the machines at all. Admitted…my Linux boxes are all fairly low use, so it’s hard for me to judge. This also means that some of my machine information doesn’t show up in the XCP-NG dashboard…but it’s not a big deal to me.
Windows VM’s on the other hand….. I install the drivers. It makes a difference you can feel.