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

[ open-vm-tools-Tracker-3523224 ] open-vm-tools cannot compile against Glibc >2.14 and TI-RPC

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

Tracker item #3523224, was opened at 2012-05-03 04:48
Message generated for change (Comment added) made by nosebleedkt
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3523224&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: misc
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: nosebleedkt (nosebleedkt)
Assigned to: Nobody/Anonymous (nobody)
Summary: open-vm-tools cannot compile against Glibc >2.14 and TI-RPC

Initial Comment:
Hello everybody !
Well my system is a linux-2.6.35.14 / gcc 4.7.0 / Glibc 2.14.1 / TI-RPC 0.2.2

Inside source tree I type: 
open-vm-tools-8.6.0-425873/# ./configure --prefix=/usr --without-x --without-dnet --without-icu --without-gtk2
Everything OK.

Then I type make. After a while I get multiple 'undefined reference to xdr...'
This is normal as open-vm-tools think that RPC implementation is still in Glibc project.
However, after Glibc >2.14 the RPC implementation has been removed and it is now in a another project called TI-RPC which resided on
http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php .

Me going  one level further, I run ./configure LIBS="-ltirpc" --prefix=/usr --without-x --without-dnet --without-icu --without-gtk2
Now, open-vm-tools know where to find the xdr references so things get a lot better. 
But still, 'make' exits with just one error: lib/include/vmxrpc.h:190: undefined reference to xdr_uint32_t.

So, I kindly ask the developers to make open-vm-tools compile against TI-RPC. 

Thanks :)

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

>Comment By: nosebleedkt (nosebleedkt)
Date: 2012-05-04 06:58

Message:
Well, I found a workaround until a proper update is done in the official
sources.

Comment out the 3 defines at the beggining of lib/include/vmxrpc.h .
Then run configure with LIBS="-ltirpc"
CFLAGS="-Wno-implicit-function-declaration"

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

Comment By: nosebleedkt (nosebleedkt)
Date: 2012-05-03 05:11

Message:
In addition, running #strings /lib/libtirpc.so | grep xdr_u_int32_t 
returns me xdr_u_int32_t . That's weird.

And the complete error from 'make' is 

../lib/guestRpc/.libs/libGuestRpc.a(nicinfo_xdr.o): In function
`xdr_uint32':
/root/open-vm-tools-8.6.0-425873/lib/include/vmxrpc.h:190: undefined
reference to `xdr_uint32_t'
/root/open-vm-tools-8.6.0-425873/lib/include/vmxrpc.h:190: undefined
reference to `xdr_uint32_t'
collect2: error: ld returned 1 exit status
make[1]: *** [libvmtools.la] Error 1
make[1]: Leaving directory `/root/open-vm-tools-8.6.0-425873/libvmtools'
make: *** [all-recursive] Error 1



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

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

[ open-vm-tools-Tracker-3523224 ] open-vm-tools cannot compile against Glibc >2.14 and TI-RPC

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

Tracker item #3523224, was opened at 2012-05-03 04:48
Message generated for change (Comment added) made by nosebleedkt
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3523224&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: misc
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: nosebleedkt (nosebleedkt)
Assigned to: Nobody/Anonymous (nobody)
Summary: open-vm-tools cannot compile against Glibc >2.14 and TI-RPC

Initial Comment:
Hello everybody !
Well my system is a linux-2.6.35.14 / gcc 4.7.0 / Glibc 2.14.1 / TI-RPC 0.2.2

Inside source tree I type: 
open-vm-tools-8.6.0-425873/# ./configure --prefix=/usr --without-x --without-dnet --without-icu --without-gtk2
Everything OK.

Then I type make. After a while I get multiple 'undefined reference to xdr...'
This is normal as open-vm-tools think that RPC implementation is still in Glibc project.
However, after Glibc >2.14 the RPC implementation has been removed and it is now in a another project called TI-RPC which resided on
http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php .

Me going  one level further, I run ./configure LIBS="-ltirpc" --prefix=/usr --without-x --without-dnet --without-icu --without-gtk2
Now, open-vm-tools know where to find the xdr references so things get a lot better. 
But still, 'make' exits with just one error: lib/include/vmxrpc.h:190: undefined reference to xdr_uint32_t.

So, I kindly ask the developers to make open-vm-tools compile against TI-RPC. 

Thanks :)

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

