1566002266 Q * jrklein Remote host closed the connection
1566002339 J * jrklein ~cloud@34.234.31.16
1566016924 Q * Guy- Ping timeout: 480 seconds
1566020732 J * Guy- ~korn@0002809d.user.oftc.net
1566021195 Q * _pa Read error: Connection reset by peer
1566021247 N * Bertl_zZ Bertl_oO
1566031543 J * fstd ~fstd@xdsl-195-14-217-227.nc.de
1566032010 Q * fstd_ Ping timeout: 480 seconds
1566034919 M * torrunes Guy: yes, as root in VM
1566035089 M * Guy- torrunes: what happens if instead of mounting /dev/snd into the container, you just copy it there?
1566035096 M * Guy- into the container's /dev?
1566035191 M * torrunes will test. One moment.
1566035386 M * torrunes wow. That worked. :)
1566035445 M * Guy- maybe your bind mount had the 'nodev' option set somehow?
1566035518 M * torrunes i'm no expert on these things. Was first mounting it using the VM's fstab file under /etc/vservers/soundtest/ as this: 
1566035527 M * torrunes "/dev/snd       /dev/snd        none    bind,rw 0 0"
1566035585 M * Guy- I'm thinking maybe 'nodev' is the default somehow; does it work better if you explicitly mount it with the 'dev' option?
1566035614 M * torrunes let me try. BRB
1566035757 M * torrunes Yup. Works too. I'm impressed - thanks a lot for saving me hours of googling...! :)
1566036154 M * Guy- my pleasure :)
1566036220 M * Guy- however, I think copying is better than mounting; and if you insist on mounting, maybe try 'ro' instead of 'rw'
1566036233 M * Guy- (device nodes should still work on a read-only mount)
1566036258 M * Guy- if you bind mount /dev/snd, the guest can mess with the filesystem of the host; remove nodes from /dev/snd, create arbitrary files there etc.
1566036275 M * Guy- torrunes: if you just copy the specific device nodes the guest needs, there are no such issues
1566036352 M * torrunes Thanks for the hints. I will test varous scenarios. it's a usb sound card to be recording, and could be inserted into various usb ports. Don't know how that will affect any other matters like persistance on naming etc from host to host and so on.
1566036381 M * Guy- well, the naming should be irrelevant; it's the major/minor device number that's important
1566036419 M * Guy- maybe you could have an udev handler copy the device node to the guest on hotplug events
1566036442 M * torrunes that sounds like a good plan
1566036457 M * Guy- or use clsync to watch /dev/snd with inotify and propagate relevant changes to the guest (but udev is cleaner)
1566036527 M * Guy- if all of this is too complicated, the read-only bind mount still offers many of the security benefits (except that the guest also gets to use all other devices under /dev/snd)
1566036565 M * torrunes i also need to take care of that in some hosts the card should not be made available to the vm (another use case....) Anyway, thanks again for great help.
1566047067 Q * padde Remote host closed the connection
1566047123 J * padde ~padde@patrick-nagel.net
1566050297 Q * Aiken Remote host closed the connection
1566053988 Q * torrunes Quit: Konversation terminated!
1566070287 J * Aiken ~Aiken@b951.h.jbmb.net
1566078969 M * Bertl_oO  off to bed now ... have a good one everyone!
1566078972 N * Bertl_oO Bertl_zZ