open-vm-tools-devel — List for open-vm-tools developer discussions.

Re: cloning and pre-freeze script question

[Marcelo V. <mv...@vm...>]

On 02/12/2011 08:40 AM, Jim wrote:
> I loaded the missing libraries and was able to get cloning working.
> Am I correct in my thinking that if I don't include the /etc/pam.d/vmtoolsd
> file then guest user authentication cannot take place which effectively
> blocks unintended guest user operation through VIX?  The quiesce operation
> of cloning does not require guest authorization correct?

I believe that would work, although I've never tested it. I know removing that
file will block VIX operations, I just never tried quiescing with that file out
of the way...

-- 
- Marcelo

vmtoolsd segfault in libunity

[Jeremie L. R. <pou...@gm...>]

In ghIntegrationInt.h:Bool GHIPlatformIsSupported(void);

a string comparison is made with a null pointer when not running in a
supported desktop environment (In this case, xmonad)

vmware-xdg-detect-de prints nothing

Re: cloning and pre-freeze script question

[Jim <jim...@ho...>]

On 11-Feb-11 14:54, Marcelo Vanzin wrote:
> On 02/10/2011 12:18 AM, James Ko wrote:
>> I have a restricted shell which limits the user from the underlying linux apps and filesystem
>> but authorization is using the usual mechanisms.  VIX would allow access to the underlying
>> filesystem bypassing the restricted shell.
>>
>> As for the logs, the user is showing guestUserName=hostd-quiescedsnap but
>> VMAutomation_ReadGuestOperationPolicies fails. hostPolicyString is NULL
>> VixAutomation_IsGuestOperationAllowed fails. No policy for this operation
>>
>> Is this the reason for the failure?
>> What is the required policy and how does this need to be set?
> The logs you sent earlier seem to imply that you don't have the VIX guest
> components running (see all VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST). If that's the
> case, it's the first problem you need to fix.
>
> As far as the policy, I've been told that no configuration is needed for things
> to work. So make sure you have the VIX components running inside the VM if you
> want that to work, and let me know if you still get failures.
>
> Unfortunately your use case (restricted shell) wasn't really envisioned when
> this system was designed; so either you run VIX or, with the current version of
> ESX, lose the cloning functionality. On ESX 5.0 (yet to be released) the code
> path is different and doesn't use VIX anymore.
>

I loaded the missing libraries and was able to get cloning working.
Am I correct in my thinking that if I don't include the /etc/pam.d/vmtoolsd
file then guest user authentication cannot take place which effectively
blocks unintended guest user operation through VIX?  The quiesce operation
of cloning does not require guest authorization correct?

Jim

Re: cloning and pre-freeze script question

[Marcelo V. <mv...@vm...>]

On 02/10/2011 12:18 AM, James Ko wrote:
> 
> I have a restricted shell which limits the user from the underlying linux apps and filesystem
> but authorization is using the usual mechanisms.  VIX would allow access to the underlying
> filesystem bypassing the restricted shell.
> 
> As for the logs, the user is showing guestUserName=hostd-quiescedsnap but
> VMAutomation_ReadGuestOperationPolicies fails. hostPolicyString is NULL
> VixAutomation_IsGuestOperationAllowed fails. No policy for this operation
> 
> Is this the reason for the failure?
> What is the required policy and how does this need to be set?

The logs you sent earlier seem to imply that you don't have the VIX guest
components running (see all VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST). If that's the
case, it's the first problem you need to fix.

As far as the policy, I've been told that no configuration is needed for things
to work. So make sure you have the VIX components running inside the VM if you
want that to work, and let me know if you still get failures.

Unfortunately your use case (restricted shell) wasn't really envisioned when
this system was designed; so either you run VIX or, with the current version of
ESX, lose the cloning functionality. On ESX 5.0 (yet to be released) the code
path is different and doesn't use VIX anymore.

-- 
- Marcelo

RE: cloning and pre-freeze script question

[James Ko <jim...@ho...>]

I have a restricted shell which limits the user from the underlying linux apps and filesystem
but authorization is using the usual mechanisms.  VIX would allow access to the underlying
filesystem bypassing the restricted shell.

As for the logs, the user is showing guestUserName=hostd-quiescedsnap but
VMAutomation_ReadGuestOperationPolicies fails. hostPolicyString is NULL
VixAutomation_IsGuestOperationAllowed fails. No policy for this operation

Is this the reason for the failure?
What is the required policy and how does this need to be set?

Jim


> Date: Wed, 9 Feb 2011 11:32:38 -0800
> From: mv...@vm...
> To: jim...@ho...
> CC: ope...@li...
> Subject: Re: cloning and pre-freeze script question
> 
> On 02/09/2011 11:24 AM, James Ko wrote:
> > Is VIX really required for quiescing?   I would actually prefer to have VIX disabled as I see it as a potential
> > security risk for the guest.
> 
> VIX is needed for quiescing on Linux, yes; that's how the freeze / thaw scripts
> are executed. There are a few other operations from the UI that also need VIX
> support in the guest, although I don't remember more details.
> 
> VIX requires guest authentication for most, if not all, of its operations. An
> exception exists when the request comes from hostd, in which case VIX assumes
> that hostd / VC are properly authenticating / authorizing the user to perform
> that operation. So unless you have some concern regarding the latter, VIX
> doesn't really add any security risks to the VM.
> 
> -- 
> - Marcelo
 		 	   		  

Re: Jumbo frame support

[Dmitry T. <dt...@vm...>]

Hi Michael,

On Wednesday, February 09, 2011 10:13:49 am Michael Eager wrote:
> Are NIC jumbo frames (MTU=9000) supported in open-vm-tools?

Yes they are supported (I assume you are asking about vmxnet3).

Generally speaking there is no difference in features between drivers 
shipped with vmware tools, open-vm-tools and drivers that are part of the 
main Linux kernel (sans some possible time lag).


Hope this helps,

Dmitry

Re: cloning and pre-freeze script question

[Marcelo V. <mv...@vm...>]

On 02/09/2011 11:24 AM, James Ko wrote:
> Is VIX really required for quiescing?   I would actually prefer to have VIX disabled as I see it as a potential
> security risk for the guest.

VIX is needed for quiescing on Linux, yes; that's how the freeze / thaw scripts
are executed. There are a few other operations from the UI that also need VIX
support in the guest, although I don't remember more details.

