Solaris 10 x64 Crashes Fusion

[emader]

Hi,

I migrated a working Solaris 10 x64 VM from my PC (AMD) to my Mac Pro (Intel). The VM has 512 Mb memory and 2 processors.

When I try to start the VM in Fusion fusion crashes. Is anyone else seeing this? Could it be an AMD vs. Intel problem? (Installing Solaris is a bit of a pain, so I'd like to not have to reinstall if I don't have to...)

(I thought I'd posted this yesterday w/ the log files attached, but the post didn't show up. Perhaps it was rejected because the attachment was too big?)

Regards,

Eric Mader

[admin]

Your previous post is here: http://www.vmware.com/community/message.jspa?messageID=682940#682940

[nathanp]

Did you use any certain update of Solaris 10? (I think update 4 is available)

I have installed solaris10 update 3 x64 without any problems.

If you could let me know what update you use, I can try that as well.

Also, did Fusion crash or just the VM running?

Could you post the vmware.log?

\--edited since you posted the other files--

Message was edited by:

nathanp

[emader]

Here's what Solaris says about itself in the working VM on my PC:

$uname -a

SunOS unknown 5.10 Generic_118855-14 i86pc i386 i86pc Solaris

emader@unknown ~

$

Yes, Fusion itself crashed. Fairly early in the boot process, as far as I can tell.

Regards,

Eric

[admin]

Here's what Solaris says about itself in the working

VM on my PC:

$uname -a

SunOS unknown 5.10 Generic_118855-14 i86pc i386 i86pc

Versions of Solaris 10 before Update 3 will fail when run on certain Intel processors; this is a bug in Solaris and happens even on native hardware. The log you sent me shows that the error you're hitting is consistent with running an earlier version, and your version string also suggests this is the problem (118855-19 was when the fix was released).

See the last bit of:

http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/common/html/wwhelp.htm?context=GOS_Install&file=gue...

[Wes_W_]

You might also like to give Solaris Express Developer Edition (SX-DE) a try if you aren't running any type of mission critical applications, as this is not likely under Fusion's beta status anyway: http://www.sun.com/software/solaris/solaris-express/get.jsp

I've run Solairs Express for some time and like it, and now I run SX-DE as a Fusion guest without any problems.

[natedev]

Solaris Express Community Edition (Nevada) build 66 has been working for me on Fusion 1.0b4 although I haven't done extensive testing. I only dedicated one processor, 8 GB of disk space, and 1 GB of RAM. I would avoid giving it two processors just because, hey... we're already pushing it by running Solaris 11.

[emader]

I downloaded the latest version of Solaris (118855.33) and it's working fine in RC1!

Regards,

Eric

[lmcmulle]

The latest Solaris does work fine.

That said the solaris bundle packages (eg. WIS, or Comms server) do not... not not not... they will take 2 hours to install and fail to boot with a kernel fault.

L

[hhwong]

I'm having issues booting a freshly installed Solaris 10 64 bit VM on an Xserve -- Fusion RC1 crashes big time and corrupts the virtual disk (fsck can't fix the problem). 32 bit seems to be fine. I submitted the logs as a problem report, but no word yet.

Am I the only one that is having this problem?

[natedev]

Solaris Express Community Edition (Nevada) build 68 (64-bit) seems to work ok under Fusion RC1 on my MacBook Pro. I've not tried Solaris 10 nor used an XServe. It might be worth trying Solaris Express though and see if you get a different result.

[hhwong]

I'll try that, but while I imagine it's acceptable for problems within a VM, we shouldn't ever expect a crash of Fusion itself.

Anyway, here's an interesting tibit from the logs -- it was something related to graphics? It did crash on me after I selected Java Desktop after I logged in as root.

PID: 7410

Thread: 3

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0xb1e55000

Thread 3 Crashed:

0 <<00000000>> 0x020b18ae 0 + 34281646

1 GLRendererFloat 0x01e9c812 gldFPEmulateScanline + 424

2 GLRendererFloat 0x01e9b706 gldDrawPixels + 1634

3 GLEngine 0x04d7650b glDrawPixels_Exec + 1517

4 libGL.dylib 0x92b254df glDrawPixels + 111

5 vmware-vmx 0x0008fea2 0x1000 + 585378

6 vmware-vmx 0x002ebfd7 0x1000 + 3059671

7 vmware-vmx 0x00086ba6 0x1000 + 547750

8 vmware-vmx 0x002d5529 0x1000 + 2966825

9 vmware-vmx 0x002d6125 0x1000 + 2969893

10 vmware-vmx 0x002d64a8 0x1000 + 2970792

11 vmware-vmx 0x000842cc 0x1000 + 537292

12 vmware-vmx 0x0007aa2a 0x1000 + 498218

13 vmware-vmx 0x00025739 0x1000 + 149305

14 vmware-vmx 0x00025fae 0x1000 + 151470

15 vmware-vmx 0x00126578 0x1000 + 1201528

16 vmware-vmx 0x000850fa 0x1000 + 540922

17 vmware-vmx 0x00076948 0x1000 + 481608

18 libSystem.B.dylib 0x90024227 pthreadbody + 84

[hhwong]

Which MBP do you have by the way? My first generation Core Due MBP can't seem to run 64 bit OSes

[admin]

The first generation MacBooks and MBPs use the Core Duo[/url] processor, which is 32-bit only. Newer ones have the Core 2 Duo[/url] processor, which is 64-bit. A 64-bit processor is required to run a 64-bit guest at any sort of reasonable speed.

[hhwong]

Boom. Got another crash in Fusion with the Dev Edition (0507 I think) from OpenSolaris.org.

Could it be that I am primarily accessing the Xserve via Apple Remote Desktop or VNC? Some strange interaction there?

[natedev]

I would report the crashes to VMware and let them know the specifics of your environment. As you said, it could be the fact that you're accessing Fusion remotely.

[hhwong]

Wish I could. I can't seem to get past the first page of the problem submission report.