5.0.2 doesn't boot raw image any more
Posted: 6. Sep 2015, 01:56
Hi there,
Things stopped working since upgrading to 5.0.2 on my Linux host. It worked well on 4.3, but now Windows 10 throws a BSOD with the message "UNMOUNTABLE_BOOT_DEVICE" when attempting to boot Windows.
The raw images were created using the usual "sudo VBoxManage internalcommands createrawvmdk -filename /home/ikt/vms/windows.vmdk -rawdisk /dev/sda" and the partition equivalent on whatever is on /dev/sdb1. This exact setup broke when upgrading to 5.0.2. I'm running VirtualBox as root, so it shouldn't have any read/writing issues. How's to fixing this?
Additionally, apparently hard-shutdown has disappeared from the machine settings and closing the window of a nonresponsive VM crashes the entire VirtualBox program, after which I need to kill the process manually.
Things stopped working since upgrading to 5.0.2 on my Linux host. It worked well on 4.3, but now Windows 10 throws a BSOD with the message "UNMOUNTABLE_BOOT_DEVICE" when attempting to boot Windows.
The raw images were created using the usual "sudo VBoxManage internalcommands createrawvmdk -filename /home/ikt/vms/windows.vmdk -rawdisk /dev/sda" and the partition equivalent on whatever is on /dev/sdb1. This exact setup broke when upgrading to 5.0.2. I'm running VirtualBox as root, so it shouldn't have any read/writing issues. How's to fixing this?
Additionally, apparently hard-shutdown has disappeared from the machine settings and closing the window of a nonresponsive VM crashes the entire VirtualBox program, after which I need to kill the process manually.