VIX requires guest authentication for most, if not all, of its operations. An
exception exists when the request comes from hostd, in which case VIX assumes
that hostd / VC are properly authenticating / authorizing the user to perform
that operation. So unless you have some concern regarding the latter, VIX
doesn't really add any security risks to the VM.

-- 
- Marcelo

RE: cloning and pre-freeze script question

[James Ko <jim...@ho...>]

Hi Marcelo,

I've added the scripts, made it +x and confirmed they exit 0 but it did not help.
No debug logs (vmtoolsd nor vmsvc) on the guest indicate any requests from the host.

The vmware.logs for this guest shows and Unknown Command for VIX.

Feb 09 11:30:50.627: vmx| DISKLIB-VMFS  : "/vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1-flat.vmdk" : open successful (21) size = 4294967296, hd = 0. Type 3
Feb 09 11:30:50.629: vmx| DISKLIB-VMFS  : "/vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1-flat.vmdk" : closed.
Feb 09 11:30:50.635: vmx| DISKLIB-VMFS  : "/vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1_1-flat.vmdk" : open successful (21) size = 536870912000, hd = 0. Type 3
Feb 09 11:30:50.636: vmx| DISKLIB-VMFS  : "/vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1_1-flat.vmdk" : closed.
Feb 09 11:30:51.603: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue for guestUserName=hostd-quiescedsnap
Feb 09 11:30:51.603: vmx| VMAutomation: VMAutomation_ReadGuestOperationPolicies fails. hostPolicyString is NULL.
Feb 09 11:30:51.603: vmx| VMAutomation: VixAutomation_IsGuestOperationAllowed fails. No policy for this operation.
Feb 09 11:30:51.603: vmx| VMAutomation: VixAutomation_IsGuestOperationAllowed returns result=0
Feb 09 11:30:51.603: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue checking global refcount
Feb 09 11:30:51.604: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue featureRefCount=1.
Feb 09 11:30:51.604: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue loading dictionary /vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1.vmx
Feb 09 11:30:51.605: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue reading secret at guest.commands.sharedSecretLogin.hostd-quiescedsnap
Feb 09 11:30:51.605: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue found shared secret value Ofj7tz1Pcf+WDsZzgU+A0soxFzn1QLPkATsXOGuP/Gk=
Feb 09 11:30:51.605: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue for guestUserName=hostd-quiescedsnap
Feb 09 11:30:51.606: vmx| VMAutomation: VMAutomation_ReadGuestOperationPolicies fails. hostPolicyString is NULL.
Feb 09 11:30:51.606: vmx| VMAutomation: VixAutomation_IsGuestOperationAllowed fails. No policy for this operation.
Feb 09 11:30:51.606: vmx| VMAutomation: VixAutomation_IsGuestOperationAllowed returns result=0
Feb 09 11:30:51.606: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue checking global refcount
Feb 09 11:30:51.606: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue featureRefCount=1.
Feb 09 11:30:51.606: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue loading dictionary /vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1.vmx
Feb 09 11:30:51.607: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue reading secret at guest.commands.sharedSecretLogin.hostd-quiescedsnap
Feb 09 11:30:51.607: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue found shared secret value Ofj7tz1Pcf+WDsZzgU+A0soxFzn1QLPkATsXOGuP/Gk=
Feb 09 11:30:51.618: vcpu-1| Vix: [48586254 guestCommands.c:2488]: Error VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST in VMAutomationTranslateGuestRpcError(): Tools failed to recognize guest command op code=4, result string="Unknown Command".
Feb 09 11:30:51.619: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue for guestUserName=hostd-quiescedsnap
Feb 09 11:30:51.619: vmx| VMAutomation: VMAutomation_ReadGuestOperationPolicies fails. hostPolicyString is NULL.
Feb 09 11:30:51.619: vmx| VMAutomation: VixAutomation_IsGuestOperationAllowed fails. No policy for this operation.
Feb 09 11:30:51.619: vmx| VMAutomation: VixAutomation_IsGuestOperationAllowed returns result=0
Feb 09 11:30:51.619: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue checking global refcount
Feb 09 11:30:51.619: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue featureRefCount=1.
Feb 09 11:30:51.619: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue loading dictionary /vmfs/volumes/2eba8c1e-3d2a3850/VM1/VM1.vmx
Feb 09 11:30:51.620: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue reading secret at guest.commands.sharedSecretLogin.hostd-quiescedsnap
Feb 09 11:30:51.620: vmx| VMAutomation: VMAutomation_CheckSharedSecretValue found shared secret value Ofj7tz1Pcf+WDsZzgU+A0soxFzn1QLPkATsXOGuP/Gk=
Feb 09 11:30:51.628: vcpu-1| Vix: [48586254 guestCommands.c:2488]: Error VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST in VMAutomationTranslateGuestRpcError(): Tools failed to recognize guest command op code=87, result string="Unknown Command".

I restarted vmware tools and see this in the logs at startup

Feb 09 11:52:01.172: vcpu-1| TOOLS completing request from tools to set option 'synctime' -> '0'
Feb 09 11:52:01.174: vcpu-1| VMXVmdb_LoadRawConfig: Loading raw config
Feb 09 11:52:01.234: vcpu-1| GuestRpc: Reinitializing Channel 0(toolbox)
Feb 09 11:52:01.234: vcpu-1| GuestRpc: Channel 0 reinitialized.
Feb 09 11:52:21.544: vcpu-1| GuestRpc: application toolbox already registered, id: -1
Feb 09 11:52:21.544: vcpu-1| GuestRpc: Channel 0, guest application toolbox.
Feb 09 11:52:21.544: vcpu-1| Vix: [48586254 guestCommands.c:2488]: Error VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST in VMAutomationTranslateGuestRpcError(): Tools failed to recognize guest command op code=62, result string="Unknown Command".
Feb 09 11:52:21.545: vcpu-1| TOOLS ToolsCapabilityGuestConfDirectory received /etc/vmware-tools
Feb 09 11:52:21.545: vcpu-1| ToolsSetVersionWork did nothing; new tools version (2147483647) matches old Tools version
Feb 09 11:52:21.545: vcpu-1| Vix: [48586254 guestCommands.c:2488]: Error VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST in VMAutomationTranslateGuestRpcError(): Tools failed to recognize guest command op code=62, result string="Unknown Command".
Feb 09 11:52:21.545: vcpu-1| Vix: [48586254 guestCommands.c:2488]: Error VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST in VMAutomationTranslateGuestRpcError(): Tools failed to recognize guest command op code=62, result string="Unknown Command".
Feb 09 11:52:21.545: vcpu-1| Vix: [48586254 guestCommands.c:2488]: Error VIX_E_UNRECOGNIZED_COMMAND_IN_GUEST in VMAutomationTranslateGuestRpcError(): Tools failed to recognize guest command op code=62, result string="Unknown Command".
Feb 09 11:52:21.545: vcpu-1| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Feb 09 11:52:21.545: vcpu-1| Guest: toolbox: Version: build-261024
Feb 09 11:52:21.566: vcpu-0| TOOLS completing request from tools to set option 'synctime' -> '1'
Feb 09 11:52:21.566: vcpu-0| VMXVmdb_LoadRawConfig: Loading raw config