>Comment By: nosebleedkt (nosebleedkt)
Date: 2012-05-03 05:11

Message:
In addition, running #strings /lib/libtirpc.so | grep xdr_u_int32_t 
returns me xdr_u_int32_t . That's weird.

And the complete error from 'make' is 

../lib/guestRpc/.libs/libGuestRpc.a(nicinfo_xdr.o): In function
`xdr_uint32':
/root/open-vm-tools-8.6.0-425873/lib/include/vmxrpc.h:190: undefined
reference to `xdr_uint32_t'
/root/open-vm-tools-8.6.0-425873/lib/include/vmxrpc.h:190: undefined
reference to `xdr_uint32_t'
collect2: error: ld returned 1 exit status
make[1]: *** [libvmtools.la] Error 1
make[1]: Leaving directory `/root/open-vm-tools-8.6.0-425873/libvmtools'
make: *** [all-recursive] Error 1



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

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

[ open-vm-tools-Tracker-3519354 ] vmware-pvscsi.modules Bad interpreter: No such file or direc

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

Tracker item #3519354, was opened at 2012-04-18 19:19
Message generated for change (Tracker Item Submitted) made by leonkyne
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3519354&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: OSP
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Leon (leonkyne)
Assigned to: Nobody/Anonymous (nobody)
Summary: vmware-pvscsi.modules Bad interpreter: No such file or direc

Initial Comment:
HI,

We are using the OSP package on CentOS 5 - on bootup we get an error when udev starts:
"/etc/sysconfig/modules/vmware-pvcsci.modules: /usr/bin/env: bad interpretor: No such file or directory"

We remove the contents of /etc/sysconfig/modules/vmware-pvcsci.modules and this removes the error.

screenshot attached.



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

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

Re: Show IP addresses in the VM Summary

[Stanislav <ste...@ci...>]

On 3/30/2012 8:23 PM, Dmitry Torokhov wrote:
> On Friday, March 30, 2012 03:22:46 PM Stanislav wrote:
>> Hello,
>>
>> When we compile open-vmtools without dnet how it can determine
>> information about IP addresses for Guest OS? I see that it can show this
>> info in the VM Summary for my VM on ESXi4.1 but don't understand how it
>> works in the code.
> Please take a look at services/plugins/guestInfo/, particularly
> guestInfoServer.c, guestInfoPosix.c and GuestInfo_GetNicInfo(),
> GuestInfoGetNicInfo().
>
> If you do not want to use libdnet you'll have to collect the data from your
> systems by other means and format it exactly like the current code does it for
> libdnet data.
>
> Hope this helps.
>
OK, thanks. Let me explain the problem.

For our system we use our special mechanism to save IP addresses and 
retrieve it in the libguestinfo plugin(by replacing 
GuestInfo_GetNicInfo() function to our function). It works in some 
cases, but we see some strange thing when it does not work.

So, I'm started my investigation and walk through the open-vmtools code. 
I've download fresh tarball(8.6), compile it  without dnet, without 
kernel modules, without x and some other features. I'm using regular 
ubuntu for testing this binaries and see that IP can be shown without 
using dnet or some other mechanism. It's very strange. 
GuestInfoGetNicInfo() has #ifndef NO_DNET and I don't use dnet. So, this 
function does not work. And my question is how it works if we don't have 
dnet and special kernel modules?

-- 
Stas

Re: Show IP addresses in the VM Summary

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

On Friday, March 30, 2012 03:22:46 PM Stanislav wrote:
> Hello,
> 
> When we compile open-vmtools without dnet how it can determine
> information about IP addresses for Guest OS? I see that it can show this
> info in the VM Summary for my VM on ESXi4.1 but don't understand how it
> works in the code.

Please take a look at services/plugins/guestInfo/, particularly 
guestInfoServer.c, guestInfoPosix.c and GuestInfo_GetNicInfo(), 
GuestInfoGetNicInfo().

If you do not want to use libdnet you'll have to collect the data from your 
systems by other means and format it exactly like the current code does it for 
libdnet data.

Hope this helps.

-- 
Dmitry

Re: Show IP addresses in the VM Summary

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

