(add f10 diry trick) |
No edit summary |
||
Line 38: | Line 38: | ||
it's dirty, but so is vmware and this seems to work in x86_64 desktop. | it's dirty, but so is vmware and this seems to work in x86_64 desktop. | ||
= Fedora 18 beta in Vmware Fusion 5.0.2 on OS X 10.8.2 = | |||
Fedora gets to the screen that counts down, then does a few seconds more, then dies. VMware Fusion is still running, but the volume "needs repair". | |||
Tips welcome. |
Revision as of 02:58, 10 January 2013
This page will be a collection of tips for running Fedora in VMWare.
Fedora 7
If you're upgrading from a previous installation, you will need to switch your disk to "buslogic" emulation. See: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1216
Upgrading a FC6 image to F7 using the rescue ISO image seems to work after the above.
Fedora 10
Kernel modules does not compile, resulting an error:
/usr/lib/vmware/bin/launcher.sh: line 231: 11405 Segmentation fault "$binary" "$@"
http://communities.vmware.com/thread/172023 page suggests using following script as root user
#!/bin/bash cd ~ rm -rf vmware-modules mkdir vmware-modules cd vmware-modules find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \; mkdir -p /lib/modules/`uname -r`/misc rm -f /lib/modules/`uname -r`/misc{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko} cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko depmod -a service vmware restart
it's dirty, but so is vmware and this seems to work in x86_64 desktop.
Fedora 18 beta in Vmware Fusion 5.0.2 on OS X 10.8.2
Fedora gets to the screen that counts down, then does a few seconds more, then dies. VMware Fusion is still running, but the volume "needs repair".
Tips welcome.