Feed on
Posts
Comments

Nevada 64a Running in VMWare Fusion

May 25th, 2007 by Lou

fusion-small.png

Woo-hoo! Now I’m off to try out vnics in Solaris 11!

I’ve encountered one minor issue, so far. Since the Solaris installer is 32 bit, I needed to create a 32 bit vm for the install. VMware was blowing up trying to get Solaris to install inside a 64 bit vm. I’ll need to futz with the Fusion configuration to see if it can stand being 64 bit now that the installation is complete.

Technorati , , ,

Posted in IT Architecture, Technology, Solaris 11 |

4 Responses to “Nevada 64a Running in VMWare Fusion”

  1. on 25 May 2007 at 1:46 pm   Scott Lowe

    If you do find a way to make Solaris 10 run 64-bit under Fusion, let me know. I kept running into a host kernel panic last time I tried. Supposedly the bug was fixed in the next beta release, but I still haven’t been able to make it work.

    Thanks!

  2. on 25 May 2007 at 2:17 pm   Lou

    I’m not getting a kernel panic *so far*, but I had to do the install with a 32 bit VM and switch it. There’s a line in the .vmx file for the vm.

    Change the line that says guestOS = "solaris10" to guestOS = "solaris10-64" after the install is complete.

  3. on 27 May 2007 at 9:38 am   Lou

    The issue with the 64bit install is that Fusion gives you a SCSI disk for the default 64 bit machine. There’s some issue between Fusion and Nevada for SCSI. Accessing a Fusion SCSI disks from Nevada causes a panic. If you delete the default SCSI boot disk and create an IDE boot disk, the 64 bit install works fine.

    I don’t think this issue exists for ESX. I have a Nevada build 52 ESX image.

  4. on 19 Jul 2007 at 7:50 pm   Inchoate Curmudgeon » Blog Archive » VMWare Fusion Version 1.0 (50460) and SCSI on Open Solaris X86

    […] In “Nevada 64a Running in VMWare Fusion” I posted a work-around for installing Open Solaris X86 Nevada build 64. […]

Trackback URI | Comments RSS

Leave a Reply