Ah... so it's an upstream issue with the included service/socket files?
Does not solve the systemd problem but: https://aur.archlinux.org/packages/vbox-headless-daemon
@WW - Hit the report button next time instead of replying. This what the mods get paid to do
@tomegun - I will follow-up with upstream. Can you provide me with some specifics regarding your 'proper solution'?
Just a guess but what if you allowed systemd to mount them?EDIT: https://wiki.archlinux.org/index.php/NF … t_handling
Just for closure, I bugged this both here and with upstream.https://bugs.archlinux.org/task/31846http://code.mythtv.org/trac/ticket/11160
It's okay, I like to be thanked. Enjoy.
Stupid question, but is there a way I can see the diff between these two?https://mailman.archlinux.org/pipermail … 24142.html
Well, I made that modification, rebooted, and I no longer have the error.
Something else is wrong. Start with finding out what app(s) are soaking up the CPU with a util like htop. Could also be IO so try iotop -Pao.