vexxhost / vexxhost/migratekit
Post migration networking expectations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 138
- Forks
- 40
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Hi,
I've now got migratekit migrating a couple of VMs.
However, when I log into them they have no networking. Trying arp just hangs for example (I've tried a lot of other things too).
I've attempted installing drivers, etc, on the VM before migration to see if that helps, but I still have no networking. FYI, here's what I installed:
yum install -y qemu-guest-agent libvirt-daemon-driver-qemu qemu-kvm-core kernel-headers kernel-devel kernel-modules-extra
depmod
dracut --force
I've checked the security groups.
Is Migratekit supposed to handle networking during migration, or is this expected behaviour from migratekit?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Begin by reproducing a VMware-to-OpenStack migration with the listed guest packages and inspect the post-migration network state; done means confirming whether Migratekit handles networking and documenting the required behavior or a concrete failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100