Vista 64bit Host + VDI on USB HDD -> BUG?
Posted: 9. Jan 2009, 12:56
Hi,
I seem to have quite a special Problem:
I'm using a WinXP Prof. SP2 32bit Guest on several Hosts. Therefore the VDI file is located on an USB drive.
So far I never had a problem with this setup, until I upgraded all my host to VirtualBox 2.1.
On my Ubuntu 8.10 host and a WinXP 32bit host everything is still fine and works perfectly.
BUT: On my Windows Vista Ultimate 64bit SP1 host I now always get a BlueScreen at the end of the boot-process of WinXP saying: "unmountable_boot_volume"
I tried a lot to solve the problem. I found that when I transfer the VDI-file to the internal HDD of my Vista-maschine it works again perfectly.
Further when I ran a Ubuntu Live CD in the VM it coudn't acces the hdd as well, so the guest OS doesn't seem to be the problem)
So it seems to be this combination:
Vista 64bit? (I don't have a 32bit Vista to test)
+ VDI-file on USB-drive
--> no access to the virtual drive --> WinXP-BlueScreen
Can somebody confirm this? What can I do to fix this? Or is it a bug in the 64bit Version of the new VirtualBox 2.1??
Thanks
I seem to have quite a special Problem:
I'm using a WinXP Prof. SP2 32bit Guest on several Hosts. Therefore the VDI file is located on an USB drive.
So far I never had a problem with this setup, until I upgraded all my host to VirtualBox 2.1.
On my Ubuntu 8.10 host and a WinXP 32bit host everything is still fine and works perfectly.
BUT: On my Windows Vista Ultimate 64bit SP1 host I now always get a BlueScreen at the end of the boot-process of WinXP saying: "unmountable_boot_volume"
I tried a lot to solve the problem. I found that when I transfer the VDI-file to the internal HDD of my Vista-maschine it works again perfectly.
Further when I ran a Ubuntu Live CD in the VM it coudn't acces the hdd as well, so the guest OS doesn't seem to be the problem)
So it seems to be this combination:
Vista 64bit? (I don't have a 32bit Vista to test)
+ VDI-file on USB-drive
--> no access to the virtual drive --> WinXP-BlueScreen
Can somebody confirm this? What can I do to fix this? Or is it a bug in the 64bit Version of the new VirtualBox 2.1??
Thanks