Bug 1177464
| Summary: | NetworkManager in Xen dom0 crashes when a domU is started | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ting-Wei Lan <lantw44> | ||||||||
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 21 | CC: | dcbw, psimerda | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-12-02 06:32:00 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Ting-Wei Lan
2014-12-27 17:54:10 UTC
Created attachment 973547 [details]
NetworkManager log in systemd journal
Created attachment 973548 [details]
Dom0 dmesg
Created attachment 973549 [details]
Xen dmesg
It still crashes when using kernel-3.17.7-300.fc21.x86_64 xen-4.4.1-11.fc21.x86_64 NetworkManager-0.9.10.0-14.git20140704.fc21.x86_64 The problem can be fixed by upgrading NetworkManager to 1.0.0, but it causes gnome-control-center to show warning because of version mismatch. It is still broken on kernel-3.17.8-300.fc21.x86_64 xen-4.4.1-11.fc21.x86_64 NetworkManager-0.9.10.1-1.2.20150109git.fc21.x86_64 It is still broken on kernel-3.17.8-300.fc21.x86_64 xen-4.4.1-12.fc21.x86_64 NetworkManager-0.9.10.1-2.fc21.x86_64 Is vif2.0 being added to a bridge port by Xen here?
For NM devs, I think what's going on is this:
nm_device_activate_stage3_ip_config_start()
- sets ip4_state=IP_WAIT
- sets NM_DEVICE_STATE_IP_CONFIG
- the master interface's slave_state_changed() is called
- it calls nm_device_enslave_slave()
- nm_device_slave_notify_enslave() is called
- since the slave is activating it sets ip4_state = IP_DONE
- nm_device_activate_stage3_ip_config_start() is called
- g_assert (ip4_state == IP_WAIT), which clearly isn't true
Yes, vif2.0 is created and added to an existing bridge by Xen. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |