PD 4 on MBP early 2008 17"/10.5.6 does not boot virtual system

Discussion in 'Installation and Configuration of Parallels Desktop' started by kion, Dec 21, 2008.

  1. kion

    kion Member

    Messages:
    23
    Hi, everybody, am I the only person here to experience this:

    [​IMG]

    on boot?

    Last driver to be loaded before screen turns black with cursor is something like Mup.sys (not sure, as this passes pretty quick).

    Have done two migrations, the image runs flawless on my other MBP (late 2008) under 5608 and the same operation system (10.5.6).

    Any ideas are greatly appreciated.

    Ah, yes: I disabled the DVD, just to avoid this to be the reason, there is nothing loaded in the drive anyway.
     
  2. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Please stop Virtual machine, and navigate to Documents/Parallels or where is your VM folder
    in case of Parallels Desktop 3 - go to VM folder and delete .mem and .sav folders
    in case of Parallels Desktop 4 - right click on pvm bundle and select show package content and again delete .mem and .sav files
     
  3. kion

    kion Member

    Messages:
    23
    thanks, John - unfortunately there aren´t any files with that extension in the pvm-bundle. I am on PD 4, with 1036 MB dedicated RAM. The migration process of the VM to version 4 works flawlessly until step 4 of the migration, the system works until this step. When step 4 is finished and XP professional reboots, I am left with the blinking cursor.

    Any other ideas?
     
  4. kion

    kion Member

    Messages:
    23
    addition: I deleted the mup.sys from the drivers and the dllcache directory, but it´s obviously not the reason for the failure to boot. When booting in safe mode, the mup.sys does not come up anymore in teh list of drivers loaded, but the system stalls anyhow.

    Here are the last entries in the log:

    /drv/ HypRealCpu.c:578 CPUs calibrating
    /drv/ HypRealCpu.c:621 CPUs (2) TSC counter calibrating was successful (calibrate time 0 mksek)

    00:17:08.913 F /vm:10188/ [Profile] Event Loop post-initialization time is 19 msecs
    00:17:08.914 F /vm:10188/ [Profile] Event Loop Initialization time is 20 msecs
    00:17:08.914 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processed command vmCmdStart with status 1
    00:17:08.946 F /vm:10188/ [Profile] Post-Event Loop Initialization time is 31 msecs
    00:17:08.951 F /vm:10188/ Event loop inited - launching
    00:17:08.975 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processing command vmCmdInitiateDevStateNotifications ....
    00:17:08.999 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processed command vmCmdInitiateDevStateNotifications with status 1
    00:17:13.141 F /vm:10188/
    [0]Chipset Type i815, 2 CPU(s) (NORTH HUB DID&VID=0x80861130)
    [0]FirstStartInit is OK
    [0][1f:0] Secondary bus number 0xff

    00:21:07.912 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processing command vmCmdStop ....
    00:21:07.923 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processed command vmCmdStop with status 1
    00:21:08.552 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processing command vmCmdStop ....
    00:21:08.565 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processed command vmCmdStop with status 1
    00:21:08.587 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processing command vmCmdStop ....
    00:21:08.605 F /vm:10188/ Setting ASYNC_REQ_SHUTDOWN for Vm
    00:21:08.610 F /vm:10188/ Event loop terminated - deinited
    00:21:08.612 F /vm:10188/

    00:21:08.616 F /vm:10188/ [Devices] Terminating...
    00:21:08.617 F /vm:10188/ [Profile] Networking termination time is 0 msecs
    00:21:08.892 F /LocalDevices:10188/ [AppHDD] Disconnect
    00:21:08.905 F /vm:10188/ [Profile] IDE device 0 termination time is 288 msecs
    00:21:08.905 F /vm:10188/ [Profile] SCSI adapter termination time is 0 msecs
    00:21:08.905 F /LocalDevices:10188/ [Floppy0] Terminating
    00:21:08.906 F /LocalDevices:10188/ [Floppy0] Disconnecting
    00:21:08.908 F /vm:10188/ [Profile] FDD 0 termination time is 3 msecs
    00:21:08.908 F /vm:10188/ [Profile] FDD 1 termination time is 0 msecs
    00:21:08.909 F /LocalDevices:10188/ [Parallel0] Terminating
    00:21:08.909 F /LocalDevices:10188/ [Parallel0] Disconnecting
    00:21:08.912 F /vm:10188/ [Profile] Parallels port 0 termination time is 3 msecs
    00:21:08.912 F /LocalDevices:10188/ [CSoundDevice::Done] Sound output terminating...
    00:21:08.913 F /vm:10188/ [Profile] Sound output termination time is 1 msecs
    00:21:08.913 F /LocalDevices:10188/ [CSoundDevice::Done] Sound input terminating...
    00:21:08.914 F /vm:10188/ [Profile] Sound input termination time is 1 msecs
    00:21:08.918 F /vm:10188/ [Profile] USB controller termination time is 4 msecs
    00:21:08.918 F /vm:10188/ [Profile] Power source termination time is 0 msecs
    00:21:08.920 F /vm:10188/ [Profile] Tools dispatcher termination time is 1 msecs
    00:21:08.920 F /vm:10188/ [Profile] PCI toolgate termination time is 0 msecs
    00:21:08.927 F /vm:10188/ [Profile] PCI video termination time is 6 msecs
    00:21:08.928 F /vm:10188/ [Profile] OTG dispatcher 3 termination time is 0 msecs
    00:21:08.928 F /vm:10188/ [Profile] OTG request tracker termination time is 0 msecs
    00:21:08.941 F /vm:10188/ [Profile] Device used thread termination time is 13 msecs
    00:21:08.941 F /vm:10188/ [Devices] Terminating finished
    00:21:08.942 F /vm:10188/ [Profile] Terminating time is 326 msecs
    00:21:08.954 F /ioctl:10188/
    /drv/ HypVtd.c:3321 [vtdOnMonitorQuit]
    /drv/ HypVtd.c:1902 [vtdFreeDomain] Unknown domain, do nothing...
    /mon/ [HpcMonitorClose] Close monitor
    /drv/ HypVMManager.c:419 Monitor quited successfully

    00:21:08.972 F /vm:10188/ VMFiniMemory completed successfully
    00:21:08.974 F /vm:10188/ VM successfully stopped.
    00:21:08.976 F /vm:10188/ Vm {d1c885f9-eff7-4a99-989f-84581853dcdc} processed command vmCmdStop with status 1
    00:21:08.986 F /vm:10188/ [CMainThread::~CMainThread]
     
  5. kion

    kion Member

    Messages:
    23
    addendum 3

    in the migratuin process, I get a message at step 3 (if I remember right) referring to the non availability of access to a driver or file related to the DVD/CD drive. The process continues, though.
     
  6. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
  7. kion

    kion Member

    Messages:
    23
    ticket has been opened: Parallels / #644890: [PD4] Migration of Virtual HD from 3.x to 4.0 does not work.

    Please have a look asap, it has only been assigned a severity 3 level and it impedes my work.
     
  8. scrantch

    scrantch Bit poster

    Messages:
    5
    Same problem

    I have the exact same problem. Support keeps saying to delete the mem and sav files but I never have those in the .pvm bundle either. Mine loads past the splash screen and then sticks on black screen also looking for a driver Mup when in Safe mode.

    I'm on a MacBook Pro 15". Worked fine in v3 of Parallels but now, nothing but problems.

    Let me know what you figure out as I too am in a crunch and no one can seem to figure this out.

    Thanks.
     
  9. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    kion please see reply in ticket
     
  10. scrantch

    scrantch Bit poster

    Messages:
    5
    Can someone share with me what the reply in the ticket was please? I am having the same problem as stated.
     
  11. kion

    kion Member

    Messages:
    23
    TZhere was no response until now, not with a solution nor with a question, so I cannot share anything here yet.

    John, any insight on this as it seems to be a common problem?

    kind regards

    Kion
     
  12. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Ops, kion, Sorry,
    I see only escalation procedure there,
    I asked support to reply
     
  13. kion

    kion Member

    Messages:
    23
    solution found accidentally?

    Hi, everybody,

    a failure of my 30" Apple HD display might have led me to the solution for this problem. I had this display connected, while possibly a power surge took it out. Now I have to bring it to Apple to have it repaired.

    After disconnecting it from my MBP, I tried to start PD4 again - imagine my surprise to see it booting correctly!

    So the reason in PD4 not being able to use the virtual HD might have been the display. I cannot retry now with the display attached, because it´s in repair, but at least this narrows down the reasons for our problem.

    I would encourage the other users who reported similar problems to see if it has to do with an external display and report it here.

    BTW, the escalation procedure has been successful, Maxim contacted me and offered to log remotely in my system to help. Thanks to you for your support, and have a great new year.

    I suggest not to close the issue right now, as I haven´t been able to verify with the display, but may the other users who experienced the same behaviour have a go on it.
     
  14. kion

    kion Member

    Messages:
    23
    Unfortunately the same ocurs now on the MacBook Pro late 2008 alu brick case, with or without the Apple display attached, using the same virtual HD that worked finally on the 17".

    Have no idea why, but surely hte nice guys from Parallels will help.

     
  15. DaTa

    DaTa Hunter

    Messages:
    192
    Dear kion,

    The engineer replied in your ticket, please, find the message and kindly respond.
     
  16. kion

    kion Member

    Messages:
    23
    Thanks again for your help. I have been treated very well by Parallel´s support until now. I sent the info and will hopefully get somebody to check this out soon.

    kind regards!
     
  17. kion

    kion Member

    Messages:
    23
    Can a kind soul remind the support to connect to me?

    kind regards
     
  18. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    reminded to support
     
  19. kion

    kion Member

    Messages:
    23
    Big Thumbs up for Parallels support

    Yesterday evening Daria logged in to my system and helped to resolve the problem of not being able to migrate from the PD3 - compatible VM to PD4.

    I must say that I seldom have experienced such a thorough, friendly and experienced support person - a big thumbs up for Daria.

    The process was not easy at all, and in the end she ended up doing a manual migration process (still don´t know how to stop the automatic 4-step migration process, as I couldn´t see what was done to interrupt the process).

    In the end, some tweaking was done to arrive at an adequate system performance.

    I can´t thank Daria enough.
     

Share This Page