Is VIX really required for quiescing?   I would actually prefer to have VIX disabled as I see it as a potential
security risk for the guest.

James



> Date: Tue, 8 Feb 2011 17:05:53 -0800
> From: mv...@vm...
> To: ope...@li...
> CC: jim...@ho...
> Subject: Re: cloning and pre-freeze script question
> 
> On 02/08/2011 11:33 AM, Jim wrote:
> > I am using open-vm-tools 8.4.2 stable release but my linux other 2.6.x guest
> > will not clone due to failure of a reported pre-freeze script returning
> > non zero.
> > Similar error to report in Tracker-3107225.
> 
> First, a disclaimer: the 8.4.2 release is a stable release, but was only tested
> with Workstation and Fusion; so not all features that are used by ESX (such as
> quiescing) are necessarily stable in that release.
> 
> I know, this is kinda non-optimal, but it's something we're trying to fix
> internally, and when we get there it will trickle down to open-vm-tools naturally.
> 
> With that out of the way...
> 
> For ESX releases up to 4.1, quiescing for non-Windows VMs is quite simple; it
> just tries to run a script in the guest (the "freeze" script, normally
> /usr/sbin/pre-freeze-script), and after the snapshot is taken, tries to run
> another script (the "thaw" script, normally /usr/sbin/post-thaw-script).
> 
> On Linux, if the vmsync driver is loaded, it will try to use it; but since that
> driver hasn't really received that much testing (despite its age...), if you
> have it loaded I'd recommend you unload it.
> 
> Since that code hasn't really changed in a while, I believe it should work. So I
> suggest you check the two paths mentioned above, make sure they exist and are
> executable, and are not returning a non-zero value.
> 
> If that doesn't help, I'd need logs from your VM to know exactly what's going on
> when you try to clone (which creates a quiesced snapshot as part of cloning).
> Let me know if you need instructions on how to set up logging.
> 
> -- 
> - Marcelo
 		 	   		  

Jumbo frame support

[Michael E. <ea...@ea...>]

Are NIC jumbo frames (MTU=9000) supported in open-vm-tools?

-- 
Michael Eager	 ea...@ea...
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

Re: cloning and pre-freeze script question

[Marcelo V. <mv...@vm...>]

On 02/08/2011 11:33 AM, Jim wrote:
> I am using open-vm-tools 8.4.2 stable release but my linux other 2.6.x guest
> will not clone due to failure of a reported pre-freeze script returning
> non zero.
> Similar error to report in Tracker-3107225.

First, a disclaimer: the 8.4.2 release is a stable release, but was only tested
with Workstation and Fusion; so not all features that are used by ESX (such as
quiescing) are necessarily stable in that release.

I know, this is kinda non-optimal, but it's something we're trying to fix
internally, and when we get there it will trickle down to open-vm-tools naturally.

With that out of the way...

For ESX releases up to 4.1, quiescing for non-Windows VMs is quite simple; it
just tries to run a script in the guest (the "freeze" script, normally
/usr/sbin/pre-freeze-script), and after the snapshot is taken, tries to run
another script (the "thaw" script, normally /usr/sbin/post-thaw-script).

On Linux, if the vmsync driver is loaded, it will try to use it; but since that
driver hasn't really received that much testing (despite its age...), if you
have it loaded I'd recommend you unload it.

Since that code hasn't really changed in a while, I believe it should work. So I
suggest you check the two paths mentioned above, make sure they exist and are
executable, and are not returning a non-zero value.

If that doesn't help, I'd need logs from your VM to know exactly what's going on
when you try to clone (which creates a quiesced snapshot as part of cloning).
Let me know if you need instructions on how to set up logging.

-- 
- Marcelo

cloning and pre-freeze script question

[Jim <jim...@ho...>]

Hi,

I am using open-vm-tools 8.4.2 stable release but my linux other 2.6.x guest
will not clone due to failure of a reported pre-freeze script returning
non zero.
Similar error to report in Tracker-3107225.

I have also tried with 2010.12.19-339835 release which is working but I
would
prefer to only stay with stable releases for a "production" environment.

Some time ago I was also testing a monthly release (exact one unknown)
and cloning with those was also failing with those so I switched to the
stable
release.  Cloning was working for a period with the stable code but I think
that changed after moving the vmtoolsd start to a later point in the boot
process.

Can someone explain the data flow from starting the clone operation in the
vSphere client through to the VM processing the request?
How is a snapshot different from the clone operation when it comes to
quiescing operation?
I think the clone operation starts with a snapshot to get a
stable/quiesced disk
prior to cloning.  So what's different that snapshot works but clone
does not?

I am comfortable examining code but I'm not sure where to start looking.
Grepping/cscope has only led me to the vmbackup stateMachine which has
anything related to quiescing.  Is the vmbackup plugin required for cloning?

Any pointers appreciated. Thanks.
Jim

[ open-vm-tools-Tracker-3110351 ] Doesn't work on openfiler

[SourceForge.net <no...@so...>]

