... being configured... looping
I upgraded from pd4 to pd5 so I would be able to run win7 in a vm on my mac presuming that pd5 supported win7 w/o issue.
I transport, using v5 of the transporter, the win7 machine to an external hdd. I moved that hdd to the mac, copied the pvm to a folder and try to open it with pd5.
Please wait wile the virtual machine is being configured...
(step 1 of 4)
fails
parallels tools are not installed.
now windows repair is running. so I can't start the install manually, as suggested. if I follw along, the vm restarts and we end up right back here. if I try choosing a repair option, the only thing that won't destroy the current vm is command prompt. you can't run the pd tools setup exe from command prompt.
I've saved the verbose output of the loop here:
http://www.easytospell.com/parallels/2009-12-20 looping parallels.log.zip
the most interesting part is here, where mounting of the iso fails:
20:35:45.790 F /gui:445:207/ Call install tools.
20:35:45.790 F /gui:445:207/ GUI issues install tools command for VM (silent=1)
20:35:45.791 F /gui:445:207/ localhost: sending [DspCmdVmInstallTools] request for VM {d869b7fc-2ef9-4fd5-a7fd-718711d116e8} [Windows 7] ...
20:35:45.821 F /gui:445:207/ localhost: received PET_DSP_EVT_VM_DEV_STATE_CHANGED. [CD/DVD 0: Disconnected, Image File]
20:35:47.312 F /gui:445:207/ localhost: received PET_DSP_EVT_VM_DEV_STATE_CHANGED. [CD/DVD 0: Connected, Image File]
20:35:47.313 F /gui:445:207/ localhost: received result for [DspCmdVmInstallTools]. RC = [PRL_ERR_SUCCESS]
20:36:53.295 F /gui:445:207/ Init timeout...
20:36:53.311 F /gui:445:207/ Init timeout. Abort.
20:36:53.312 W /gui:445:207/
Message info dump:
>> Object id = {a7608901-9087-4aba-91dd-278dd858d33e}
>> Issuer id = {d869b7fc-2ef9-4fd5-a7fd-718711d116e8}
>> Code = GUI_ERR_VM_HW_UPGRADE_VMXPHY_INIT_TIMEOUT
>> Type = Critical
>> Short Message = "You need to manually continue the process of configuring the "Windows 7" virtual machine."
>> Long Message = "To continue with the configuration, log in to your Windows virtual machine. If you have the CD autorun option enabled, the configuration will resume automatically. Otherwise, open My Computer and run the setup.exe file located on your CD, ignoring any Windows messages. For more information on configuring your virtual machines, <a href="http://www.parallels.com/support/pdfm5-reconfiguration-en_US">visit the configuration page</a> on the Parallels website."
>> Details = ""
>> Spontanous = 0
>> Can be hidden = 0
>> Force show = 0
>> Use active = 0
>> Event handle = 0
>> Answers: [OK] [] []
>> Default button number: 1
..>> Message hint: 0x0
20:36:53.313 F [MESSAGE_MNG] /gui:445:207/ Showing message box. Type = [Critical, GUI_ERR_VM_HW_UPGRADE_VMXPHY_INIT_TIMEOUT]. Id = {d869b7fc-2ef9-4fd5-a7fd-718711d116e8}
unless there is a way to install the tools from what amounts to safe mode command prompt, I see no way to fix this on my own.
I have already reduced the win7 vm to 1 gig ram (from 2) and one cpu. vid is set to 256. optimization is set: unchecked hypervisor, unchecked tune for speed. pd5 has been set for auto ram to 2 gigs ram. nothing I do seems to allow the iso to mount and run.
the computer I transported is a 6 hour one way drive from here, which would be a faster round trip, including the 2 hours to retransport to an external hdd, that transferring 90 gigs over the net.
Ideas?