Fusion

 View Only
  • 1.  New Unibody MBP + Leopard Server issue

    Posted Oct 29, 2008 10:12 PM
      |   view attached

    As requested, I'm starting a new discussion thread to cover the problem I'm having with Fusion, Leoaprd Server, and my fresh new 'unibody' Macbook Pro. The problem is that every attempt to boot a Leopard Server installer results in a KP within the VM just after the grey screen / apple logo is presented. I have verified that the physical DVD media I used for the test case documented here successfully boots an older macbook pro. I have also tried various disk image installers of both leoaprd and 'a future Mac OS X release', all with the same results.

    My vmware.log is attached. Also, here is a QuickTime video demonstrating the kernel panic:

    My hardware info:

    andre@ba0801a-dhcp122 % system_profiler SPHardwareDataType

    Hardware:

    Hardware Overview:

    Model Name: MacBook Pro

    Model Identifier: MacBookPro5,1

    Processor Name: Intel Core 2 Duo

    Processor Speed: 2.53 GHz

    Number Of Processors: 1

    Total Number Of Cores: 2

    L2 Cache: 6 MB

    Memory: 4 GB

    Bus Speed: 1.07 GHz

    Boot ROM Version: MBP51.0073.B00

    SMC Version: 1.33f6

    Serial Number: W884069Z1GA

    Sudden Motion Sensor:

    State: Enabled

    Cheers!

    -dre

    Attachment(s)

    log
    vmware.log   133 KB 1 version


  • 2.  RE: New Unibody MBP + Leopard Server issue

    Posted Oct 29, 2008 11:23 PM

    What are your settings for the virtual machine you're installing leopard into? Some devices that never appear in "pure macs" could potentially cause a virtual mac to crash, or KP.

    You may also consider being careful about what is plugged into your mac while installing the virtual machine. It's not likely to be the case, but if you have an external drive plugged into your laptop which happens to be an OS X bootable drive WHILE you're installing a Leopard VM, I could see that might confuse things a bit.

    Most importantly, check your RAM settings for both your Mac and the VM. - In this same line of thought, consider shutting down all other programs while installing Leopard into a VM.

    Is your VM trying to install to a IDE disk or a SCSI disk? are the drives split-up, allocated all at once, one big VM file?

    I suggest using one big VM file with regular maintence to make for a happy host, and happy guests. Also I find that non-windows OS can be happier if they're installed on Virtual SCSI discs, NOT IDE. That is only my experience, I'm not sure why they'd care exactly but it seems to be the case.

    Good luck.

    P.S. here's an idea

    Install Leopard Server as the Host OS on the laptop, then use VMware inside Leopard Server to install regular Leopard (when it becomes avaliable if it isn't an option already)

    Also, never forget that it's important to consider your original task. If you're just trying to share files with a mac, there are MUCH easier ways to do this. What is the reason for which you're installing Leopard Server to begin with?



  • 3.  RE: New Unibody MBP + Leopard Server issue

    Posted Oct 29, 2008 11:36 PM

    What are your settings for the virtual machine you're installing leopard into? Some devices that never appear in "pure macs" could potentially cause a virtual mac to crash, or KP.

    From the video, it's all default settings. The default settings work for other people on other Macs, and should not change depending on the host, so this shouldn't be a problem.

    You may also consider being careful about what is plugged into your mac while installing the virtual machine. It's not likely to be the case, but if you have an external drive plugged into your laptop which happens to be an OS X bootable drive WHILE you're installing a Leopard VM, I could see that might confuse things a bit.

    From the video, there's nothing extra plugged in.

    Most importantly, check your RAM settings for both your Mac and the VM. - In this same line of thought, consider shutting down all other programs while installing Leopard into a VM.

    From the video, the only other programs running are the video capture software and Terminal.app. RAM could be a problem (Leopard Server wants 1 GB), except current MBPs start at 2 GB, so there should have been enough for Fusion to have allocated things correctly.

    Is your VM trying to install to a IDE disk or a SCSI disk? are the drives split-up, allocated all at once, one big VM file?

    I believe the default is SCSI. Default disk type is split, sparse.

    Install Leopard Server as the Host OS on the laptop, then use VMware inside Leopard Server to install regular Leopard (when it becomes avaliable if it isn't an option already)

    Due to Apple's EULA, you can only install Leopard Server in a virtual machine, not Leopard Client. I don't think this will solve the problem even if it were possible.



  • 4.  RE: New Unibody MBP + Leopard Server issue

    Posted Oct 30, 2008 12:42 AM

    What are your settings for the virtual machine you're installing leopard into? Some devices that never appear in "pure macs" could potentially cause a virtual mac to crash, or KP.

    You may also consider being careful about what is plugged into your mac while installing the virtual machine. It's not likely to be the case, but if you have an external drive plugged into your laptop which happens to be an OS X bootable drive WHILE you're installing a Leopard VM, I could see that might confuse things a bit.

    Most importantly, check your RAM settings for both your Mac and the VM. - In this same line of thought, consider shutting down all other programs while installing Leopard into a VM.

    Is your VM trying to install to a IDE disk or a SCSI disk? are the drives split-up, allocated all at once, one big VM file?

    I suggest using one big VM file with regular maintence to make for a happy host, and happy guests. Also I find that non-windows OS can be happier if they're installed on Virtual SCSI discs, NOT IDE. That is only my experience, I'm not sure why they'd care exactly but it seems to be the case.

    Good luck.

    P.S. here's an idea

    Install Leopard Server as the Host OS on the laptop, then use VMware inside Leopard Server to install regular Leopard (when it becomes avaliable if it isn't an option already)

    Also, never forget that it's important to consider your original task. If you're just trying to share files with a mac, there are MUCH easier ways to do this. What is the reason for which you're installing Leopard Server to begin with?

    etung has correctly answered most of your questions, but just to confirm:

    • no extra devices plugged in (other than standard ethernet)

    • RAM settings are default, which supply 1 GB to the VM. I have also tried giving 2 GB to the VM, same results

    • I've reproduced the issue directly after a reboot, with only Fusion running

    • SCSI disk (the default)

    The reason I want to use Fusion is to virtualize Leopard Server for testing and QA purposes. My job includes processing bugs filed against various versions of Mac OS X Server (10.5 and 10.6), and testing of (pre-release) software updates. Having various versions of Mac OS X Server available and online to verify bug reproduction steps or to verify a fix is quite helpful. Traditionally, this has required discrete hardware... virtualization will be a big win for us in this respect. So far I prefer Fusion over Parallels Server because Parallels server seems to require that the host OS be Mac OS X Server in order to run Mac OS X Server as a guest; Fusion does not have this requirement. Aside from that, I have also found Fusion to be a good deal more efficient - basic testing with a fairly vanilla Ubuntu Linux VM shows that Fusion idles at nearly half the cpu usage as compared to Parallels (when testing against the same VM image, with the same workload).

    Cheers,

    -dre



  • 5.  RE: New Unibody MBP + Leopard Server issue

    Posted Oct 30, 2008 01:05 AM
      |   view attached

    The installer just booted with Fusion in debug mode, leading me to believe that perhaps we're hitting some race condition - all of my previous attempts have been with debug mode OFF (seems like troubleshooting this one might be fun ;). Currently I'm looking at the installer 'desktop' background image and a spinning beach ball.... but this is well further than I've been able to get in the past :smileyhappy:

    Attached is the debug vmware.log

    The last few lines are:

    Oct 29 17:58:55.354: vmx| LOADAVG: 0.57 0.55 0.42

    Oct 29 17:59:25.352: vmx| LOADAVG: 1.03 0.66 0.46

    Oct 29 17:59:25.610: vmx| TOOLS setting the tools version to '0'

    Oct 29 17:59:25.610: vmx| DISKLIB-DDB : "toolsVersion" = "0" (was "7456")

    Oct 29 17:59:35.541: vcpu-0| HostSMCRead: Unable to read key "OSK0": 0x82.

    Oct 29 17:59:35.543: vcpu-0| HostSMCRead: Unable to read key "OSK1": 0x82.

    Oct 29 17:59:55.350: vmx| LOADAVG: 1.10 0.70 0.48

    Oct 29 18:00:25.353: vmx| LOADAVG: 0.97 0.71 0.50

    Oct 29 18:00:55.352: vmx| LOADAVG: 1.55 0.87 0.56

    Oct 29 18:01:02.348: mks| MKS switching absolute mouse on

    Oct 29 18:01:25.351: vmx| LOADAVG: 1.84 1.02 0.62

    Cheers,

    -dre

    Attachment(s)

    log
    vmware.log   182 KB 1 version


  • 6.  RE: New Unibody MBP + Leopard Server issue

    Posted Oct 30, 2008 01:54 AM

    The installer just booted with Fusion in debug mode, leading me to believe that perhaps we're hitting some race condition - all of my previous attempts have been with debug mode OFF (seems like troubleshooting this one might be fun :smileywink:.

    Yep :smileysilly:

    Oct 29 17:59:35.541: vcpu-0| HostSMCRead: Unable to read key "OSK0": 0x82.

    Oct 29 17:59:35.543: vcpu-0| HostSMCRead: Unable to read key "OSK1": 0x82.

    This is the one from the other thread that we fixed. Interesting to know debug mode may affect it.