Mac OSX für VMware

Quelle
Snow Leopard Image für VMware Workstation / Player / Fusion.
VMware Image: Mac OSX 10.6.5 Snow Leopard
Extra Boot-CD's für verbesserte CPU unterstützung (Danke an soldier16):
nawcomModCD.iso 32Bit+64Bit
Sound-Patch:
Sound Patch für VMware
http://communities.vmware.com/t...ead/240010 .
TIP:
bevor ihr das Updates durchführt, macht einen Snapshot im VMware, damit ihr ein "Backup" vom laufenden System habt. Zu diesem Snapshot könnt ihr immer wieder "zurückspringen"!
Ergänzung:
Aktuell kann es aufgrund der Aktualität von einigen Mainboards und CPU's dazu kommen, dass das Image nicht funktioniert. Es liegt nicht am Image, sondern an der zu neuen Hardware, die nicht von OS X unterstützt wird.
-----------------------------------
Was ich bisher versucht habe:
- new Virtual Machine (Typical)
- install from
1: installer disc image file (iso) -- mit dem darwin_snow.iso. Ein gelbes ! erscheint mit folgender Meldung:
Could not detect which operating system is in this disc image. You will need to specify which operating system will be installed.
2: i will install os later
1: guest operating system other/other
Festplattenplatz zugewiesen und RAM erhöht
Wenn ich dann starte kommt:
Please wait for the DVD to load... EBIOS read error: Error 0x31
Wenn ich dann change Disc mache und das Iso auswähle: You should eject this CD and insert an OS X disc. Do you want to continue booting this cd (probably won't work)?
2: in der "Taskleiste" von VM Rechtsklick auf die CD, Settings, darwin_snow.iso ausgewählt, danach Connect. Boot from DVD ausgewählt und folgende Meldung erhalten:
You should eject this CD and insert an OS X disc. Do you want to continue booting this cd (probably won't work)?
Scheinbar erkennt er das darwin_snow.iso nicht als MacOsX

Increasing VMware Hard Disk Space

Source By expectus

For this example I am running VMware server on Windows Vista , WIth one virtual machine running Linux Ubuntu 8.04 Hardy and will go through the steps to increase my harddrive size from 15GB to 25GB
Increasing Hard Disk Size on your Virtual Machine ( VMware )
Step 1.
Firs thing to do is locate the location of vmware.exe on your PC typically it will be in
C:\Program Files\VMware\VMware Server or VMware Workstation
Once you have located your vmware.exe file open up command prompt on Windows.
[Start -> Run -> type "cmd" in the window then press ENTER
Now navigate into the vmware.exe directory , in this case simply
C:\Program Files\VMware\VMware Server
From here type
vmware-vdiskmanager -x 25GB image.vmdk
- 25GB in this case we would like to make the NEW size 25GB , this method will not remove any exisiting files
- image.vmdk , Name of your Virtual Machine disk my example was Ubuntu.vmdk, if for some reason it doesn't work type the entire path of the vmdk file for example
vmware-vdiskmanager -x 25GB D:\Virtual Machines\Ubuntu\Ubuntu.vmdk
corrected:
vmware-vdiskmanager -x 25GB "D:\Virtual Machines\Ubuntu\Ubuntu.vmdk"

Extending Partition / Hard Disk
Now that you have used the VMware diskmanager to increase size if the Virtual Disk Space , this will create a new parition that 10GB in this case
(original 15GB + 10GB increase).
This increased size will not automatically show up when we reboot our Virtual Machine.
We need to carry out a few extra steps to make use of this newly created space , this involves extending the partition or merging two partitions together.
Step 2.
Before trying to extend your harddrive to include the newly created partition, you will need to open vmdk file in a second virtual machine. The reason for this is that you cannot extend a partition on a drive that you are actually using system files on, It has to be set as the secondary drive.
So go through the steps of making a new virtual machine and give it 4-5GB or so it doesn't need to be huge. You wont actually need to load any Operating system on it if you use the LiveCD. Before you run your second virtual machine you will need to add the harddrive you wish to increase onto that system , see screenshot

Select your 2nd/Other Virtual Machine, then select Edit virtual machine settings, Click Add, Select Harddrive and use exisiting virtual then load your original harddisk , in my case Ubuntu.vmdk

Choose to start Ubuntu without installing it, Run it off the CD (LiveCD)

Gparted
Now that you have created your secondary virtual machine, Boot it up and in order to extend our virtual hard disk we will use a inbuilt linux tool called gparted , there are also many other partitioning programs out there including fdisk and many others.
Now we want to load up our ubuntu LiveCD instead of having to install an Operating System, To get your virtual machine to boot up from your LiveCD do the following.
- Use Daemon Tools or any other mounting program and mount your Ubuntu.iso image.
- Start your virtual machine and soon as it starts press ESC to enter the boot menu and from here select CD-ROM
- This will start your secondary virtual machine with the Ubuntu LiveCD
Running Gparted ( Partitioning Program )
To run gparted simply enter the terminal window and type "gparted" , and this will open the gparted gui window. ( Remember to issue this command with root privledges )
Once gparted has started you will see a window similar to below, We see two parition that we want to join together below circled in red, To extend the exisitng partition to the unallocated partition use the resize button to increase the size of the exisiting partition to increase the size.
( Ensure the harddrive is unmounted, and swapoff )

Not my original screenshot for this case but you get the drift:)

Resizing Partition , simply drag the handle across to pick a size or type in desired size
Finishing Up
Now once you have resized your partition to include the unallocated partition size click apply. This may take sometime for it to resize the partition size.
Once this is complete shutdown the virtual machine and remove the secondary harddrive you added in the previous section. Boot your original virtual machine and you should have successfully extended your hard disk space.
Gparted LiveCD
There is also a gparted LiveCD which can be run if you have trouble deleting and creating partitions. Simply mount the gparted LiveCD and follow the prompts. Link: http://sourceforge.net/project/showfiles.php?group_id=115843&package_id=271779
Other Methods
If you have made your way through this howto and still unable to get it to work you could try the Vmware Converter which can do all this tasks a lot easier, ( yeaa should've told you a lot earlier) its a free download and can perform partition extensions easily.
VMware Converter
Windows Method
After you have loaded the secondary harddrive on the secondary virtual machine (windows in this case) to fix the partitions. Run the command prompt and enter "diskpart.exe" or if that doesn't work locate its location and run it through cmd using the directory locations.
Steps - type
- show volume
select volume 2 ( in this case , double check to make sure you have the right one)
extend
exit
Then simply shutdown this virtual machine, remove the secondary hard disk, then startup the original virtual machine.

Virtual Machine Backup and Restore

Source (extract)

How often do you think about backups or your backup strategy? Most of us only think about such things during or after a failure occurs — because that’s then you need them. A good virtual machine (VM) backup strategy is a costly endeavor financially and in labor — or is it? It doesn’t have to be because your best backup strategy is part of your existing virtualization solution. Both VMware and Citrix provide the tools you need to create and maintain a successful backup strategy with supplied tools.

For backups, you have the following options:

• Treat VMs as if they are Physical Machines
• Treating VMs as Files
• Using an Internal VLAN for Client/Server Backup
• Snapshots¹ and VM Copy
• Built-in Backup Tools
• VM Cloning

Any method you choose has its drawbacks and not every method will work for every VM. You’ll probably have to use more than one backup method to satisfy backup requirements for your systems. For example, if you have an application server VM that cannot be shutdown or paused, then your best option is to treat this VM as if it were a physical system — meaning that you’ll install a backup client on it and backup its files over the network or to local disk or tape. Most of the other techniques require that the VM is quiescent, shutdown, or can tolerate decreased performance during the backup procedure.

For VMs whose services can go offline temporarily, treating the VMs as files is the traditional backup method. The VM disk images and configuration files are copied to storage media (Tape, Disk, SAN, NAS).

A generally non-supported strategy is to use an internal VLAN for backups. In this scenario, you run a backup client on your VM of interest and a backup server on another VM connected to a backup device and allows the backup to run. Both VMs must exist on the same host server so that the data isn’t transmitted over the physical network. This procedure takes its toll on the VM host system but the backup is very fast since no data flows over the LAN.

I like the Snapshot capability in VMware. A Snapshot is a hot copy of an entire VM while the VM stays up and running. For a very busy system, there may be a momentary disruption in service but the advantage of being able to grab a Snapshot far outweighs this minor downside. There’s no equivalent yet for Xen* users but the Snapshot is due for a future release. A VM copy (vm-copy) is the current Xen way to make a Snapshot of a VM. The downside is that the VM has to be shutdown (powered off) before making the copy.

Cloning is another oft-used backup method. For VMware and Xen alike, you’ll have to power off the VM to make a clone. For VMware, there is no direct clone creation tool. You’ll have to create the clone yourself by using a script, making a copy of the VM, or using the Snapshot method. Xen has a cloning tool (vm-clone) that’s used specifically for the job.

I don’t really like to say, “I love you, but” — or to take sides on a particular product but for backups, I’ll take the VMware road on backups alone. Xen, you’ve got a great product — a nice interface, a second-to-none Templating schema, world-class I/O but your backup technology is lagging behind. After all, what’s more important than backups for a company’s data and resources? Nothing except the data and resources themselves.

The second thing you should build into any software product, behind basic functionality, is the ability to backup, save, archive, or manage data versioning. It’s hard to believe that the only way to create true backups is to completely power off a virtual machine. Can you imagine powering off a physical machine when you need to do a backup? It isn’t very practical, is it?

If we are to move our valued infrastructure to a virtual one, then we need the same set of tools in those virtual environments that we have in the physical one. So, this discussion brings us back to the question, do you need to buy a third-party solution or can you use the built-in tools to do the job just as well? The answer is that if you’re running virtual machines that can’t be shut down for backups on VMware, you’re probably safe with the VMware-supplied tools. If you’re using Xen however, consider a third-party backup solution that doesn’t require shutting down your VMs.

¹ No SnapShot utility available as of XenServer version 4.1.

Kenneth Hess is a Linux evangelist and freelance technical writer on a variety of open source topics including Linux, SQL, databases, and web services. Ken can be reached via his website at http://www.kenhess.com.