Can't Launch Current VirtualBox Twice
by upnort from LinuxQuestions.org on (#54AHS)
Slackware 14.2 host, VirtualBox 6.1.8, Fully updated and functional Current virtual machine (VM).
For a long time I have been unable to launch a Current VirtualBox system twice.
After powering down the VM the next launch will crash, just before mounting the system partition read-only. There are no logs at that point in the boot and with such a crash accessing dmesg is impossible.
Shutting down VirtualBox and purging the kernel modules does not help. Temporarily dropping to runlevel 1 does not help. Using lsof reveals no open files.
The only cure is a full host reboot. After a host reboot, the Current VM launches but a forced fsck is executed.
Temporarily attaching the Current virtual disk to a Slackware 14.2 VM and manually running fsck fixes the disk errors but the Current VM will not launch without a host reboot.
Not a priority, but a nuisance. Sure would like to know the root cause.
Any ideas?
Thanks. :)
For a long time I have been unable to launch a Current VirtualBox system twice.
After powering down the VM the next launch will crash, just before mounting the system partition read-only. There are no logs at that point in the boot and with such a crash accessing dmesg is impossible.
Shutting down VirtualBox and purging the kernel modules does not help. Temporarily dropping to runlevel 1 does not help. Using lsof reveals no open files.
The only cure is a full host reboot. After a host reboot, the Current VM launches but a forced fsck is executed.
Temporarily attaching the Current virtual disk to a Slackware 14.2 VM and manually running fsck fixes the disk errors but the Current VM will not launch without a host reboot.
Not a priority, but a nuisance. Sure would like to know the root cause.
Any ideas?
Thanks. :)