Vmware-workstation runs on amd64 with a little modification to the ebuild. That is: Adding a src_compile() that untar's vmmon.tar, patching one file to use pte_offset_kernel() instead of pte_offset() kernelfunction (latter doesn't exist on amd64), tar'ing it back and removing the created directory vmmon-only.
Created attachment 28817 [details, diff] Patch against app-emulation/vmware-workstation-4.5.1.7568.ebuild to work on amd64 I can't install vmware myself (No license). An amd64 user with a vmware license tested this and provided info for this patch. It works for him.
Created attachment 28818 [details, diff] Patch against app-emulation/vmware-workstation-4.5.1.7568.ebuild to work on amd64 Sorry, forgot to add: if [ ${ARCH} = "amd64" ...
Tried it with kernel 2.6.5, installs and runs just fine.
I'll look into it... I'm sure I'll need some testing on amd64 before I mark it stable, though.
I'll test it tomorrow... I have an interest in seeing this work.
I wouldn't call it stable anytime soon because there are issues that apparently only vmware.com can fix. They are: - Using USB in the VM kills host USB controller - Bridged networking mode doesn't work - Pasting text from vmware's dialog boxes (not from a VM) crashes vmware (some problem with my X 32bit libs perhaps?) - The first VM opened just crashes after a host reboot, the next attempts work fine. However, with these limitations in mind, it works great :) I would put it in ~amd64, with these (or whatever they may be) problems stated in the ebuild.
I'll be honest, there's no way I want to add amd64 to VMWare given the problems Tiago listed. In the end, I will be the one getting all of the bug reports for it, and I'm not willing to add a proven unstable product. The ~arch keyword does not mean unstable, it means testing for ebuilds only. If the package is broken, it should not be in portage at all, or package.masked if testing stability. We are aware that there are definite stability problems that appear to not only affect the guest, but also the host system. In my book, that is definitely reason enough to not include it. There's nothing stopping someone from adding an ebuild to their overlay, but I wouldn't feel comfortable with it in portage as long as I am the maintainer for VMWare and it is still not stable on the platform. We can revisit this issue once VMWare releases their next version and hopefully the stability problems will have been addresses and resolved.
*** Bug 47463 has been marked as a duplicate of this bug. ***
