Windows 10 X64 Will not boot when I add a second virtual hard drive

MacJohnMcC

Bit poster
When I boot with a single drive it boots fine. If I configure the VM to have a second new or existing virtual hard disk upon attempting to boot a few seconds in it shows a black window that has the "Parallels" logo in grey and it will never boot up but the process for the VM will run at 100% CPU usage. I thought it was because initially I tried adding a 256GB drive so I tried again with only 8GB no behavior difference.

I used to have more that one Hard disk for this VM but those were added before Parallels Desktop 14 came out so I don't know if this is a new problem in Parallels Desktop 14.

The first drive is SATA 0:1 and the second one I add shows as SATA 0:3.

I am running under macOS High Sierra (latest) and latest version of Parallels Desktop 14. The vm operating system is the current version of Window 10 X64 Pro latest version.

I checked the option to select boot devices at startup and it shows the message to press a key to select boot devices but then it freezes at that point instead of showing boot devices.

The tail of the parallels.log file shows this:

09-18 18:12:41.651 F /USB:22090:89347/ [UHC] DMA Started
09-18 18:12:41.651 F /monitor/ [UHC] Unsupported (unaligned) Read from 0x14 ()
09-18 18:12:41.851 F /USB:22090:89347/ [UHC0:203a:fffc:01.81i] ep create: dscr 07:05, attr 03, mps 000A, interval 01; streams_count 0
09-18 18:12:41.851 F /USB:22090:89347/ [UHC0:203a:fffc:01.82i] ep create: dscr 07:05, attr 03, mps 000A, interval 01; streams_count 0
09-18 18:12:41.857 F /monitor/ EHC controller reset
09-18 18:12:41.917 F /monitor/ [AHCI] Enable Command Queue Acceleration
09-18 18:12:41.917 F /monitor/ [SATA0] controller reset
09-18 18:12:41.917 F /monitor/ Enable AHCI mode
09-18 18:12:45.220 F /LocalDevices:22090:129027/ sync_request on dev(8:0) was not acked in time, continue wait...
09-18 18:12:46.919 F /LocalDevices:22090:89863/ sync_request on dev(8:0) was not acked in time, continue wait...

I have attached the parallels.log as parallels.txt

It does not show anything more even after waiting for a while.

Edit: I downgraded Parallels to version 13 and the behavior hasn't changed.

Any pointers would be welcome.
 

Attachments

Last edited:
Back
Top