hotblack said:
Well, Parallels 3 installed, old version overwritten, the VM I want to test upgraded so it can't be used with the version I own and normally use.
I agree with a lot of your criticisms but I think you're laying that particular one on a bit thick - its not a great effort to take a backup of your VMs before trying them with the new version (especially as it transpires that you're using the beta). Uninstalling V3 and re-installing 2.5 is not a massive undertaking.
I click the option to get a trial key, enter the required information in the User Registration form and click Register. I hadn't joined an airport network yet so it correctly failed, I joined a network then tried again.
Hmm - I've had problems there too when I recently tried to get a trial key that way, it apparently worked but the key email never came. Logging on to the parallels website and requesting a key seems to work better.
Networking: are you using bridged, shared or host-only? If you're using bridged then how is DHCP set up on your LAN - does it require MAC addresses to be registered on the DHCP server? If you're using wireless I'd suggest sticking with shared... (not sure how "bridged" interacts with wireless, encryption etc.)
Also, Ubuntu and other recent Gnome-based distros enable the Gnome network manager which simply doesn't work with manually-configured network addresses (and will helpfully disconnect them for you). Even if this is not the underlying cause, it might make it more difficult for you to work around the problem. (Back-up and try 'sudo apt-get remove network-manager' ).
Startup/shutdown: Parallels doesn't support ACPI under Linux (see the Parallels response in this thread:
http://forum.parallels.com/thread15575.html) so you'll have to power down manually. As long as you wait until Linux is halted its perfectly safe.
Also, there are "issues" with framebuffers in Parallels meaning that you often lose the startup/shutdown splashes in Linux distros. See here:
http://forum.parallels.com/thread14108.html for some tips.
Screen resolution selection: this is one of the weak points in most Linux distros anyway (I've had problems on 'real' PCs). However, this is one area where i've been impressed with Parallels tools for Linux - once you get them installed the Linux desktop dynamically resizes to fit the Parallels window (in this one respect, its better than VMWare which just choses the nearest 'standard' resolution).
In short - Linux support in Parallels leaves a bit to be desired, with popular distros like Fedora 7 and Ubuntu needing work-arounds to get a standard installation going. Fusion has more mature, established Linux support from VMWare on PC - the fact you can install Ubuntu or Fedora in Fusion and it just works is an undeniable plus.
To be fair - Fusion has probably inherited much of its Linux support from VMWare's PC versions which, historically, have been quite expensive developer/enterprise products. Odds are, the guest-side stuff 'just worked'. I doubt that they would have put much effort into Linux support for their Mac desktop product if it hadn't already existed.
Fusion is not perfect - installing the tools still entails resorting to the terminal, and often re-compiling for your kernel (but then they <i>do</i> more); if you try to install the tools after installing linux from an iso you hit the exact same bug as in Parallels (doesn't send a disc ejected message, so Linux sees a corrupt CD); the officialy "supported" distros all come out of the ark and (as mentioned above) Parallels' X display driver handles window resizing rather better.
Bottom line: the ads for Parallels say that it supports Linux, so its about time they got their act together and ensured that the 2-3 most popular distros would install and run out-of-the box. On the other hand - there is a limit to how much support for installing and configuring diverse operating systems you can expect for $80.
Some of your problems are well known issues with Parallels that should have been fixed by now. Others (the networking, and screen resolution) would require a lot of detecive work to track down and may be nothing to do with Parallels. E.g. a lot more info is required to diagnose the networking issue (and I'd lay odds that it is at least being complicated by an Ubuntu 'feature').