On Friday, March 30, 2012 01:41:59 PM Reindl Harald wrote:
> Am 30.03.2012 13:22, schrieb Stanislav:
> > Hello,
> > 
> > When we compile open-vmtools without dnet how it can determine
> > information about IP addresses for Guest OS? I see that it can show this
> > info in the VM Summary for my VM on ESXi4.1 but don't understand how it
> > works in the code.
> 
> wild guess: VMCI
> 
> http://pubs.vmware.com/vmci-sdk/index.html

You can't (at least for now) use VMCI from userspace, you'd need to use vsock 
for that; but using vsock would require additional sofware receiving data on 
the other side. I does not appear that that's what Stanislav is looking for 
...

-- 
Dmitry

Re: Usage of vmware-toolbox-cmd

[Stanislav <ste...@ci...>]

On 3/30/2012 3:52 PM, Reindl Harald wrote:
>
> Am 30.03.2012 13:48, schrieb Stanislav:
>> On 3/30/2012 3:41 PM, Reindl Harald wrote:
>>> Am 30.03.2012 13:11, schrieb Stanislav:
>>>> Hello,
>>>>
>>>> I have a question about "vmware-toolbox-cmd". When I run it in the Guest OS(linux) I see:
>>>> root@ubuntu-console:~# /usr/local/bin/vmware-toolbox-cmd stat memlimit          4294967295 MB
>>>> What does it mean? When I change memory allocated for VM I don't see that this value changed. This is for ESXi 4.1.
>>> this is not the allocated memory of the VM (RAM)
>>> this is the LIMIT which can be lower to partly
>>> force memory get ballooned or even compressed
>>>
>>> look for "ressource limits" in the viclient
>>> these can be changed at runtime also in viclient
>>> assigned memory itself usually not (depends on license and guest-OS)
>>>
>> Thanks!
>>
>> And how can I get amount of allocated memory in runtime? When I use "cat
>> /proc/meminfo" in the Guest OS it shows lower values that I set in the
>> viclient for VM
> BTW: you are aware that this is a devel-list?
>
>
> free -m
>
> the guest has 8500 MB RAm allocated
> the rest is kernel assigned memory
>
>               total       used       free     shared    buffers     cached
> Mem:          8289       7913        376          0        605       3389
> -/+ buffers/cache:       3918       4371
> Swap:          511          0        511
>
> ________________________________________
>
> there is nothing different on physical machines
> below my workstation with 16 GB RAM
>
>               total       used       free     shared    buffers     cached
> Mem:         15939      15718        220          0        234      13241
> -/+ buffers/cache:       2242      13696
> Swap:         2047          2       2045
>
>
>
Sorry for that. I thought that there are some methods in the code how 
can I determine actual amount of memory, like in the viclient. Any way, 
thank you for your effort.

-- 
Stas

Re: Usage of vmware-toolbox-cmd

[Reindl H. <h.r...@th...>]

Am 30.03.2012 13:48, schrieb Stanislav:
> On 3/30/2012 3:41 PM, Reindl Harald wrote:
>>
>> Am 30.03.2012 13:11, schrieb Stanislav:
>>> Hello,
>>>
>>> I have a question about "vmware-toolbox-cmd". When I run it in the Guest OS(linux) I see:
>>> root@ubuntu-console:~# /usr/local/bin/vmware-toolbox-cmd stat memlimit          4294967295 MB
>>> What does it mean? When I change memory allocated for VM I don't see that this value changed. This is for ESXi 4.1.
>> this is not the allocated memory of the VM (RAM)
>> this is the LIMIT which can be lower to partly
>> force memory get ballooned or even compressed
>>
>> look for "ressource limits" in the viclient
>> these can be changed at runtime also in viclient
>> assigned memory itself usually not (depends on license and guest-OS)
>>
> Thanks!
> 
> And how can I get amount of allocated memory in runtime? When I use "cat 
> /proc/meminfo" in the Guest OS it shows lower values that I set in the 
> viclient for VM

BTW: you are aware that this is a devel-list?


free -m

the guest has 8500 MB RAm allocated
the rest is kernel assigned memory

             total       used       free     shared    buffers     cached
Mem:          8289       7913        376          0        605       3389
-/+ buffers/cache:       3918       4371
Swap:          511          0        511

________________________________________

there is nothing different on physical machines
below my workstation with 16 GB RAM

             total       used       free     shared    buffers     cached
Mem:         15939      15718        220          0        234      13241
-/+ buffers/cache:       2242      13696
Swap:         2047          2       2045