Tracker item #3110351, was opened at 2010-11-16 23:11
Message generated for change (Comment added) made by tobiasholst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: vmware-user
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tobias Holst (tobiasholst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Doesn't work on openfiler

Initial Comment:
Hi
I try to use Open VM Tools on Openfiler 2.3.
Kernel version is 2.6.29.6-0.29.smp.gcc3.4.x86_64.
The last working version was open-vm-tools-2010.01.19-226760.
Since then I get errors during "make install".
Configuration is "./configure --without-pam --without-x --without-icu"
open-vm-tools-2010.10.18-313025 can be configured but during "make install" I get the following:

fileLogger.c: In function 'VMFileLoggerOpen':
fileLogger.c:170: warning: implicit declaration of function 'g_atomic_int_set'
make[1]: *** [libvmtools_la-fileLoger.lo] Error 1
make[1]: Leaving directory '/root/open-vm-tools-2010.10.18-313025/libvmtools'
make: *** [install-recursive] Error 1

Greets from Germany
Tobias

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-02-04 01:40

Message:
Hi

open-vm-tools 2011.01.24, configure --without-pam --without-x
--without-icu
make install
threadPool.c: In function 'ToolsCorePool_Init':
threadPool.c:516: warning: implicit declaration of function
'g_thread_pool_set_max_idle_time'
make[3]: *** [vmtoolsd-threadPool.o] Error 1
make[3]: Leaving directore
'/root/open-vm-tools-2011.01.24-354108/services/vmtoolsd'
make[2]: *** [install] Error 2
make[2]: Leaving directore
'/root/open-vm-tools-2011.01.24-354108/services/vmtoolsd'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directore
'/root/open-vm-tools-2011.01.24-354108/services'
make: *** [install-recursive] Error 1

same with LDFLAGS=-lrt

Greets Tobias :)

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-02-02 19:20

Message:
The latest release should fix these issues, but I have a feeling there
might be more. We don't really test with glib versions that old...

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-15 01:02

Message:
Again with open-vm-tools 2010.12.19

./configure --without-pam --without-x --without-icu LDFLAGS=-lrt
make install

serviceObj.c: In function 'ToolsCore_Service_class_init':
ServiceObj.c:379: error: structure has no member named 'constructed'
make[3]: *** [vmtoolsd-serviceObj.o] Error 1
make[3]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services/vmtoolsd'
make[2]: *** [install] Error 2
make[2]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services/vmtoolsd'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services'
make: *** [install-recursive] Error 1

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 23:47

Message:
Could you try to configure with "LDFLAGS=-lrt"?

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-09 04:43

Message:
Hi

I just tried it with the open-vm-tools 2010.12.19

../lib/misc/.libs/libMisc.a(hostinfoPosix.o): In function
'Hostinfo_SystemTimerNS':
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1647:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1652:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1669:
undefined reference to 'clock_gettime'
collect2: ld returned 1 exit status
make[1]: *** [libvmtools.la] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/libvmtools'
make: *** [install-recursive] Error 1

Greets Tobias

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-12-02 23:12

Message:
This particular issue is fixed but there might be others. I just don't have
a system with a version of glib that old to test on.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

[ open-vm-tools-Tracker-3107225 ] Quiescing not Working on Ubuntu

[SourceForge.net <no...@so...>]

Tracker item #3107225, was opened at 2010-11-11 03:06
Message generated for change (Comment added) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3107225&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Quiescing not Working on Ubuntu

Initial Comment:
Quiescing not Working on Ubuntu 10.04.
pre-freeze-scripts are not triggered.

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-02-02 10:21

Message:
Can't do much here without more information. Our tests are working.

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 15:28

Message:
I tested with our internal build of Tools and it seems to be working
(tested with ESX 4.1). If you still see the problem, could you upload hostd
logs from your ESX host (or send them to me)?

Also, just in case, make sure the vmsync driver is unloaded.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3107225&group_id=204462

[ open-vm-tools-Tracker-3110351 ] Doesn't work on openfiler

[SourceForge.net <no...@so...>]

