Linux won't boot natively after installing Virtual Box additions (#16985)
Posted: 20. Jun 2017, 00:55
Hello,
I'm trying to get the following configuration work: Windows 7 + OpenSuse Linux on different partitions, BCD bootmenu entry for starting Linux or Windows at boottime. And I want to be able to run the Linux in Virtual Box on the Windows host. In earlier Setups I simply installed Linux in Virtual Box on a device, created with something like "VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sda -partitions 1,5" and that's it. But now the Linux will not boot natively anymore, after installing the Virtual Box additions. The boot stopps with an error "A start job is running for dev-disk-by\ ... .device" - it seems it is the filesystem driver of Virtual Box, that causes this error.
I tried to deactivate the VB-additions by disabling the related services, but no succes. Even tried other Linux distributions (Kubuntu, Xubuntu) without success. When installing Linux natively and then booting it in Virtual Box, the setup of the VB-additions fails.
Does anyone here know, why the Virtual Box additions are not longer compatible with native hardware? How can I get the desired configuration working in a reasonable way?
Leaving out the VB-additions is possible, but for working I need at least the VB display driver and the collective clipboard.
I'm trying to get the following configuration work: Windows 7 + OpenSuse Linux on different partitions, BCD bootmenu entry for starting Linux or Windows at boottime. And I want to be able to run the Linux in Virtual Box on the Windows host. In earlier Setups I simply installed Linux in Virtual Box on a device, created with something like "VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sda -partitions 1,5" and that's it. But now the Linux will not boot natively anymore, after installing the Virtual Box additions. The boot stopps with an error "A start job is running for dev-disk-by\ ... .device" - it seems it is the filesystem driver of Virtual Box, that causes this error.
I tried to deactivate the VB-additions by disabling the related services, but no succes. Even tried other Linux distributions (Kubuntu, Xubuntu) without success. When installing Linux natively and then booting it in Virtual Box, the setup of the VB-additions fails.
Does anyone here know, why the Virtual Box additions are not longer compatible with native hardware? How can I get the desired configuration working in a reasonable way?
Leaving out the VB-additions is possible, but for working I need at least the VB display driver and the collective clipboard.