PD6 - Win7 VM can't be configured nor started - PCI device???

I've just upgraded from PD5 to 6 and can't start my Win7 VM after two successful sessions anymore. I get the message (i translate it from german): "This virtual machine can not be started because there is a direct assigned PCIe-device in the configuration. The activation key for this product does not allow a direct assignment of PCI-devices to virtual machines."

I don't know what i've done in the configuration for the W7 machine but every time i try to change something or just to take a look at it and want to close the window, i get now "The PCI-device you want to add can not be used in this virtual machine. Do you want to add it anyway? (Yes or Cancel)". Whatever option i choose i can't get Win7 to start up.

After installation of PD6 Win7 was running two times, first to install Parallels tools (which leads to a hanging shut down but seems to work afterwards) and a second run to play around. I have done a normal shutdown the last time.

There was no hardware change, no new devices on my iMac Quad i5 8GB between the the last sessions under PD5, the two working sessions with PD6 and now.

What does this error mean and how can i get around it????

 

KlausL, can you please generate problem report (Help->Report a problem) menu and post here its ID next time this message appears? This will give us more technical information about the issue.

 

STim, thx for fast reply! Ok, my ID is 6643673.

Looking into the parallels log i see equal messages regarding sound devices and something like "Hardware Config changed" every time i've tried to start Win7.

The only thing that changed on my mac in the last days was a test with a new USB MIDI device which comes class-compliant and without any driver. This was included in my Audio/Midi configuration, but was inactive and not turned on today.

 

Thanks. Unfortunately the report misses the configuration of your virtual machine as it was taken when the VM was not open. Can you please open the VM that refuses to start this way (just open, do not need to start it) and resend the problem report? This will have problem reporter attach the VM config file to report.

 

Ok, this is the report after i tried to start Win7 and immediately get the message window. ID is 6643886 (i think).

 

It's #6643889

I have replicated the issue by simple copying your VM config from problem report. Extremely weird issue, and I cannot yet understand what causes it. I will get in touch with appropriate R&D team and get back to to this thread once I have something.

Thank you for reporting.

 

Thanx STim, i appreciate your work!

BTW: I have just updated PD6 with the latest patch available (11822) - no change with my Win7 prob. And i haven't changed anything in Win7 itself during the last working sessions.

My XP SP3 and the just tested ChromeOS VMs are working perfect.

 

Something i haven't described yet (was a hard day for me;-): I also had an Ubuntu VM in PD5 and PD6 after upgrading. I installed the Parallels Tools update into that but after reboot of Ubuntu the VM window remained all white, no chance for input with mouse or keyboard. So - as i had it only for some minor testing purposes - i deleted the Ubuntu VM with all data from PD6. IIRC right after that delete action the problems with Win7 occured.

 

Tadaaa!!! Now it's up and running again!!

Problem was (i think): Under PD5 i had configured Win7 to use Bridged Networking to have an individual IP generated and getting a logical OSX-to-Win network connection on the same mac. This was necessary for some MIDI-over-ethernet software.

I have changed it now to Shared Network Connection and voila... it works now with no error messages during configuration or startup.

I will report if this is reproducible when i switch back to Bridging but for now i'll take some sleep;-))

 

FYI: I can now switch back to Bridged network and select i.e. the Ethernet adapter and it works without problems. I remember that on the configuration page for network i saw that there was only "Bridged network" and not a specific adapter shown when i had the probs with refusing to start.

Thanx anyway for your effort, STim!

 

Klaus,

Thank you for the resolution. I just had exactly the same issue with an XP configuration upgraded from 5 to 6. Your solution of switching to shared networking worked for me too.