Bug 580806
Summary: | Network doesn't work after Live Migration | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lijian Xu <lxu> |
Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | berrange, clalance, crobinso, itamar, jforbes, moshe.ortov, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-17 17:51:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lijian Xu
2010-04-09 05:54:30 UTC
Can you still reproduce this issue? On the remote host, if you do 'virsh define $vmname' for the migrated VM, the reboot the VM, do you get network connectivity? Do VMs on the remote host have network connectivity to start? Can you provide the XML of the migrated guest? Can the guest ping public websites at all? Closing as INSUFFICIENT_DATA. Please reopen if you can reproduce with latest F13 or rawhide packages. I have what seems to be an identical issue. I can confirm that a reboot of the XP SP3 guest OS /does/ return the networking to operation - at the expense of making live migration a bit of a pointless exercise since the intention is to avoid the reboot and keep things running seamlessly. The identical cluster migrating a Linux VM works properly - there is no interruption to operation. NeatX/NoMachine sessions continue to operate and no pings are lost. Right now, this seems to affect XP SP3. I've tried it with and without the virtio network driver but the result is identical. My systems are AMD64 quad core CPUs - both servers are identical in all hardware. A tcpdump shows the XP guest sends out packets, these are forwarded over the bridge and the reply packets also come back onto the guest vnet0 device but the guest does not see them. e.g. a tcpdump shows the ping request and the reply packet but the guest itself does not receive the reply packet even though tcpdump shows it is there. |