Re: Usage of vmware-toolbox-cmd

[Stanislav <ste...@ci...>]

On 3/30/2012 3:41 PM, Reindl Harald wrote:
>
> Am 30.03.2012 13:11, schrieb Stanislav:
>> Hello,
>>
>> I have a question about "vmware-toolbox-cmd". When I run it in the Guest OS(linux) I see:
>> root@ubuntu-console:~# /usr/local/bin/vmware-toolbox-cmd stat memlimit          4294967295 MB
>> What does it mean? When I change memory allocated for VM I don't see that this value changed. This is for ESXi 4.1.
> this is not the allocated memory of the VM (RAM)
> this is the LIMIT which can be lower to partly
> force memory get ballooned or even compressed
>
> look for "ressource limits" in the viclient
> these can be changed at runtime also in viclient
> assigned memory itself usually not (depends on license and guest-OS)
>
Thanks!

And how can I get amount of allocated memory in runtime? When I use "cat 
/proc/meminfo" in the Guest OS it shows lower values that I set in the 
viclient for VM.

-- 
Stas

Re: Show IP addresses in the VM Summary

[Reindl H. <h.r...@th...>]

Am 30.03.2012 13:22, schrieb Stanislav:
> Hello,
> 
> When we compile open-vmtools without dnet how it can determine 
> information about IP addresses for Guest OS? I see that it can show this 
> info in the VM Summary for my VM on ESXi4.1 but don't understand how it 
> works in the code.

wild guess: VMCI

http://pubs.vmware.com/vmci-sdk/index.html

Re: Usage of vmware-toolbox-cmd

[Reindl H. <h.r...@th...>]

Am 30.03.2012 13:11, schrieb Stanislav:
> Hello,
> 
> I have a question about "vmware-toolbox-cmd". When I run it in the Guest OS(linux) I see:
> root@ubuntu-console:~# /usr/local/bin/vmware-toolbox-cmd stat memlimit          4294967295 MB
> What does it mean? When I change memory allocated for VM I don't see that this value changed. This is for ESXi 4.1.

this is not the allocated memory of the VM (RAM)
this is the LIMIT which can be lower to partly
force memory get ballooned or even compressed

look for "ressource limits" in the viclient
these can be changed at runtime also in viclient
assigned memory itself usually not (depends on license and guest-OS)

Show IP addresses in the VM Summary

[Stanislav <ste...@ci...>]

Hello,

When we compile open-vmtools without dnet how it can determine 
information about IP addresses for Guest OS? I see that it can show this 
info in the VM Summary for my VM on ESXi4.1 but don't understand how it 
works in the code.

-- 
Stas

Usage of vmware-toolbox-cmd

[Stanislav <ste...@ci...>]

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO8859_1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hello,<br>
    <br>
    I have a question about "<font face="Calibri, Verdana, Helvetica,
      Arial"><span style="font-size:11pt">vmware-toolbox-cmd</span></font>".
    When I run it in the Guest OS(linux) I see:<br>
    root@ubuntu-console:~# /usr/local/bin/vmware-toolbox-cmd stat
    memlimit          4294967295 MB<br>
    What does it mean? When I change memory allocated for VM I don't see
    that this value changed. This is for ESXi 4.1. <br>
    <br>
    So, we just need to get allocated VM memory in the Guest OS. Is it
    possible?<br>
    <br>
    Additional info:<br>
    root@ubuntu-console:~# uname -a<br>
    Linux ubuntu-console 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7
    14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux<br>
    root@ubuntu-console:~# free<br>
                 total       used       free     shared    buffers    
    cached<br>
    Mem:        504444     150540     353904          0      24328     
    63288<br>
    -/+ buffers/cache:      62924     441520<br>
    Swap:            0          0          0<br>
    <br>
    In the vSphere client I set 512Mb for this VM.<br>
    <pre class="moz-signature" cols="72">-- 
Stas</pre>
  </body>
</html>

Re: A lot of questions about vmtools

[Stanislav <ste...@ci...>]

