| Summary: | arping cannot see device inside LXC container | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robin Green <greenrd> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | berrange, clalancette, crobinso, itamar, jforbes, jskala, jyang, karlthered, laine, libvirt-maint, thomas.moschny, veillard, virt-maint |
| 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: | 2013-07-11 17:39:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Robin Green
2012-02-24 23:12:16 UTC
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. I've setup an LXC container using the virt-manager that is using only one virtual NIC - virtual network 'eth0': isolated network. Ifconfig shows only 'eth0' and the loopback device. # /sbin/arping -q -c 2 -w 3 -D -I eth0 192.168.1.55 sysfs read broadcast value: No such file or directory Arping is trying to access '/sys/class/net/eth0/broadcast', which I guess should be present. So to my understanding, LXC now knows only about the virtual device. But, because there is no information about the virtual device anywhere in the sysfs, there is no way for arping to actually work. And that would be a problem of LXC then. In my opinion, LXC should provide the correct information about the virtual devices. Afaik libvirtds's lxc is different from lxc itself, re-assigning. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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. This seems to work fine on F19, and since F17 is end of life soon, just closing as CURRENTRELEASE |