Comments on: Nevada 64a Running in VMWare Fusion http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/ I'm getting there. What's the rush? It's about the journey, right? Wed, 07 Jan 2009 08:23:47 +0000 http://wordpress.org/?v=2.0.4 by: Inchoate Curmudgeon » Blog Archive » VMWare Fusion Version 1.0 (50460) and SCSI on Open Solaris X86 http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-6836 Thu, 19 Jul 2007 23:50:09 +0000 http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-6836 [...] In “Nevada 64a Running in VMWare Fusion” I posted a work-around for installing Open Solaris X86 Nevada build 64. [...] […] In “Nevada 64a Running in VMWare Fusion” I posted a work-around for installing Open Solaris X86 Nevada build 64. […]

]]> by: Lou http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-4461 Sun, 27 May 2007 13:38:36 +0000 http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-4461 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. 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.

]]> by: Lou http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-4372 Fri, 25 May 2007 18:17:43 +0000 http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-4372 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<code> guestOS = "solaris10"</code> to<code> guestOS = "solaris10-64"</code> after the install is complete. 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.

]]> by: Scott Lowe http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-4371 Fri, 25 May 2007 17:46:21 +0000 http://blog.louspringer.com/2007/05/25/nevada-64a-running-in-vmware-fusion/#comment-4371 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! 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!

]]>