| Summary: | vmware-workstation-tools 5.5.1 - virtual machine does not suspend | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | gentoo |
| Component: | New packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
| Status: | VERIFIED TEST-REQUEST | ||
| Severity: | normal | CC: | svec |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | In case it may be of help, I attach file var_tmp_portage_vmware-workstation-tools-5.5.1-r2_temp_eclass-debug | ||
I just wonder if this has been fixed now in the vmware overlay? Can you get the ebuilds from the vmware overlay listed on overlays.gentoo.org? You can also get it via layman. I want to know if it has been fixed there before I move them to the tree. If not, then I'll go ahead and move the ebuilds to the tree and try making a new ebuild in the overlay for this bug. We got the ebuilds from the vmware overlay listed on overlays.gentoo.org, but finally it fails emerging. Translations of messages: - The message "No existe el fichero o el directorio cp: no se puede efectuar `stat' sobre We got the ebuilds from the vmware overlay listed on overlays.gentoo.org, but finally it fails emerging. Translations of messages: - The message "No existe el fichero o el directorio cp: no se puede efectuar `stat' sobre «installer/services.sh»: No existe el fichero o el directorio" can be translated to "The file or directory does not exist. cp: you cannot do `stat' over «installer/services.sh»: The file or directory does not exist" The result of trying to emerge is: -------------------------------------------- # emerge vmware-workstation-tools Calculating dependencies... done! >>> Emerging (1 of 1) app-emulation/vmware-workstation-tools-5.5.1-r2 to / >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) * You will need VMwareTools-5.5.1-19175.tar.gz from the VMware installation. * Select VM->Install VMware Tools from VMware's menu. * Found CD #1 root at /root >>> Unpacking source... >>> Source unpacked. >>> Compiling source in /var/tmp/portage/vmware-workstation-tools-5.5.1-r2 ... >>> Source compiled. >>> Test phase [not enabled]: app-emulation/vmware-workstation-tools-5.5.1-r2 >>> Install vmware-workstation-tools-5.5.1-r2 into /var/tmp/portage/vmware-workstation-tools-5.5.1-r2/image/ category app-emulation /usr/portage/local/layman/vmware/eclass/vmware.eclass: line 190: cd: /var/tmp/portage/vmware-workstation-tools-5.5.1-r2/work/vmware-tools-distrib: No existe el fichero o el directorio cp: no se puede efectuar `stat' sobre «installer/services.sh»: No existe el fichero o el directorio !!! ERROR: app-emulation/vmware-workstation-tools-5.5.1-r2 failed. Call stack: ebuild.sh, line 1539: Called dyn_install ebuild.sh, line 1013: Called src_install vmware-workstation-tools-5.5.1-r2.ebuild, line 30: Called vmware_src_install vmware.eclass, line 272: Called die !!! services.sh !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/portage/local/layman/vmware' /usr/portage/local/layman/vmware/eclass/vmware.eclass: line 190: cd: /var/tmp/portage/vmware-workstation-tools-5.5.1-r2/work/vmware-tools-distrib: No existe el fichero o el directorio That looks like the root cause of the problem. What is the contents of /var/tmp/portage/vmware-workstation-tools-5.5.1-r2/work ? The /var/tmp/portage/vmware-workstation-tools-5.5.1-r2/work is empty. Created attachment 97728 [details]
In case it may be of help, I attach file var_tmp_portage_vmware-workstation-tools-5.5.1-r2_temp_eclass-debug
In today's tryings we also had problems installing the ebuild from the vmware overlay, since the emerge program always said there was a checksum error. It seems that the "manifest" file inside is wrong? Oops... fixed that now. I also fixed that it appears nothing was being unpacked. This should hopefulyl work now. By the way, I want to thank you for taking the time to troubleshoot this with me. We've tried it again, and again the "work" folder remains empty, showing the same error (the checksum error seems to be solved, since that error is not shown). We have noticed now that the "group" of the "work" folder is "root". More explicitly: all the folders of the same level of "work" have user=root and group=portage; however, work has user=root and group=root. We have also tried to uncompress manually the tar.gz in the "work" folder, but the installer deletes its content. Hiya guys, could you please give the open-vm-tools a try from the vmware overlay? Hopefully they're like a universal vmware-workstation/server/player-tools, and might fix your problem. If you could provide some feedback to this bug to let us know whether it works or not now, that'd be extremely helpful, thanks! 5:) At last we've been able to test it with the overlay and now it seems solved. Thanks to all Gentoo developers! |
EBUILD USED: vmware-workstation-tools 5.5.1 VMWARE TOOLS TAR USED: VMwareTools-5.5.1-19175.tar.gz KERNEL VERSION: Linux 2.6.15-gentoo-r5 VIRTUAL KERNEL VERSION: Linux 2.6.16-gentoo-r7 PLATFORM: Amd64 BUG: When trying to suspend the virtual machine, vmware shows an error in a window and cancels the operation, it says: "The request to suspend this virtual machine failed because the corresponding VMware Tools script did not run successfully. If you have configured a custom suspend script in this virtual machine, please inspect it for errors; otherwise, please submit a support request. The script can be deactivated on the Power page of the virtual machine settings by unchecking "Before suspending" in the Run VMware Tools Scripts section." In the log /var/log/vmware-tools-guestd of the virtual machine appears this message: Executing '/etc/vmware-tools/suspend-vm-default' initdir not found COMMENTS: If we directly use the vmware-config-tools.pl from the tar (without using the ebuild), the virtual machine can be suspended and resumed correctly; so there must be little errors inside the ebuild.