Public bug reported:
This was introduced for bug 1370199 ages ago, I would expect this to no
more be functional - at least depending on the container type.
debian/qemu-kvm-init:
50 if systemd-detect-virt --quiet --container; then
51 mknod /dev/kvm c 10 232 || true
52 chown root:kvm /dev/kvm || true
53 chmod g+rw /dev/kvm || true
54 fi
At least in LXD system containers it will fail and do nothing useful
Jun 23 07:50:21 s qemu-kvm-init[2901]: mknod: Operation not permitted (os error
1)
Jun 23 07:50:21 s qemu-kvm-init[2902]: chown: cannot dereference '/dev/kvm': No
such file or directory
Jun 23 07:50:21 s qemu-kvm-init[2903]: chmod: cannot access '/dev/kvm': No such
file or directory
In LXD you'd nowadays add a profile to expose it
kvm:
path: /dev/kvm
type: unix-char
Would this still be helpful in other container types?
Or is this a relic from pre LXD and no more needed?
How does that look in other solutions?
Is it still worth to be kept?
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2157949
Title:
Should we drop the mknod for /dev/kvm in qemu-kvm-init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2157949/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
