Red Hat Bugzilla – Bug 799703
Cannot open /dev/dri/card0 from within LXC container: No such device
Last modified: 2013-04-05 15:27:05 EDT
Description of problem:
X (nouveau driver) won't start inside an LXC container, because it says
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
even though I've enabled device creation in cgroups and created the device node at that path. I've simplified the test case to just cat below, after the setup steps.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an LXC container called Rawhide (for a rawhide tree in my case, but it probably doesn't matter) in virt-manager
2. Start the LXC container
3. In a host terminal, as root do
echo a > /sys/fs/cgroup/devices/libvirt/lxc/Rawhide/devices.allow
4. In the LXC guest, as root do: mknod -m 660 /dev/dri/card0 c 226 0
5. In the LXC guest, as root do: cat /dev/dri/card0
cat: /dev/dri/card0: No such device
cat should wait indefinitely trying to read from the device, but not exit with an error. This is the behaviour observed on the host.
The ACLs reported by getfacl /dev/dri/card0 are different on the host and guest, but I don't see why this should make a difference - I'm running cat as root in both cases.
I'm going to be honest here. This isn't going to take a high priority with the fedora kernel maintainers. You will probably have better luck using a rawhide or self-built mainstream kernel and working directly with upstream.
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Clearing needinfo flags here.
Robin, did you ever take your request upstream?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Closing insufficient data since it has been so long without any response from the original reporter