We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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).
arp
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?
The text was updated successfully, but these errors were encountered:
@paulfelton Does it fully not work at all? It seems odd that the networking doesn't work, are you able to launch VMs manually?
Sorry, something went wrong.
Hi there, I work with Paul and have picked this up while he's away.
The VM initially seems to migrate okay. It boots and I can access it and log in via the console in OpenStack. It's just networking that doesn't work.
Morning, as @markattree said, the VM migrates okay and we can log into it via the console. But there's no networking at all. Even running arp fails.
No branches or pull requests
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:
I've checked the security groups.
Is Migratekit supposed to handle networking during migration, or is this expected behaviour from migratekit?
The text was updated successfully, but these errors were encountered: