Bug 524880
Summary: | The error message should be more explicit when bridge networking is disabled | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Laurent Léonard <laurent> |
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | berrange, crobinso, dallan, devurandom, laurent, libvirt-maint, mprivozn, xen-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: | 2013-06-25 13:11:09 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
Laurent Léonard
2009-09-22 15:03:08 UTC
Michal, is this still relevant? Currently you'll get: virsh # net-start default error: Failed to start network default error: Unable to create bridge virbr0: Function not implemented Can that be considered as more explicit? I think the requester wanted us to tell which package should he install - but that's out of libvirt scope (if even feasible). Getting 'Function not implemented' (=ENOSYS) is the best we can do here for a reasonable trade-off. Hence, I am closing this one. If somebody disagrees feel free to reopen with defining what's expected from a 'more explicit' error message in this case. Is there any other reason that this codepath would fail other than lack of bridge support in the kernel? If not, I'd say it should say: error: Unable to create bridge virbr0: Kernel lacks bridge support otherwise, I agree with you. The codepath is determined at build time. So no package installation/upgrade after you've build libvirt will change the path. Nor kernel package. The decision on the path is made depending on linux-headers package. In which case the most proper error message then would be "Bridge creation disabled at build time". Do we want to do that? |