Hi Oliver,
We’re hoping
to try and use `diskimage-builder` to build an appliance
instead of a Docker image, because it seems there’s a lot of
issues around compatibility that we’re seeing right now.
For nbdcopy,
I’m not sure there’s much we can do in there, we’re relying
on an external tool to run this, it would be good to double
check, I think part of this is because it uses VDDK which
pipes all the traffic through vCenter (I think).
For the
cutover, I think it restarts with a full copy because VMware
CBT resets when the VM restarts (once again, not too
familiar, but I think), but the error you’re seeing is
because you need to specify the network mapping (which
essentially tells what VMware MAC address of interface maps
to which OpenStack network):
You can see
that documented in the README that explains how to specify
the network mapping, with the MAC, OpenStack network ID,
etc. IS it possible you have multiple NICs and you forgot
one of them in the defn?
Thanks for
all the feedback
Regards,
Mohammed
today we invested quite some time
to get it working and we noted a few things.
We use kolla-ansible and we
figured out that the migratekit needs to connect to
the metadata service in openstack. So we deployed a
fresh instance of Rocky9 and got stuck again with
some nbdcopy error and so we deployed ubuntu 24 with
docker and this time we got a lot further.
What is strange is that nbdcopy
is very slow. On our first try we only had around
40MB/s. Both source and destination are on SSDs with
a 10Gb network in between. Something we need to
investigate on.
We managed to get a copy done and
initiated the cutover but got stuck again at:
INFO[0000] Setting Disk Bus:
virtio
INFO[0000] Ensuring OpenStack
resources exist
INFO[0000] Flavor exists, ensuring
network resources exist flavor=flavor_2C_4GB_120GB
Error: no network mapping found for
MAC address
Strange was that after we did the
cutover the migrate would again start with a full copy
instead of incremental.
Hi Mohammed,
Many thanks for looking into this so quickly. A
colleague has tested your new container, but it
would not offer any suggestions for the VM name or
path.
He looked in your code and figured that you use
govc.
So he used it to figure out the correct path to
the VM:
Download govmomi Binaries
or directly install in linux using this executed
by root:
Afterwards set variables
accordingly to your credentials and execute this
to find the VM-Path for your vm (replace
password and <testvm*> accordingly. * is
Wildcard)
export
GOVC_USERNAME="<username>@<domain>"
export
GOVC_PASSWORD="**********"
export GOVC_INSECURE=true
export VMPATH="$(govc find .
-type m -name <vmname*>)"
##Output: /Datacenter
Germany/vm/Projects Cluster/Linux/testvm.local
##Output:
/<Datacenter>/vm/<Cluster>/<Folder>/<VM>
Feel free to add this to your Readme if you want.
It is a life saver. :)
We will do some more tests tomorrow and migrate a
couple of VMs.
Cheers,
Oliver
Am 26.08.2024 um 18:16
schrieb Mohammed Naser:
Hi
Oliver,
I
just pushed up a PR that I tested which
lists all VMs if it doesn’t find any VMs:
https://github.com/vexxhost/migratekit/pull/10
I’ve
merged it and this pushed up a new image
that has gotten promoted, so I suggest
pulling the latest image (aka `docker pull
…`) and trying again. It’ll help you find
the right path. 😊
Thanks,
Mohammed
thanks four
your quick reply.
Unfortunately
this also doesn't work.
Can you add
quotes around the path and
replace the %20 with spaces
and see if that works?
A frequent
ask is being able to list
VMs.. we may just add that
feature to make it easier to
use.
We struggled
using virt-v2v directly with
OpenStack. Our approach was
using ovftool to export the VM
as OVA and then create a qcow2
image that we can import in
OpenStack. So many manual steps
involved.
So I tested
your tool aganst vsphere 7.x
vcenter. But I just can't manage
to get it working.
It keeps
complaining about the path of
the source VM. I can use the
following just fine with
virt-v2v:
Using the
same in your tool:
docker run
-it --rm --privileged \
-v
/usr/lib64/vmware-vix-disklib/:/usr/lib64/vmware-vix-disklib:ro
\
--vmware-endpoint
vcenter.somedomain.local \
--vmware-username
user123 \
--vmware-password
XXXXXX \
--vmware-path
/GE%Office%20One/Projects/esx01.somedomain.local/test-vm-01
I tried many
different variants of the path
none has worked.
Is there a
way to lookup the path of a VM?
which shows
me all VMs running on that
particular ESXi host.