Tracker item #3110351, was opened at 2010-11-16 14:11
Message generated for change (Comment added) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: vmware-user
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tobias Holst (tobiasholst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Doesn't work on openfiler

Initial Comment:
Hi
I try to use Open VM Tools on Openfiler 2.3.
Kernel version is 2.6.29.6-0.29.smp.gcc3.4.x86_64.
The last working version was open-vm-tools-2010.01.19-226760.
Since then I get errors during "make install".
Configuration is "./configure --without-pam --without-x --without-icu"
open-vm-tools-2010.10.18-313025 can be configured but during "make install" I get the following:

fileLogger.c: In function 'VMFileLoggerOpen':
fileLogger.c:170: warning: implicit declaration of function 'g_atomic_int_set'
make[1]: *** [libvmtools_la-fileLoger.lo] Error 1
make[1]: Leaving directory '/root/open-vm-tools-2010.10.18-313025/libvmtools'
make: *** [install-recursive] Error 1

Greets from Germany
Tobias

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-02-02 10:20

Message:
The latest release should fix these issues, but I have a feeling there
might be more. We don't really test with glib versions that old...

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-14 16:02

Message:
Again with open-vm-tools 2010.12.19

./configure --without-pam --without-x --without-icu LDFLAGS=-lrt
make install

serviceObj.c: In function 'ToolsCore_Service_class_init':
ServiceObj.c:379: error: structure has no member named 'constructed'
make[3]: *** [vmtoolsd-serviceObj.o] Error 1
make[3]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services/vmtoolsd'
make[2]: *** [install] Error 2
make[2]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services/vmtoolsd'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services'
make: *** [install-recursive] Error 1

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 14:47

Message:
Could you try to configure with "LDFLAGS=-lrt"?

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-08 19:43

Message:
Hi

I just tried it with the open-vm-tools 2010.12.19

../lib/misc/.libs/libMisc.a(hostinfoPosix.o): In function
'Hostinfo_SystemTimerNS':
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1647:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1652:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1669:
undefined reference to 'clock_gettime'
collect2: ld returned 1 exit status
make[1]: *** [libvmtools.la] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/libvmtools'
make: *** [install-recursive] Error 1

Greets Tobias

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-12-02 14:12

Message:
This particular issue is fixed but there might be others. I just don't have
a system with a version of glib that old to test on.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

fix for compiling with --with-linuxdir

[Wojciech S. <vo...@co...>]

Hello,

The following patch fix issue when compiling open-vm-tools configured 
with --with-linuxdir=
Current version required to prepare valid link  /lib/modules/$(uname 
-r)/build and kernel , pointed to kernel sources.
- what is not valid solution and is not always possible. It was 
especially annoying for crosscompilation.
Attached patch is fixing this problem.

regards,
Wojtek Sawaściuk

[ open-vm-tools-Tracker-3073585 ] Out of memory and high cpu usage

[SourceForge.net <no...@so...>]

Tracker item #3073585, was opened at 2010-09-22 19:40
Message generated for change (Settings changed) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3073585&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: guestd
Group: v1.0 (example)
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Kleber  Rocha (kleberrocha)
Assigned to: Nobody/Anonymous (nobody)
Summary: Out of memory and high cpu usage

Initial Comment:
On Fedora 13 32bits open-vm-tools get all cpu and memory and freeze.

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2011-01-28 23:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 22:47

Message:
Without more information about what is going on (i.e., logs), there's
nothing we can do.

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-09-22 21:36

Message:
To try to fix whatever problem you're running into, we'd at least need logs
to know what's going on, since nobody in our internal QA has reported
similar issues. It might be a problem with some patch Fedora may have
applied, but again, without logs it will be really hard to figure out.

I don't generally follow updates for older releases of ESX, so I don't
know how the distro support for ESX 3.5 is looking these days.

----------------------------------------------------------------------

Comment By: Kleber  Rocha (kleberrocha)
Date: 2010-09-22 20:51

Message:
I agree, but the vmware-tools shipped with exx3.5 don't work with fedora, I
turn off the open-vm-tools and the system work fine, what do you recommend?
change fedora or exist other way to work with fedora?

Thanks

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-09-22 20:47

Message:
You really shouldn't be using open-vm-tools in a production environment,
since they're not officially supported by VMware. We always recommend you
use the VMware Tools shipped with your VMware product.

Without any logs it's gonna be hard to know what's going on.

----------------------------------------------------------------------

Comment By: Kleber  Rocha (kleberrocha)
Date: 2010-09-22 20:44

Message:
I use packages from rpmfusion. 
open-vm-tools-libs-0.0.0.243334-1.fc13.i686
open-vm-tools-0.0.0.243334-1.fc13.i686
akmod-open-vm-tools-0.0.0.243334-1.fc13.5.i686
kmod-open-vm-tools-2.6.34.7-56.fc13.i686-0.0.0.243334-1.fc13.17.i686

The version is: 8.4.1.1212 (build-243334)
We use ESX 3.5
The system freeze with kernel panic - Out of memory
The process that get all cpu: is vmtoolsd
No, this machine is production, and I can't stop this system to test with
log.

Thanks

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-09-22 20:33

Message:
There's not enough information here to do anything.

. which version of open-vm-tools are you running?
. which VMware product are you running?
. what does "freeze" mean?
. what's the process that's using all the CPU?
. have you tried to enable logging and see if any useful information shows
up?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3073585&group_id=204462

RE: guest failure to shutdown / reboot

[Edward N. H. <ope...@ne...>]

I never saw any reply to this.
Maybe this list or this project is basically abandoned???

Of particular interest:  
-1- I'd like to know if there is any documentation regarding the config
file.  I couldn't find any.
-2- If vmtoolsd is logging the "OS_Halt" signal, but then the OS doesn't
halt, I'd like to know how to go about figuring out what's wrong.

Thank you...



> -----Original Message-----
> From: Edward Ned Harvey [mailto:ope...@ne...]
> Sent: Sunday, January 16, 2011 12:01 AM
> To: ope...@li...
> Subject: guest failure to shutdown / reboot
> 
> On my system (pfsense 1.2.3 which is based on an old version of FreeBSD,
> running on vmware ESXi 4.0u1) I installed the Open-VM-Tools package
> (package ver 167859) via web interface, but I don't know which version of
> open-vm-tools that is.
> 
> Rebooted.  My vmtoolsd is running.  The rc.d scripts seem to work fine
during
> bootup.  The kldstat shows vmmemctl.ko, vmxnet.ko, vmblock.ko, and
> vmhgfs.ko loaded into the kernel.
> 
> But my host OS cannot shutdown/reboot the guest OS.  (And I don't know
> what else it can't do.)
> 
> I don't know what the cause of the problem is, but ps -ax shows me:
> /usr/local/bin/vmtoolsd -c /usr/local/share/vmware-tools/tools.conf -p
> /usr/local/lib/open-vm-tools/plugins/vmsvc
> and I noticed the conf file doesn't exist.  This seems suspicious.
> 
> I can't seem to find any documentation anywhere, indicating what should go
> inside that file?  But I'm not sure I should be sticking anything in that
file...
> 
> I enabled logging, issued the guest shutdown command from the host, and I
> got this in the log:
> [Jan 15 21:19:45.931] [   debug] [powerops] State change: OS_Halt
> [Jan 15 21:19:45.960] [   debug] [powerops] State change complete, success
=
> 0.
> 
> Nothing happened.  But at least I know the guest got the signal...  And I
don't
> know enough about open-vm-tools to figure out what I should look at
> next.  Like ...
> 
> When the guest gets that signal, what gets it?  Does the signal go
directly to
> vmtoolsd?
> Does vmtoolsd then launch some shutdown command, which is actually
> failing?  What is that command?

High CPU utilisation with NVIDIA driver in Win7+VMWareWorkstation

[Matthias A. <gu...@un...>]

Hello,

I've the following environment:

host:

Win7 Prof 64-bit,
VMWare-workstation 7.1.3 build 324285,
NVIDIA driver

guest:

FreeBSD 8-CURRENT,
Xorg-7.4.1,
open-vm-tools-253958 (from FreeBSD' ports collection),
KDE applications

The problem is:

After some time (minutes, not hours) the CPU utilisation in the VM goes
to 100% and makes the VM unusable because of its slow reaction on key
and mouse events; even after stopping the VM the CPU utilisation in the
host system Win7 stays at high level, even after stopping the VMWare
itself; this is only true if the NVIDIA driver in Win7 is used, not with
the standard Microsoft VGA driver itself;

It's hard to say if this is a bug in Win7 or NVIDIA or VMWare or Xorg,
that's why I wanted at least to ask here if there are know issues or
some pointers;

Thanks in advance for any hint

	matthias

-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <gu...@un...> - w http://www.unixarea.de/

guest failure to shutdown / reboot

[Edward N. H. <ope...@ne...>]

On my system (pfsense 1.2.3 which is based on an old version of FreeBSD,
running on vmware ESXi 4.0u1) I installed the Open-VM-Tools package (package
ver 167859) via web interface, but I don't know which version of
open-vm-tools that is.  

 

Rebooted.  My vmtoolsd is running.  The rc.d scripts seem to work fine
during bootup.  The kldstat shows vmmemctl.ko, vmxnet.ko, vmblock.ko, and
vmhgfs.ko loaded into the kernel.

 

But my host OS cannot shutdown/reboot the guest OS.  (And I don't know what
else it can't do.)

 

I don't know what the cause of the problem is, but ps -ax shows me:

/usr/local/bin/vmtoolsd -c /usr/local/share/vmware-tools/tools.conf -p
/usr/local/lib/open-vm-tools/plugins/vmsvc

and I noticed the conf file doesn't exist.  This seems suspicious.

 

I can't seem to find any documentation anywhere, indicating what should go
inside that file?  But I'm not sure I should be sticking anything in that
file...

 

I enabled logging, issued the guest shutdown command from the host, and I
got this in the log:

[Jan 15 21:19:45.931] [   debug] [powerops] State change: OS_Halt

[Jan 15 21:19:45.960] [   debug] [powerops] State change complete, success =
0.

 

Nothing happened.  But at least I know the guest got the signal...  And I
don't know enough about open-vm-tools to figure out what I should look at
next.  Like ...  

 

When the guest gets that signal, what gets it?  Does the signal go directly
to vmtoolsd?

Does vmtoolsd then launch some shutdown command, which is actually failing?
What is that command?

[ open-vm-tools-Tracker-3110351 ] Doesn't work on openfiler

[SourceForge.net <no...@so...>]

Tracker item #3110351, was opened at 2010-11-16 23:11
Message generated for change (Comment added) made by tobiasholst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: vmware-user
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tobias Holst (tobiasholst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Doesn't work on openfiler

Initial Comment:
Hi
I try to use Open VM Tools on Openfiler 2.3.
Kernel version is 2.6.29.6-0.29.smp.gcc3.4.x86_64.
The last working version was open-vm-tools-2010.01.19-226760.
Since then I get errors during "make install".
Configuration is "./configure --without-pam --without-x --without-icu"
open-vm-tools-2010.10.18-313025 can be configured but during "make install" I get the following:

fileLogger.c: In function 'VMFileLoggerOpen':
fileLogger.c:170: warning: implicit declaration of function 'g_atomic_int_set'
make[1]: *** [libvmtools_la-fileLoger.lo] Error 1
make[1]: Leaving directory '/root/open-vm-tools-2010.10.18-313025/libvmtools'
make: *** [install-recursive] Error 1

Greets from Germany
Tobias

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-15 01:02

Message:
Again with open-vm-tools 2010.12.19

./configure --without-pam --without-x --without-icu LDFLAGS=-lrt
make install

serviceObj.c: In function 'ToolsCore_Service_class_init':
ServiceObj.c:379: error: structure has no member named 'constructed'
make[3]: *** [vmtoolsd-serviceObj.o] Error 1
make[3]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services/vmtoolsd'
make[2]: *** [install] Error 2
make[2]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services/vmtoolsd'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/services'
make: *** [install-recursive] Error 1

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 23:47

Message:
Could you try to configure with "LDFLAGS=-lrt"?

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-09 04:43

Message:
Hi

I just tried it with the open-vm-tools 2010.12.19

../lib/misc/.libs/libMisc.a(hostinfoPosix.o): In function
'Hostinfo_SystemTimerNS':
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1647:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1652:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1669:
undefined reference to 'clock_gettime'
collect2: ld returned 1 exit status
make[1]: *** [libvmtools.la] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/libvmtools'
make: *** [install-recursive] Error 1

Greets Tobias

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-12-02 23:12

Message:
This particular issue is fixed but there might be others. I just don't have
a system with a version of glib that old to test on.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

[ open-vm-tools-Tracker-3107225 ] Quiescing not Working on Ubuntu

[SourceForge.net <no...@so...>]

Tracker item #3107225, was opened at 2010-11-11 03:06
Message generated for change (Comment added) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3107225&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Quiescing not Working on Ubuntu

Initial Comment:
Quiescing not Working on Ubuntu 10.04.
pre-freeze-scripts are not triggered.

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 15:28

Message:
I tested with our internal build of Tools and it seems to be working
(tested with ESX 4.1). If you still see the problem, could you upload hostd
logs from your ESX host (or send them to me)?

Also, just in case, make sure the vmsync driver is unloaded.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3107225&group_id=204462

[ open-vm-tools-Tracker-3118268 ] conflicting typedef for Bool

[SourceForge.net <no...@so...>]

Tracker item #3118268, was opened at 2010-11-25 03:48
Message generated for change (Comment added) made by admiralnemo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3118268&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: conflicting typedef for Bool

Initial Comment:
current builds of open-vm-tools fail with this error:

libtool: compile:  gcc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" -DPACKAGE_VERSION=\"2010.11.17\" "-DPACKAGE_STRING=\"open-vm-tools 2010.11.17\"" -DPACKAGE_BUGREPORT=\"ope...@li...\" -DPACKAGE_URL=\"\" -DPACKAGE=\"open-vm-tools\" -DVERSION=\"2010.11.17\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_ECVT=1 -DHAVE_FCVT=1 -DNO_PROCPS=1 -DHAVE_CRYPT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_IO_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE_UNWIND_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -I. -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -DGTK2 -DVMTOOLS_USE_GLIB -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fvisibility=hidden -DGCC_EXPLICIT_EXPORT -DRESOLUTION_X11 -I/usr/src/packages/BUILD/open-vm-tools-2010.11.17-327185/lib/include -I/usr/src/packages/BUILD/open-vm-tools-2010.11.17-327185/lib/include -DUSING_AUTOCONF=1 -DOPEN_VM_TOOLS -D_REENTRANT -I/usr/include -DUSE_ICU -DHAVE_ICU_38 -DVMX86_TOOLS -DNO_CORE_ICU -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -c resolutionX11.c  -fPIC -DPIC -o .libs/libresolutionSet_la-resolutionX11.o
In file included from /usr/include/X11/extensions/render.h:29:0,
                 from /usr/include/X11/extensions/Xrender.h:33,
                 from /usr/include/X11/extensions/Xrandr.h:33,
                 from resolutionX11.c:32:
/usr/include/X11/Xdefs.h:47:13: error: conflicting types for 'Bool'
/usr/src/packages/BUILD/open-vm-tools-2010.11.17-327185/lib/include/vm_basic_types.h:86:24: note: previous declaration of 'Bool' was here
resolutionX11.c:115:1: error: conflicting types for 'ResolutionBackendInit'
resolutionInt.h:73:6: note: previous declaration of 'ResolutionBackendInit' was here
resolutionX11.c:168:1: error: conflicting types for 'ResolutionSetResolution'
resolutionInt.h:76:6: note: previous declaration of 'ResolutionSetResolution' was here
resolutionX11.c:205:1: error: conflicting types for 'ResolutionSetTopology'
resolutionInt.h:81:6: note: previous declaration of 'ResolutionSetTopology' was here
make[3]: *** [libresolutionSet_la-resolutionX11.lo] Error 1
make[3]: Leaving directory `/usr/src/packages/BUILD/open-vm-tools-2010.11.17-327185/services/plugins/resolutionSet'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/packages/BUILD/open-vm-tools-2010.11.17-327185/services/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/packages/BUILD/open-vm-tools-2010.11.17-327185/services'
make: *** [all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.2P199U (%build)


----------------------------------------------------------------------

Comment By: AdmiralNemo (admiralnemo)
Date: 2011-01-14 16:54

Message:
Great, I was just thinking about this yesterday. Hopefully I should have
some time this weekend to test it out. Thanks!

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 16:42

Message:
This is hopefully fixed by commit 4df41ac. Let me know otherwise.

----------------------------------------------------------------------

Comment By: AdmiralNemo (admiralnemo)
Date: 2010-11-25 11:35

Message:
I too am experiencing this exact problem. I am on Gentoo ~amd64, where the
issue has been experienced by a number of users:
http://forums.gentoo.org/viewtopic-p-6493986.html. The conflicting
definitions seem to come from xproto, however, even rolling back to
xproto-7.0.17, which was installed when I last successfully built
open-vm-tools (0.0.20100824.292196) does not solve the issue.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3118268&group_id=204462

[ open-vm-tools-Tracker-3073585 ] Out of memory and high cpu usage

[SourceForge.net <no...@so...>]

Tracker item #3073585, was opened at 2010-09-22 12:40
Message generated for change (Settings changed) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3073585&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: guestd
Group: v1.0 (example)
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Kleber  Rocha (kleberrocha)
Assigned to: Nobody/Anonymous (nobody)
Summary: Out of memory and high cpu usage

Initial Comment:
On Fedora 13 32bits open-vm-tools get all cpu and memory and freeze.

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 14:47

Message:
Without more information about what is going on (i.e., logs), there's
nothing we can do.

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-09-22 14:36

Message:
To try to fix whatever problem you're running into, we'd at least need logs
to know what's going on, since nobody in our internal QA has reported
similar issues. It might be a problem with some patch Fedora may have
applied, but again, without logs it will be really hard to figure out.

I don't generally follow updates for older releases of ESX, so I don't
know how the distro support for ESX 3.5 is looking these days.

----------------------------------------------------------------------

Comment By: Kleber  Rocha (kleberrocha)
Date: 2010-09-22 13:51

Message:
I agree, but the vmware-tools shipped with exx3.5 don't work with fedora, I
turn off the open-vm-tools and the system work fine, what do you recommend?
change fedora or exist other way to work with fedora?

Thanks

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-09-22 13:47

Message:
You really shouldn't be using open-vm-tools in a production environment,
since they're not officially supported by VMware. We always recommend you
use the VMware Tools shipped with your VMware product.

Without any logs it's gonna be hard to know what's going on.

----------------------------------------------------------------------

Comment By: Kleber  Rocha (kleberrocha)
Date: 2010-09-22 13:44

Message:
I use packages from rpmfusion. 
open-vm-tools-libs-0.0.0.243334-1.fc13.i686
open-vm-tools-0.0.0.243334-1.fc13.i686
akmod-open-vm-tools-0.0.0.243334-1.fc13.5.i686
kmod-open-vm-tools-2.6.34.7-56.fc13.i686-0.0.0.243334-1.fc13.17.i686

The version is: 8.4.1.1212 (build-243334)
We use ESX 3.5
The system freeze with kernel panic - Out of memory
The process that get all cpu: is vmtoolsd
No, this machine is production, and I can't stop this system to test with
log.

Thanks

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-09-22 13:33

Message:
There's not enough information here to do anything.

. which version of open-vm-tools are you running?
. which VMware product are you running?
. what does "freeze" mean?
. what's the process that's using all the CPU?
. have you tried to enable logging and see if any useful information shows
up?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3073585&group_id=204462

[ open-vm-tools-Tracker-3110351 ] Doesn't work on openfiler

[SourceForge.net <no...@so...>]

Tracker item #3110351, was opened at 2010-11-16 14:11
Message generated for change (Comment added) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: vmware-user
Group: None
Status: Open
>Resolution: None
Priority: 5
Private: No
Submitted By: Tobias Holst (tobiasholst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Doesn't work on openfiler

Initial Comment:
Hi
I try to use Open VM Tools on Openfiler 2.3.
Kernel version is 2.6.29.6-0.29.smp.gcc3.4.x86_64.
The last working version was open-vm-tools-2010.01.19-226760.
Since then I get errors during "make install".
Configuration is "./configure --without-pam --without-x --without-icu"
open-vm-tools-2010.10.18-313025 can be configured but during "make install" I get the following:

fileLogger.c: In function 'VMFileLoggerOpen':
fileLogger.c:170: warning: implicit declaration of function 'g_atomic_int_set'
make[1]: *** [libvmtools_la-fileLoger.lo] Error 1
make[1]: Leaving directory '/root/open-vm-tools-2010.10.18-313025/libvmtools'
make: *** [install-recursive] Error 1

Greets from Germany
Tobias

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 14:47

Message:
Could you try to configure with "LDFLAGS=-lrt"?

----------------------------------------------------------------------

Comment By: Tobias Holst (tobiasholst)
Date: 2011-01-08 19:43

Message:
Hi

I just tried it with the open-vm-tools 2010.12.19

../lib/misc/.libs/libMisc.a(hostinfoPosix.o): In function
'Hostinfo_SystemTimerNS':
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1647:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1652:
undefined reference to 'clock_gettime'
/root/open-vm-tools-2010.12.19-339835/lib/misc/hostinfoPosix.c:1669:
undefined reference to 'clock_gettime'
collect2: ld returned 1 exit status
make[1]: *** [libvmtools.la] Error 1
make[1]: Leaving directory
'/root/open-vm-tools-2010.12.19-339835/libvmtools'
make: *** [install-recursive] Error 1

Greets Tobias

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2010-12-02 14:12

Message:
This particular issue is fixed but there might be others. I just don't have
a system with a version of glib that old to test on.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3110351&group_id=204462

[ open-vm-tools-Tracker-1813024 ] checkvm compile fails

[SourceForge.net <no...@so...>]

Tracker item #1813024, was opened at 2007-10-13 15:05
Message generated for change (Settings changed) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1813024&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: checkvm
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Heiko Zuerker (smiley73)
Assigned to: Nobody/Anonymous (nobody)
Summary: checkvm compile fails

Initial Comment:
Checkvm fails to compile (see error message below).

./configure --prefix=/usr --disable-multimon --without-x
make LDFLAGS=-liconv all

Unfortunately upgrading to a newer gcc is at the moment not possible.

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----------------------------------
gcc -v
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.2/specs
Configured with: ../gcc-3.3.2/configure --prefix=/usr --localstatedir=/var
--enable-shared --enable-CONFIG_SHELL=/bin/bash --enable-threads=posix
--with-slibdir=/lib --enable-__cxa_atexit --enable-clocale=gnu
--enable-languages=c,c++,objc --disable-nls i586-pc-linux-gnu
Thread model: posix
gcc version 3.3.2
-----------------------------------
ld -v
GNU ld version 2.16.1
-----------------------------------
glibc 2.3.2
-----------------------------------
[ cut the stuff with worked ]
make[1]: Entering directory
`/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/checkvm'
gcc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\"
-DPACKAGE_VERSION=\"2007.10.08-SNAPSHOT\"
-DPACKAGE_STRING=\"open-vm-tools\ 2007.10.08-SNAPSHOT\"
-DPACKAGE_BUGREPORT=\"ope...@li...\"
-DPACKAGE=\"open-vm-tools\" -DVERSION=\"2007.10.08-SNAPSHOT\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DX_DISPLAY_MISSING=1 -DHAVE_ECVT=1 -DHAVE_FCVT=1 -DHAVE_WCHAR_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_CRYPT_H=1 -DHAVE_SYS_IO_H=1
-DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE__BOOL=1
-DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1
-DHAVE_LSEEK=1 -DNO_MULTIMON=1 -I.    -Wall -Werror -Wno-unknown-pragmas
-Wno-uninitialized -fno-strict-aliasing -Wno-unused-value -DVMX86_TOOLS
-I/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/lib/include
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -DUSING_AUTOCONF=1 -MT checkvm.o -MD -MP -MF
.deps/checkvm.Tpo -c -o checkvm.o checkvm.c
checkvm.c: In function `getVersion':
checkvm.c:80: error: can't find a register in class `BREG' while reloading
`asm'
make[1]: *** [checkvm.o] Error 1
make[1]: Leaving directory
`/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/checkvm'
make: *** [all-recursive] Error 1

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2011-01-14 14:44

Message:
Commit bb7a78 should fix this.

----------------------------------------------------------------------

Comment By: No Name (archwyvern)
Date: 2009-11-14 15:32

Message:
Patch available @ http://bugs.gentoo.org/show_bug.cgi?id=200376 in comment
#49.

----------------------------------------------------------------------

Comment By: Adar Dembo (adembo)
Date: 2008-11-24 02:32

Message:
Mike, we haven't added -nopie upstream, but enough people have complained
about this (here and in the Gentoo bug report) that we should look into
doing just that, or look at changing the affected checkvm.c code. I'll
reopen this bug.

For those seeing this bug report for the first time, there's a lot more
information available at the associated Gentoo bug report, which can be
found here: http://bugs.gentoo.org/show_bug.cgi?id=200376


----------------------------------------------------------------------

Comment By: Mike Auty (ikelos)
Date: 2007-11-26 11:04

Message:
Logged In: YES 
user_id=230582
Originator: NO

Sorry to check on this, but does that mean that -nopie has been added to
the CFLAGS in the Makefile, or could other users still run into this
problem?  If it has been added, is it enabled at all times, or just when
being built against a hardened config?  Certainly for the Gentoo
distribution we can add in a Makefile patch, I just would have thought it
more beneficial to have a solid fix upstream...

----------------------------------------------------------------------

Comment By: ECL (sopwith)
Date: 2007-11-26 10:38

Message:
Logged In: YES 
user_id=18318
Originator: NO

Closing as "WORKSFORME"...

----------------------------------------------------------------------

Comment By: Heiko Zuerker (smiley73)
Date: 2007-11-26 09:23

Message:
Logged In: YES 
user_id=112133
Originator: YES

Hey,

I ended up using this to get the compile running:
CC="gcc -U_FORTIFY_SOURCE -fno-PIE" LDFLAGS=-liconv ./configure
--prefix=/usr --without-x
make all modules

-U_FORTIFY_SOURCE was necessary because there are a lot of compiler
warnings and we treat warnings as errors.
-fno-PIE was necessary because of the error in the original support
request.

It may be required on hardened systems in general.
Devil-Linux uses the hardened settings from "Hardened Linux from Scratch",
which may be the base or similar to other hardened distros.

Heiko


----------------------------------------------------------------------

Comment By: Mike Auty (ikelos)
Date: 2007-11-26 04:24

Message:
Logged In: YES 
user_id=230582
Originator: NO

Hiya, we've had a report of one of our users patching the Makefile in
checkvm to include I tried to CFLAGS+="-nopie" and this appears to solve
the problem.  It would be nice to find a way of only enabling this if
required...

----------------------------------------------------------------------

Comment By: Heiko Zuerker (smiley73)
Date: 2007-10-16 14:06

Message:
Logged In: YES 
user_id=112133
Originator: YES

I hate to admit it, but the problem seems to be Devil-Linux specific.
I disabled all security features and now it compiles fine.
I'm not sure where the problem is, this may take quite some time to figure
it out. It may be SSP or PIE related.

If you want you can close this tracker.

Heiko

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1813024&group_id=204462