On 3/22/2012 10:09 AM, Stanislav wrote:
> On 3/21/2012 8:42 PM, Dmitry Torokhov wrote:
>> On Wednesday, March 21, 2012 08:32:55 PM Stanislav wrote:
>>> For one ESX I see that it works. For another(the same version and build) -
>>> doesn't work. But for the second one - I can set IP by running: "vmtoolsd
>>> --cmd "info-set guestinfo.ip 1.1.1.1" and it is shown in Summary as well.
>>> But after some time I see it disappeared because vmtoolsd is running in
>>> parallel in background(as I understand it's a polling timeout). It looks
>>> like at the first one - vmtoolsd can update nicInfo and hostname. And for
>>> another one - it can't update nicInfo but can update hostname
>>> automatically.
>> Is this the with the same VM running on the 2 hosts or are there different
>> VMs? What are the guest OSes and how are NICs configured?
>>
>> Thanks,
>> Dmitry
>>
>>
> I'm talking about two different VMs on two different ESXs(the same
> versions and build number). I'm running WindRiver Linux with changed
> open-vmtools. I've changed IP retrieving mechanism to do it
> directly(don't use usual IOCTLs). I mean I've added function to save
> what we need in the struct nicInfo. After that it works like usual, i.e.
> send this struct to GuestInfoUpdateVmdb. It works fine for one VM, I can
> see the full list in Summary tab. But for another VM - I don't. I'm
> trying to understand differences but see that VMX files are the same.
> It's very strange.
>
I've found that if we have more than 4 ethernet devices on the VM it 
works fine. But if we have 3 and less - it doesn't work. It's very 
interesting.

-- 
Stas

Re: A lot of questions about vmtools

[Stanislav <ste...@ci...>]

On 3/21/2012 8:42 PM, Dmitry Torokhov wrote:
> On Wednesday, March 21, 2012 08:32:55 PM Stanislav wrote:
>> For one ESX I see that it works. For another(the same version and build) -
>> doesn't work. But for the second one - I can set IP by running: "vmtoolsd
>> --cmd "info-set guestinfo.ip 1.1.1.1" and it is shown in Summary as well.
>> But after some time I see it disappeared because vmtoolsd is running in
>> parallel in background(as I understand it's a polling timeout). It looks
>> like at the first one - vmtoolsd can update nicInfo and hostname. And for
>> another one - it can't update nicInfo but can update hostname
>> automatically.
> Is this the with the same VM running on the 2 hosts or are there different
> VMs? What are the guest OSes and how are NICs configured?
>
> Thanks,
> Dmitry
>
>
I'm talking about two different VMs on two different ESXs(the same 
versions and build number). I'm running WindRiver Linux with changed 
open-vmtools. I've changed IP retrieving mechanism to do it 
directly(don't use usual IOCTLs). I mean I've added function to save 
what we need in the struct nicInfo. After that it works like usual, i.e. 
send this struct to GuestInfoUpdateVmdb. It works fine for one VM, I can 
see the full list in Summary tab. But for another VM - I don't. I'm 
trying to understand differences but see that VMX files are the same. 
It's very strange.

-- 
Stas

Re: A lot of questions about vmtools

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

On Wednesday, March 21, 2012 08:32:55 PM Stanislav wrote:
> 
> For one ESX I see that it works. For another(the same version and build) -
> doesn't work. But for the second one - I can set IP by running: "vmtoolsd
> --cmd "info-set guestinfo.ip 1.1.1.1" and it is shown in Summary as well.
> But after some time I see it disappeared because vmtoolsd is running in
> parallel in background(as I understand it's a polling timeout). It looks
> like at the first one - vmtoolsd can update nicInfo and hostname. And for
> another one - it can't update nicInfo but can update hostname
> automatically.

Is this the with the same VM running on the 2 hosts or are there different 
VMs? What are the guest OSes and how are NICs configured?

Thanks,
Dmitry

Re: A lot of questions about vmtools

[Stanislav <ste...@ci...>]

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Dmitry,<br>
    <br>
    On 3/21/2012 8:19 PM, Dmitry Torokhov wrote:
    <blockquote cite="mid:378...@dt..."
      type="cite">
      <pre wrap="">Hi Stanislav,

On Wednesday, March 21, 2012 06:10:43 PM Stanislav wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi,

I have some questions. It will be very helpfull to understand how it should
work because I can't find answers in the documentation.

First one is about vmware-checkvm. For the vSphere Client 4.1 with ESXi 4.1
I see in the VMX file: virtualHW.version = "7"
config.version = "8"

And for this VM in Summary I see:
VM version: 7

But in the guest OS with installed open-vmtools I see:
Linux(debug)# vmware-checkvm -h
VM's hw version is 4
VMware software version 6 (good)

Can someone explain situation with this versions? What does it mean?
</pre>
      </blockquote>
      <pre wrap="">
The platform (ESX, WS) does not report true HW version to the guest; do not 
pay attention to the number reported by checkvm.

The "software version" returned will be 6 unless something really drastic 
happens.

</pre>
      <blockquote type="cite">
        <pre wrap="">

Second question is about disabling features in the vSphere Client like "send
ctrl+alt+del" or "install vmtools". Can we hide or disable this fields? I
see some fields already grayed out.
</pre>
      </blockquote>
      <pre wrap="">
That would be a question for the client folks, you better ask through normal 
support channels.

</pre>
      <blockquote type="cite">
        <pre wrap="">

Third question is about showing IP addresses in the Summary tab.
If we use vSphere Client 4.1 with ESXi 4.1 it works fine and we can see IP
addresses assigned in the guest OS. But for vCenter 4.1/5.0 with ESXi 4.1
we don't see it. And for vCenter 5.0 with ESXi 5.0 we can see it again.

Are there any differences between versions in case Summary tab and updating
guest info by plugin(libguestInfo.so)?
</pre>
      </blockquote>
      <pre wrap="">
Is the difference only with open-vm-tools or with tolls shipped with product 
as well?</pre>
    </blockquote>
    We are using open-vmtools always. I'm trying to investigate this
    issue and don't understand the difference.<br>
    <br>
    For one ESX I see that it works. For another(the same version and
    build) - doesn't work. But for the second one - I can set IP by
    running: "<span class="st"><em>vmtoolsd</em> --cmd "<wbr>info-set <em>guestinfo.ip
        1.1.1.1</em></span>" and it is shown in Summary as well. But
    after some time I see it disappeared because vmtoolsd is running in
    parallel in background(as I understand it's a polling timeout). It
    looks like at the first one - vmtoolsd can update nicInfo and
    hostname. And for another one - it can't update nicInfo but can
    update hostname automatically.<br>
    <blockquote cite="mid:378...@dt..."
      type="cite">
      <pre wrap="">

Thanks,
Dmitry


</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Stas</pre>
  </body>
</html>

Re: A lot of questions about vmtools

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

Hi Stanislav,

On Wednesday, March 21, 2012 06:10:43 PM Stanislav wrote:
> Hi,
> 
> I have some questions. It will be very helpfull to understand how it should
> work because I can't find answers in the documentation.
> 
> First one is about vmware-checkvm. For the vSphere Client 4.1 with ESXi 4.1
> I see in the VMX file: virtualHW.version = "7"
> config.version = "8"
> 
> And for this VM in Summary I see:
> VM version: 7
> 
> But in the guest OS with installed open-vmtools I see:
> Linux(debug)# vmware-checkvm -h
> VM's hw version is 4
> VMware software version 6 (good)
> 
> Can someone explain situation with this versions? What does it mean?

The platform (ESX, WS) does not report true HW version to the guest; do not 
pay attention to the number reported by checkvm.

The "software version" returned will be 6 unless something really drastic 
happens.

> 
> 
> Second question is about disabling features in the vSphere Client like "send
> ctrl+alt+del" or "install vmtools". Can we hide or disable this fields? I
> see some fields already grayed out.

That would be a question for the client folks, you better ask through normal 
support channels.

> 
> 
> Third question is about showing IP addresses in the Summary tab.
> If we use vSphere Client 4.1 with ESXi 4.1 it works fine and we can see IP
> addresses assigned in the guest OS. But for vCenter 4.1/5.0 with ESXi 4.1
> we don't see it. And for vCenter 5.0 with ESXi 5.0 we can see it again.
> 
> Are there any differences between versions in case Summary tab and updating
> guest info by plugin(libguestInfo.so)?

Is the difference only with open-vm-tools or with tolls shipped with product 
as well?

Thanks,
Dmitry

A lot of questions about vmtools

[Stanislav <ste...@ci...>]

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    I have some questions. It will be very helpfull to understand how it
    should work because I can't find answers in the documentation.<br>
    <br>
    First one is about vmware-checkvm. For the vSphere Client 4.1 with
    ESXi 4.1 I see in the VMX file: <br>
    virtualHW.version = "7"<br>
    config.version = "8"<br>
    <br>
    And for this VM in Summary I see: <br>
    VM version: 7<br>
    <br>
    But in the guest OS with installed open-vmtools I see:<br>
    Linux(debug)# vmware-checkvm -h<br>
    VM's hw version is 4<br>
    VMware software version 6 (good)<br>
    <br>
    Can someone explain situation with this versions? What does it mean?<br>
    <br>
    <br>
    Second question is about disabling features in the vSphere Client
    like "send ctrl+alt+del" or "install vmtools". Can we hide or
    disable this fields? I see some fields already grayed out.<br>
    <br>
    <br>
    Third question is about showing IP addresses in the Summary tab. <br>
    If we use vSphere Client 4.1 with ESXi 4.1 it works fine and we can
    see IP addresses assigned in the guest OS. But for vCenter 4.1/5.0
    with ESXi 4.1 we don't see it. And for vCenter 5.0 with ESXi 5.0 we
    can see it again.<br>
    <br>
    Are there any differences between versions in case Summary tab and
    updating guest info by plugin(libguestInfo.so)?<br>
    <pre class="moz-signature" cols="72">-- 
Stas</pre>
    <div style="bottom: auto; left: 1177px; right: auto; top: 465px;"
      class="translator-theme-default" id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

Transferring debugging data between VMware guest OS and host OS

[tudor c. <tud...@gm...>]

Hello,

I am trying to write a Linux kernel module, that captures kernel
debugging information from a VMware guest OS, and sends it to the host
OS, using
some native VMware mechanisms like VMCI Sockets, for example.

After downloading the open-vm-tools source code, and browsing trough
it, it seems that what I need my kernel module to do, is to
communicate directly with the underlying VMCI driver.
Vmci Sockets[1] seemed as a good start, but it has the problem of
being a user-space API, whereas I need lower-level functionalities.

I would appreciate some advice regarding the best way to transfer the
debugging data between the guest and host OS, at device driver level.
I would also like to know which components from open-vm-tools would I
need to use, in order to build my module.

Tudor

[1].http://www.vmware.com/support/developer/vmci-sdk/

Re: 2012.03.13-651368: warnings after compile

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

Hi Reindl,

On Saturday, March 17, 2012 08:40:33 PM Reindl Harald wrote:
> * open-vm-tools-2012.03.13-651368.tar.gz
> * kernel 3.2.10-3.fc16.x86_64
> 
> here are some warnings from rpmbuild
> 
> as far as i can see all is working fine including HA/VDR-Backup on
> ESXi 4.1, but however in my opinion this needs to be fixed since
> we are speaking about software running in kernel-space
> 
> WARNING: "VMCIDatagram_CreateHnd"
> [/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linu
> x/vsock/vsock.ko] undefined! WARNING: "VMCIDatagram_DestroyHnd"
> [/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linu
> x/vsock/vsock.ko] undefined! WARNING: "VMCIEvent_Subscribe"
> [/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linu
> x/vsock/vsock.ko] undefined! WARNING: "VMCIQPair_ProduceBufReady"

I do not see these warnings when I do "./configure && make && make install". 
The warnings are most likely coming from 'depmod' in your rpm build script.

Thanks,
Dmitry

Re: Simple question

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

On Friday, March 16, 2012 02:58:50 PM Stanislav wrote:
> On 3/16/2012 12:10 PM, Dmitry Torokhov wrote:
> > On Friday, March 16, 2012 10:43:19 AM Stanislav wrote:
> >> On 3/16/2012 9:42 AM, Dmitry Torokhov wrote:
> >>> On Thu, Mar 15, 2012 at 08:53:43PM +0400, Stanislav wrote:
> >>>> Thanks a lot.
> >>>> 
> >>>> Next simple question from my side. I wanted to use scripts before
> >>>> and after snapshot creation, but see that there is no RPC messages
> >>>> from ESX(WS) to VMTools(and no any actions in the scripts). Does it
> >>>> work fine for others? Maybe there are some tricks?
> >>> 
> >>> What scripts/snapshots are you talking about? Are you trying to set up
> >>> VCB or just regular VM snapshots?
> >>> 
> >>> Thanks,
> >>> Dmitry
> >> 
> >> I'm talking about regular VM snapshot, scripts:
> >> /usr/sbin/pre-freeze-script and /usr/sbin/post-thaw-script
> > 
> > Regular snapshots are transparent to the VM and no scripts are being
> > invoked. The pre-freeze-script and post-thaw-script are being invoked y
> > vmbackup plugin when doing a VCB snapshot.
> > 
> > Thanks,
> > Dmitry
> 
> Dmitry, yes, sorry, my mistake. I meant VCB and vmbackup plugin.

Stanislav,

You should have gotten the answer already from Paul (he mentioned you were on 
the thread) but for the benefit of others following the thread:

If you have "Snapshot the virtual machine's memory" box checked when you take 
the snapshot we will not invoke vmbackup plugin and therefore will not execute 
pre-freeze and post-thaw scripts as there is no point in quescing the 
filesystems - we are talking a full snapshot of the system, including all the 
operations that are currently in progress.

You need to quesce filesystems if you are not saving contents of VM memory so 
that the data being backed up is in consistent state should you need to 
restore it.

Thanks,
Dmitry

2012.03.13-651368: warnings after compile

[Reindl H. <h.r...@th...>]

* open-vm-tools-2012.03.13-651368.tar.gz
* kernel 3.2.10-3.fc16.x86_64

here are some warnings from rpmbuild

as far as i can see all is working fine including HA/VDR-Backup on
ESXi 4.1, but however in my opinion this needs to be fixed since
we are speaking about software running in kernel-space

WARNING: "VMCIDatagram_CreateHnd"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ProduceBufReady"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_DequeueV"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_EnqueueV"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_DeviceRelease"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_GetConsumeIndexes"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_PeekV"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_Detach"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIDatagram_CreateHndPriv"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_GetProduceIndexes"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ProduceFreeSpace"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_Alloc"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIContext_GetPrivFlags"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ConsumeBufReady"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ConsumeFreeSpace"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_GetContextID"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_IsContextOwner"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2012.03.13-651368/modules/linux/vsock/vsock.ko] undefined!

Re: Simple question

[Stanislav <ste...@ci...>]

On 3/16/2012 12:10 PM, Dmitry Torokhov wrote:
> On Friday, March 16, 2012 10:43:19 AM Stanislav wrote:
>> On 3/16/2012 9:42 AM, Dmitry Torokhov wrote:
>>> On Thu, Mar 15, 2012 at 08:53:43PM +0400, Stanislav wrote:
>>>> Thanks a lot.
>>>>
>>>> Next simple question from my side. I wanted to use scripts before
>>>> and after snapshot creation, but see that there is no RPC messages
>>>> from ESX(WS) to VMTools(and no any actions in the scripts). Does it
>>>> work fine for others? Maybe there are some tricks?
>>> What scripts/snapshots are you talking about? Are you trying to set up
>>> VCB or just regular VM snapshots?
>>>
>>> Thanks,
>>> Dmitry
>> I'm talking about regular VM snapshot, scripts:
>> /usr/sbin/pre-freeze-script and /usr/sbin/post-thaw-script
> Regular snapshots are transparent to the VM and no scripts are being invoked.
> The pre-freeze-script and post-thaw-script are being invoked y vmbackup plugin
> when doing a VCB snapshot.
>
> Thanks,
> Dmitry
>
Dmitry, yes, sorry, my mistake. I meant VCB and vmbackup plugin.

-- 
Stas

Re: Simple question

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

On Friday, March 16, 2012 10:43:19 AM Stanislav wrote:
> On 3/16/2012 9:42 AM, Dmitry Torokhov wrote:
> > On Thu, Mar 15, 2012 at 08:53:43PM +0400, Stanislav wrote:
> >> Thanks a lot.
> >> 
> >> Next simple question from my side. I wanted to use scripts before
> >> and after snapshot creation, but see that there is no RPC messages
> >> from ESX(WS) to VMTools(and no any actions in the scripts). Does it
> >> work fine for others? Maybe there are some tricks?
> > 
> > What scripts/snapshots are you talking about? Are you trying to set up
> > VCB or just regular VM snapshots?
> > 
> > Thanks,
> > Dmitry
> 
> I'm talking about regular VM snapshot, scripts:
> /usr/sbin/pre-freeze-script and /usr/sbin/post-thaw-script

Regular snapshots are transparent to the VM and no scripts are being invoked. 
The pre-freeze-script and post-thaw-script are being invoked y vmbackup plugin 
when doing a VCB snapshot.

Thanks,
Dmitry