Bugzilla – Bug 202605
Not possible to install under Parallels
Last modified: 2006-09-29 21:41:40 UTC
It is not possible to install under Parallels, where it was possible to install Alpha 1 and 2. The Parallels sytem locks up. Attached you will find 2 frames I took from a movie I made of the process. One is just before the hangup and the next frame is what I see during the hangup. The sequence I do is boot the VM and enter 'linux' or any of the other options to start the installation with the result that the VM hangs. Parallels is available from Parallels.com and is a VM-manager, like VM-ware in case you did not know.
Created attachment 97485 [details] Situation just before the lockup
Created attachment 97486 [details] situatian just after lockup After this there is no change in the screen. CPU usage goes to 50% on a SMP kernel, using 100% of one of the CPUs.
Created attachment 98088 [details] Situation with 10 2 Alpha 4 Still not installable with Alpha 4. The message is however a bit better readable in the screenshot.
See also 203466 202079 and 204252
Created attachment 98310 [details] larger screenshot showing situation with alpha4 screenshot taken after using maxcpus=1 and vga=0x317 kernel options
This is likely a bug in Parallels, which we do not support. Please file the bug with the parallels project.
This is NOT a bug in Parallels. The same bug happens in older hardware and in VMware. See also 203466 202079 and 204252 and the thread "10.2 Alpha 4 install fails on low end hardware" on openSUSE factory mailinglist
Also see 204647 and 204647 and http://lists.opensuse.org/archive/opensuse-factory/2006-09/msg00380.html
Just out of curiosity, I replaced the boot kernel and initrd on CD1 with that from factory and the newer kernel still fails with a kenel panic. Kernel version used is 2.6.18-rc6-git3-2-default.
Created attachment 98788 [details] Screenshot using kernel/initrd 2.6.18-rc6-git3-2-default from factory Kernel version used in this screenshot is 2.6.18-rc6-git3-2-default.
*** This bug has been marked as a duplicate of bug 202079 ***