-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm trying to move a KVM guest to LXC and it utilizes ifb in order to rate limit the ingest rate of data. I'm having problems getting the ifb0 device up in the contianer but I get "Can't find device 'ifb0'" when tying to bring it up. The ifb module is loaded on the host. Host: Linux my-kvm 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux LXC: Debian Jessie root@betelgeuse:~# lsmod | grep ifb ifb 12637 0 root@betelgeuse:~# ip link set dev ifb0 up Cannot find device "ifb0" Unlike tun devices, I can't find a device in /dev to know how it should be "allow" in the container. For tun adapters I add this to the LXC config file: lxc.cgroup.devices.allow = c 10:200 rwm and I create the device inside the container: mkdir -p /dev/net mknod -m 0666 /dev/net/tun c 10 200 I suspect that something similar is needed for ifb, but I can't seem to figure it out. Please let me know if you have any ideas. - ---------------- Robert LeBlanc PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1 -----BEGIN PGP SIGNATURE----- Version: Mailvelope v0.13.2 Comment: https://www.mailvelope.com wsFcBAEBCAAQBQJVz56LCRDmVDuy+mK58QAA7vAQAI7RcsVU2YjGWNainio9 cP+KMI835vY2g2xJyQRRzIPDzBSDWhanNhSsfWKvSyY8u5Khtlguwq5VtX+h t++yFiaPbUeeTgXiFIUOXkvNypOmuVHGZCru4Xi9+OxHulo55OOHVAs5Uy6Q 6ibQa6XD7sbu36jhNTsiOU4SbouJXy5D6tbcVZ4D/CQ7nBpCYllhsiNZjYO0 P/Kg0QCjiFuNjhohXq5ap3NPhozAikiirPs5mSTcKpsTL6I/b6k3XSuI+zbF oTFjc8H5qqfw5cZ1rRvinyOM42c7l28ObdjHWFJruh8RkNiZCGKmjH00/DVR TzpSQohzNY8TIgk566cH9Fg5MaMJXgAaIK6KS6MT+lUZx3eR5Dhj0/J4IUkF CIdWMwociijZVKIvZY+B3b0kISEyWJ98Ym+ZIi7xQtJYKFO75/T2rBPbze7L KUDSz0xcQAPtcWuzE+aG6cChaXF0YAdovn4hgeRmrEZ1g6x3LQHqH+cFyQCS idXAKxBNHaEuuI9cyze0yHRw8vSyG7dHl7PWDiuDB3sQc2RhiLwGR0OgMNAl PS32aosbUj7dZdZfgv7fvG9r/HuVxjk7RtoQs1I8kmpH6FB9yKfea3Nsi14J IgjdkL/2tdz93RNMP5YkoW6VBZsmgwa+exQnaejV5DpRsOroi0rwsYFrOWDj 5lVR =LGto -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
