Jump to content
23 posts in this topic

Recommended Posts

Leopard server works so much faster in this beta2 than in parallels server. It's amazing how it's fast on my mbp @2.4ghz/4gb ram

 

VMware crew have done a really good job :). Don't forget to install vmware tools of course ^^

 

ps: there's still somes issues with keyboard, sometimes when you hit a key for example "n", in the textinput we can see "nnnnnnnnnnnn", vmware repeat the same key, dunno why.., and i can't choose the good resolution for my screen, there is only 1400x900, but my screen is 1440x900, but it's not a huge problem :P

If you can't run the VMware tools installer, install with Pacifist and run services.sh, and enable sharing in the VM.

 

Sharing works fine with VMware Workstation Beta 2 99530 running Leopard 10.5.4 consumer version retail install with boot-132 dfe

 

Playing around with the VMwareIOFrameBuffer.kext now.

Hi,

 

I just burned the darwin.iso to a CD ROM and tried to boot my machine with it, this ask me for the OS X server but I dont have a copy at hand to try. It works exactly like the DFE boot loader.

 

The most interesting part are the included kexts, if they include kexts for audio and video may be a lot of the incompatibilities can be solved. I couldn't find any one for audio. Paralles server include the AppleAC97 to handle the audio I dont know what is vmware using.

 

Other interesting point is how they avoid the use of something like dsmos, may be they passthrough all the checking directly to the host.

You can't boot darwin.iso, if that's what you mean. Its a set of drivers/tools to be used inside the vm of course ... this is the iso that gets mounted when you select 'install vmware tools' from the menu.

 

Not really, I know is not a complete OS or something like that, what I tried to do was use it just like the modified DEF boot loader, as you can check in the credits this is basically the same boot loader, use the exact same structure, the kexts in the companion initrd.img are the same listed in DEF's web site and even display the same error about the missing plist. I was trying to check if using it avoid the use of the dsmos kext and how they did it.

 

Cheers.

I have been working on BOOT-132 for VMware and will be writing it up tomorrow. The VMware darwin.iso from Fusion 2 Beta 2 is intersting but you will find that some of the tools give an error when run on Workstation, plus the boot system looks for a Server image and needs the SMC controller present to get the keys for decryption. There is some useful stuff there but not sure how useful for Workstation.

there's still somes issues with keyboard, sometimes when you hit a key for example "n", in the textinput we can see "nnnnnnnnnnnn", vmware repeat the same key, dunno why..,

 

Use a SCSI virtual hard drive and it will solve this problem (it seems unrelated, but trust me it works).

For more "Mac OS in a VMware VM" goodies, see http://communities.vmware.com/docs/DOC-6670

 

and i can't choose the good resolution for my screen, there is only 1400x900, but my screen is 1440x900, but it's not a huge problem :rolleyes:

If you have installed VMware Tools, you should have access to all resolutions in System Preferences > Display.

Or are you saying that you see many resolutions inthat list, but that 1440x900 is somehow missing in that list?

 

But why do you care about specific resolutions? Resizing the VM's window works and will change the resolution of the Mac OS guest to an arbitrary size. In particular, you can Full Screen a Mac OS guest on top of a Mac OS host, which is pretty confusing :)

No you don't have QE on vmware fusion, even with the vmware tools installed.

 

For the resolution issues, it's not a big deal at all to run in 1400x900 instead 1440x900, it's a server, so i use it most of the time by using sharing screen :)

 

ps; for those who have a problem with dmg image disk - because vmware don't accept this format - you have to convert your dmg file in iso by using this command:

hdiutil convert osx-server.dmg -format UDTO -o osx-server-copy.iso

So I grabbed the vmware tools package in fusion beta 2 after installing OS X Server and transferred it over to my 10.5.2 VM and tried installing them.

 

They installed fine and VMWare recognized the tools as installed as well. I'm not completely sure how it has changed anything, though, other than identifying that VMWare tools in installed >_<

 

Anybody else given this a try?

So I grabbed the vmware tools package in fusion beta 2 after installing OS X Server and transferred it over to my 10.5.2 VM and tried installing them.

 

They installed fine and VMWare recognized the tools as installed as well. I'm not completely sure how it has changed anything, though, other than identifying that VMWare tools in installed >_<

 

Anybody else given this a try?

 

Can you post the vmware tools on rapidshare. I can try and give u feedback.

Cheers

The darwin.iso bootloader checks for /System/Library/CoreServices/ServerVersion.plist. If you want to burn it to a CD as a loader for OS X Client, you can patch a copy to check for SystemVersion.plist instead (hex editor, search for ServerVersion, replace with SystemVersion).

Sadly, the .iso's are signed, and VMware won't load them if the signature is wrong. So this doesn't work for installing inside a VM.

×
×
  • Create New...