On Fri, 14 Oct 2016 09:29:08 +0200, Peter Bauer wrote:
I guess I have to use some Command line to get the machine up again...
Take a look at the log files. The paths are not necessarily those .VirtualBox/VBoxSVC.log* VirtualBox\ VMs/*/Logs/VBox.log* Regards, Ralf PS: I already wrote a script to backup and restore from an older backup, all settings and the guest, if something fails. VBox is easy to use, but regarding reliability a PITA. Sometimes it takes very long to repair something broken and sometimes it's impossible. Restoring from a backup usually is the better way to go. Btw. regarding to https://bugs.archlinux.org/task/50120 I stay with 5.0.24. [rocketmouse@archlinux ~]$ pacman -Q virtualbox virtualbox 5.0.24-1 [rocketmouse@archlinux ~]$ objdump -p /usr/lib/virtualbox/components/* 2>/dev/null|grep libvpx NEEDED libvpx.so.3 [rocketmouse@archlinux ~]$ pacman -Ql libvpx | grep so libvpx /usr/lib/libvpx.so libvpx /usr/lib/libvpx.so.4 libvpx /usr/lib/libvpx.so.4.0 libvpx /usr/lib/libvpx.so.4.0.0 [rocketmouse@archlinux ~]$ ls -hl /lib/libvpx.so* lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so -> libvpx.so.4.0.0 lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3 -> libvpx.so.3.0.0 lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3.0 -> libvpx.so.3.0.0 -rwxr-xr-x 1 root root 3.4M Jan 16 2016 /lib/libvpx.so.3.0.0 lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4 -> libvpx.so.4.0.0 lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4.0 -> libvpx.so.4.0.0 -rwxr-xr-x 1 root root 3.3M Aug 1 19:41 /lib/libvpx.so.4.0.0