Comment 0 for bug 1944619
Revision history for this message
| Erlon R. Cruz (sombrafam) wrote Instances with SRIOV ports loose access after failed live migrations | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
If for some reason a live migration fails for an instance with an SRIOV port
during the '_pre_live_
network and leave behind duplicated port bindings on the database.
The instance re-gains connectivity on the source host after a reboot (don't
know if there's another way to restore connectivity). As a side effect of this
behavior, the pre-live migration cleanup hook also fails with:
PCI device 0000:3b:10.0 is in use by driver QEMU
[How to reproduce]
Create an environment with SRIOV, (our case uses switchdev[1])
Create 1 VM
Provoke a failure in the _pre_live_migration process (for example creating a directory /var/lib/
Check the VM's connectivity
Check the logs for: libvirt.
Full-stack trace[2]
[Expected]
VM connectivity is restored even if it gets a brief disconnection
[Observed]
VM loses connectivity which is only is restored after the VM status is set to ERROR and the VM is power recycled
[1] https:/
[2] https:/