Bug 1266190
| Summary: | net-dhcp-leases returns nothing for VM that is restored after leases haved timed out | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Zeeshan Ali <zeenix> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED DEFERRED | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | crobinso, mclasen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-03 17:11:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
So turns out that this is caused by guest continuing to use it's last lease after being restored from a saved state. Maybe libvirt should try to retain the leases for VMs, maybe through a very large lease time (bug#913446). Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution. |
Description of problem: I have a domain running (on session libvirt) with following network configuration: ------------- <interface type='bridge'> <mac address='52:54:00:c2:2e:90'/> <source bridge='virbr0'/> <target dev='tap0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> --------- The networking inside guest is working fine too. However, system libvirtd (which afaik manages the virbr0) reports no active dhcp leases: --------------- $ virsh -c qemu:///system Welcome to virsh, the virtualisation interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # net-dhcp-leases error: command 'net-dhcp-leases' requires <network> option virsh # net-list Name State Autostart Persistent ---------------------------------------------------------- default active yes yes virsh # net-dhcp-leases default Expiry Time MAC address Protocol IP address Hostname Client ID or DUID ------------------------------------------------------------------------------------------------------------------- virsh # ------------- This worked at least a few months ago so I'm guessing this is some sort of regression. We use the net-dhcp-leases API in Boxes to retrieve the IP address of the guest. Version-Release number of selected component (if applicable): 1.2.13.1-2.fc22 How reproducible: 100% Steps to Reproduce: See above.