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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1841558 ] "configure" reports wrong reasons of failures

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

Tracker item #1841558, was opened at 2007-11-30 12:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1841558&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: Mikhail Krivtsov (mkborg)
Assigned to: Nobody/Anonymous (nobody)
Summary: "configure" reports wrong reasons of failures

Initial Comment:
While doing "./configure" I got reports that "libXinerama" and "libXrandr" are missing. But those reports appear even if libraries are installed.

Investigation revealed that:
  "XineramaQueryVersion in -lXinerama" check fails due to missing "libXext devel" package
  "XRRQueryVersion in -lXrandr" check fails due to missing "libXrender devel" package

Unfortuanely I don't yet know how to fix "configure" script.

Distribution: Fedora 8
Kernel: 2.6.23.1-49

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

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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1839981 ] "make install" only installs libguestlib

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

Tracker item #1839981, was opened at 2007-11-27 19:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1839981&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: Alf Mel (alfmel)
Assigned to: Nobody/Anonymous (nobody)
Summary: "make install" only installs libguestlib

Initial Comment:
When issuing the following commands:

  ./configure --prefix=/usr --without-x
  make
  make install

only libguestlib is installed in /usr/lib.  The other non-gui tools (checkvm, guestd, hgfsclient, hgfsmounter, scripts and xferlogs) are built, but are not installed as part of the "make install".  It would be *really nice* to have the Makefile install those utilities as part of the "make install" phase.

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

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

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

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

Tracker item #1813024, was opened at 2007-10-13 22:05
Message generated for change (Comment added) made by ikelos
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: None
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: Mike Auty (ikelos)
Date: 2007-11-26 19: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 18:38

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

Closing as "WORKSFORME"...

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

Comment By: Heiko Zuerker (smiley73)
Date: 2007-11-26 17: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 12: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 21: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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1797158 ] Open Virtual Machine Tools for windows

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

Tracker item #1797158, was opened at 2007-09-18 16:05
Message generated for change (Comment added) made by sopwith
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1797158&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: 1
Private: No
Submitted By: stopka (stopka2top)
Assigned to: Nobody/Anonymous (nobody)
Summary: Open Virtual Machine Tools for windows

Initial Comment:
Open Virtual Machine Tools for windows users.


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

>Comment By: ECL (sopwith)
Date: 2007-11-26 18:54

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

Just updating this bug to note that nothing has happened with it :) If
there is a real and pressing demand for it (e.g. someone who is actively
interested in working on contributing to the Windows tools) please note
that on this bug....

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

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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1805476 ] FreeBSD port of open-vm-tools

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

Tracker item #1805476, was opened at 2007-10-01 08:30
Message generated for change (Comment added) made by sopwith
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1805476&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: None
Priority: 5
Private: No
Submitted By: Gamester17 (gamester17)
Assigned to: Nobody/Anonymous (nobody)
Summary: FreeBSD port of open-vm-tools

Initial Comment:
I like to put in a request for "Open Virtual Machine Tools for FreeBSD"

Why limit open-vm-tools to Linux?, why not port it to make it useable diretcly in BSD operating-systems such a FreeBSD.

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

>Comment By: ECL (sopwith)
Date: 2007-11-26 18:42

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

The new open-vm-tools release should cover this.

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

Comment By: Ragavan S (ragavan_s)
Date: 2007-10-05 23:58

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

Good news. We have decided to release the source for the FreeBSD ports of
the kernel modules. We plan to release all of the modules except one (the
vmblock module) under the GPL v2. We will most likely be releasing the
vmblock module under the BSD license because it is built on top of nullfs
(which is licensed under the BSD license).

We are currently going through the internal review process for
contributing this as well as cleaning up the code a bit. We hope to be able
to include this in the next drop of the tarball.

We will update this bug when the release happens.

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

Comment By: Adar Dembo (adembo)
Date: 2007-10-01 08:40

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

The various userlevel components (guestd, vmware-user, toolbox, etc.)
should compile and run in FreeBSD as is (we tested them in FreeBSD 6 I
believe). We didn't get a chance to test other BSD-based operating systems,
although it appears that at least one other person is trying to do that
(see
http://sourceforge.net/mailarchive/forum.php?thread_name=20070930225805.GA5615%40silence.homedns.org&forum_name=open-vm-tools-devel).

We also have FreeBSD ports of the kernel modules available in binary form;
we're currently evaluating whether to release them in source form, and if
so, under what license. When a conclusion about that is reached, I'll
update this bug with more information.

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

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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1805960 ] cannot build lib/string/str.c on systems without vswprintf()

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

Tracker item #1805960, was opened at 2007-10-01 21:47
Message generated for change (Comment added) made by sopwith
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1805960&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: libraries
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Klaus Heinz (kheinz)
Assigned to: ECL (sopwith)
Summary: cannot build lib/string/str.c on systems without vswprintf()

Initial Comment:
While trying to build the software on NetBSD 3 this
is the first real blocker because vswprintf() is not
available on NetBSD 3.

../str.c: In function `Str_Vsnwprintf':
../str.c:558: warning: implicit declaration of function `vswprintf'
*** Error code 1

While NetBSD 3 is not a supported guest operating system,
FreeBSD 4.x _is_ and does _not_ have the vswprintf()
function, which makes me believe open-vm-tools cannot
be built on FreeBSD 4.

Regards,
     Klaus Heinz

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

>Comment By: ECL (sopwith)
Date: 2007-11-26 18:40

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

This one /should/ be fixed in the new open-vm-tools release. I have not
tested it, however.

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

Comment By: ECL (sopwith)
Date: 2007-10-08 22:37

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

I'm working on fixing this. No promises as to when it'll be released, but
your report has not been forgotten :)

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

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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1813016 ] make needs LDFLAGS=-liconv

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

Tracker item #1813016, was opened at 2007-10-13 21:22
Message generated for change (Comment added) made by sopwith
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1813016&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: None
Priority: 5
Private: No
Submitted By: Heiko Zuerker (smiley73)
Assigned to: ECL (sopwith)
Summary: make needs LDFLAGS=-liconv 

Initial Comment:
Hi,

the open-vm-tools only compiles in my environment when I add  LDFLAGS=-liconv  to the make command.
See the details at the end of this message.

Thanks
  Heiko
-----------------------------------

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
-----------------------------------
gcc -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 -o guestd debugStdio.o foreignVMToolsDaemon.o foreignVMToolsNetworking.o foundryToolsDaemon.o main.o stub.o toolsDaemon.o  -lcrypt -ldl -lpthread ../lib/atomic/libAtomic.a ../lib/backdoor/libBackdoor.a ../lib/conf/libConf.a ../lib/dnd/libDnd.a ../lib/err/libErr.a ../lib/eventManager/libEventManager.a ../lib/file/libFile.a ../lib/guestApp/libGuestApp.a ../lib/guestInfo/libGuestInfo.a ../lib/hgfsServer/libHgfsServer.a ../lib/hgfsServerManagerGuest/libHgfsServerManagerGuest.a ../lib/hgfsServerPolicyGuest/libHgfsServerPolicyGuest.a ../lib/deployPkg/libDeployPkg.a ../lib/impersonate/libImpersonate.a ../lib/netUtil/libNetUtil.a ../lib/printer/libPrinter.a ../lib/procMgr/libProcMgr.a ../lib/rpcIn/libRpcIn.a ../lib/rpcOut/libRpcOut.a ../lib/rpcVmx/libRpcVmx.a ../lib/SLPv2Parser/libSLPv2Parser.a ../lib/socketMgr/libSocketMgr.a ../lib/strUtil/libStrUtil.a ../lib/string/libString.a ../lib/sync/libSync.a ../lib/syncDriver/libSyncDriver.a ../lib/system/libSystem.a ../lib/user/libUser.a ../lib/vixTools/libVixTools.a ../lib/vmBackupLib/libVmBackupLib.a ../lib/vmCheck/libVmCheck.a ../lib/vmSignal/libVmSignal.a ../lib/wiper/libWiper.a ../lib/dict/libDict.a ../lib/hgfs/libHgfs.a ../lib/message/libMessage.a ../lib/misc/libMisc.a ../lib/foundryMsg/libFoundryMsg.a ../lib/fileUtf8/libFileUtf8.a ../lib/auth/libAuth.a ../lib/panicDefault/libPanicDefault.a ../lib/panic/libPanic.a
../lib/misc/libMisc.a(codeset.o): In function `CodeSetGenericToGeneric':
codeset.c:(.text+0x3c5): undefined reference to `libiconv_open'
codeset.c:(.text+0x3f5): undefined reference to `libiconv_open'
codeset.c:(.text+0x48c): undefined reference to `libiconv'
codeset.c:(.text+0x4f7): undefined reference to `libiconv_close'
codeset.c:(.text+0x51b): undefined reference to `libiconv_close'
collect2: ld returned 1 exit status
make[1]: *** [guestd] Error 1
make[1]: Leaving directory `/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/guestd'
make: *** [all-recursive] Error 1



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

>Comment By: ECL (sopwith)
Date: 2007-11-26 18:39

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

Closing as "WORKSFORME"

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

Comment By: Heiko Zuerker (smiley73)
Date: 2007-10-16 21:09

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

I disabled all security features, but it still doesn't compile. 
I'm fine with adding LDFLAGS=-liconv in our build environment, if you want
to close this tracker.

Heiko

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

Comment By: Heiko Zuerker (smiley73)
Date: 2007-10-16 00:08

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

In order to reproduce the problem you would have to get the Devil-Linux
build environment and kick off a compile.
http://www.devil-linux.org/documentation/1.2.x/ch03.html
This takes a little bit time and a couple of gigabytes of disk space.
Start with the default configuration, but stop after the 'make
menuconfig'. Edit the file .config and set OPEN_VM_TOOLS to y.

If you don't want spend the time on it, we compile everything per default
with -pie and ssp.
I did a test compile with 
make CC="gcc -nopie -fno-stack-protector" all
It still didn't work (same error).

I will kick off a fresh clean compile with all these security options
disabled, maybe that makes a difference. This will take quite a while to
finish.

Heiko

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

Comment By: ECL (sopwith)
Date: 2007-10-15 23:20

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

Thanks for reporting this problem. I'm wondering why the undefined
function references are to 'libiconv*' instead of 'iconv*'... Did you pass
some special flags when building or something like that?

glibc 2.3.2 definitely has iconv_open(), iconv(), and iconv_close()
functions included in the main libc library. I'd need info on reproducing
this before I could suggest a solution.

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

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

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

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

Tracker item #1813024, was opened at 2007-10-13 22:05
Message generated for change (Comment added) made by sopwith
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: None
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: ECL (sopwith)
Date: 2007-11-26 18:38

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

Closing as "WORKSFORME"...

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

Comment By: Heiko Zuerker (smiley73)
Date: 2007-11-26 17: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 12: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 21: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

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

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

Tracker item #1813024, was opened at 2007-10-13 17:05
Message generated for change (Comment added) made by smiley73
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: Open
Resolution: None
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: Heiko Zuerker (smiley73)
Date: 2007-11-26 12: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 07: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 16: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

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

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

Tracker item #1813024, was opened at 2007-10-13 22:05
Message generated for change (Comment added) made by ikelos
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: Open
Resolution: None
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: Mike Auty (ikelos)
Date: 2007-11-26 12: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 21: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

[open-vm-tools-devel] [ open-vm-tools-Tracker-1796805 ] Cannot configure without X libraries

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

Tracker item #1796805, was opened at 2007-09-17 22:40
Message generated for change (Comment added) made by alfmel
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1796805&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: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Alf Mel (alfmel)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot configure without X libraries

Initial Comment:
Thank you for releasing these tools to the Open Source community.

I am trying out the new tools by trying to simply build the modules in a system that does not have X installed.  I do this because I don't install X on my servers to reduce the VM hard disk footprint.

However, when running the configure script with --without-x --disable-multimon, the configure script exits with an error when trying to find the xrandr library:

checking for pkg-config... yes
checking for XRRQueryVersion in -lXrandr... no
configure: error: libXrandr not found. Please install the libXrandr devel package(s).

The README file contains the following:

(*)Building Linux kernel modules:
1) ./configure
2) make modules

Since I cannot run configure successfully, I am not even able to compile the kernel modules that should not require any X libraries what so ever.

Could you fix your configure script to allow configuration without any X libraries?  Ideally, it would also be nice to know what packages will *not* be compiled due to failed X dependencies during configuration.

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

>Comment By: Alf Mel (alfmel)
Date: 2007-11-23 17:28

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

Tried version 2007.11.21 and the configure finished successfully.  Thanks
for fixing this bug.

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

Comment By: Ragavan S (ragavan_s)
Date: 2007-10-11 16:11

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

Elliot released a development snapshot that should fix this.
http://sourceforge.net/project/showfiles.php?group_id=204462&package_id=244023&release_id=545283
(specifically the nox patch).

Can you please try that and see if it works for you?


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

Comment By: ECL (sopwith)
Date: 2007-10-08 16:35

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

I'm working on a compatibility patch that allows builds on more systems. I
know --without-x works for me because I've got builds going on a couple of
systems that don't have libXrandr, so it's just a matter of getting a
tarball out there with the fixes...

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

Comment By: Ira Abramov (seefood)
Date: 2007-10-08 16:32

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

actually, I managed to build the modules without configure finishing,
still it's a kind of an ugly improvisation :-)

I should not need any X devel libs for make modules, especially if I asked
--without-x...

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

Comment By: Ira Abramov (seefood)
Date: 2007-10-08 16:32

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

actually, I managed to build the modules without configure finishing,
still it's a kind of an ugly improvisation :-)

I should not need any X devel libs for make modules, especially if I asked
--without-x...

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

Comment By: Elias Probst (eliasp)
Date: 2007-10-08 12:17

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

Same here. It's a blocker for me as I currently can't continue development
of the Gentoo ebuild ( http://bugs.gentoo.org/show_bug.cgi?id=192377 /
vmware overlay) because my only VM where I'm doing the tests on is X-less.

I hope this is fixed soon. Would do it, but I don't have any
autotools/autoconf knowledge. I think this is fixed very fast by somebody
having some basic autotools/autoconf knowledge.

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

Comment By: Ira Abramov (seefood)
Date: 2007-10-08 10:07

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

+1, exact same proglem here. I say at least seperate a makefile for the
kernel modules from the rest.

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

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

Re: [open-vm-tools-devel] Build options

[Todd I. <tod...@gm...>]

Thanks for the response.  My responses below.

On 11/19/07, Elliot Lee <el...@vm...> wrote:
> On 11/18/07 7:43 AM, "Todd Ignasiak" <tod...@gm...> wrote:

> Hey Todd,
>
> As Charles suggested, --help gives you help, --without-x turns off X11, and
> you won't have much luck reading the configure file since it's generated by
> autoconf from configure.ac... :)

I had used --help,  but even after using --without-x it was still
stopping on Xrandr.

It looks like that option wasn't working in the release version.
But, after I found the October snapshot version, the --without-x
option had the expected result, and everything worked.

> I think the way to build kernel modules for a different kernel version is
> not quite clear, but looking at modules/linux/<foo>/Makefile is the best way
> to figure it out. A quick glance makes it look like you could pass
> VM_UNAME=<kernelver> on the command line to select a different directory
> under /lib/modules to build against.

I ended up replacing the "HEADER_DIR" setting in each of the module
config files, since the kernel I was building for was not installed on
the build host (and thus not present under /lib/modules).    Being
able to specify the KERNEL_SOURCE_DIR via the configure script would
be a nice future enhancement.

Once I made those changes, everything built fine, and I was able to
copy the modules over to my minimal VM, and they installed fine.

Re: [open-vm-tools-devel] Build options

[Elliot L. <el...@vm...>]

On 11/18/07 7:43 AM, "Todd Ignasiak" <tod...@gm...> wrote:

> Is there any documentation on the configure options for vmware tools?
> 
> The configure file is quite large,  ~850 KB, with what looks like a
> lot of default / unneeded config checks.   The huge size makes it
> difficult to pick out the relevant options.
> 
> The kind of things I'm looking for, and I'm sure others will need are:
> 
> - Which components can be enabled/disabled via configure?
>     - Specifically, how do I disable any X11 packages, and only do
> modules and command-line tools?
> - How can I specify a different kernel source path, to build modules
> for another VM which doesn't have build tools, rather than building
> for the running system?
> 
> 
> My first time running configure, it stopped on some Xinerama
> dependencies, and recommended the --disable-multimon option.   Next
> time through, it stopped on another X11 package..
> 
> I just want to build the command-line utilities, and kernel modules to
> be installed in a light-weight VM that doesn't have X-Windows, or gcc.

Hey Todd,

As Charles suggested, --help gives you help, --without-x turns off X11, and
you won't have much luck reading the configure file since it's generated by
autoconf from configure.ac... :)

I think the way to build kernel modules for a different kernel version is
not quite clear, but looking at modules/linux/<foo>/Makefile is the best way
to figure it out. A quick glance makes it look like you could pass
VM_UNAME=<kernelver> on the command line to select a different directory
under /lib/modules to build against.

Hope this helps,
-- Elliot

Re: [open-vm-tools-devel] Build options

[Charles N W. <ch...@th...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Todd Ignasiak wrote:
> Is there any documentation on the configure options for vmware tools?

Have you tried the --help option?

> 
> The configure file is quite large,  ~850 KB, with what looks like a
> lot of default / unneeded config checks.   The huge size makes it
> difficult to pick out the relevant options.

Haha. Have you ever had to work with autotools to build a configure
script? Its a lot of work and the checks often have dependencies etc.

> 
> The kind of things I'm looking for, and I'm sure others will need are:
> 
> - Which components can be enabled/disabled via configure?
>     - Specifically, how do I disable any X11 packages, and only do
> modules and command-line tools?

This has been covered in the archives of this list a few times now.
Perhaps its time for a FAQ?



- --
Charles N Wyble ch...@th... (818) 280 7059
Website: http://www.thewybles.com/~charles
Blog: http://jackshck.livejournal.com

President and CEO of Known Element Enterprises and affiliated companies.
Website: http://www.knownelement.com
Blog: http://siliconvs.blogspot.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHQIuwkQPZV56XDBMRAlybAKCN+gTtx/xhDgvZqBKTGg8RvdySXQCfeUhD
qwTltmnmONkqlfBF4ubBS3g=
=9bnk
-----END PGP SIGNATURE-----

[open-vm-tools-devel] Build options

[Todd I. <tod...@gm...>]

Is there any documentation on the configure options for vmware tools?

The configure file is quite large,  ~850 KB, with what looks like a
lot of default / unneeded config checks.   The huge size makes it
difficult to pick out the relevant options.

The kind of things I'm looking for, and I'm sure others will need are:

- Which components can be enabled/disabled via configure?
    - Specifically, how do I disable any X11 packages, and only do
modules and command-line tools?
- How can I specify a different kernel source path, to build modules
for another VM which doesn't have build tools, rather than building
for the running system?


My first time running configure, it stopped on some Xinerama
dependencies, and recommended the --disable-multimon option.   Next
time through, it stopped on another X11 package..

I just want to build the command-line utilities, and kernel modules to
be installed in a light-weight VM that doesn't have X-Windows, or gcc.

Re: [open-vm-tools-devel] Next release

[Johannes K. <oj...@gm...>]

Elliot Lee schrieb:

> Hey Johannes,
>=20
> If you're interested in implementing this type of thing, the VMDK specs=
 are
> available ;)

If I could I would have done so, but Im not a programmer, so... ;-(

OJ

Re: [open-vm-tools-devel] Next release

[Johannes K. <oj...@gm...>]

Adar Dembo schrieb:
>> I was hoping this could be the right place to ask for the
>> mount-vmdks-feature on linux, but apparently it was not... ;-(
>=20
> In the Server 2.0 beta (http://www.vmware.com/beta/server) I think you'=
ll
> find the new "fuseMount" utility for mounting vmdks using a fuse filesy=
stem.
> I think it will install itself as the vmware-mount binary.

That would be one hell of a feature, that I would like to see. Let me
get the new beta... ;-)

OJ

Re: [open-vm-tools-devel] Next release

[Adar D. <ad...@vm...>]

> I was hoping this could be the right place to ask for the
> mount-vmdks-feature on linux, but apparently it was not... ;-(

In the Server 2.0 beta (http://www.vmware.com/beta/server) I think =
you'll
find the new "fuseMount" utility for mounting vmdks using a fuse =
filesystem.
I think it will install itself as the vmware-mount binary.

Re: [open-vm-tools-devel] Next release

[Elliot L. <el...@vm...>]

On 11/15/07 4:42 AM, "Johannes Kastl" <oj...@gm...> wrote:

> I was hoping this could be the right place to ask for the
> mount-vmdks-feature on linux, but apparently it was not... ;-(

Hey Johannes,

If you're interested in implementing this type of thing, the VMDK specs are
available ;)

http://www.vmware.com/interfaces/vmdk.html

Best,
-- Elliot

Re: [open-vm-tools-devel] Next release

[Johannes K. <oj...@gm...>]

Hi,

Marcelo Vanzin schrieb:

> I think Elliot's comments are not 100% accurate. :-) The purpose of
> the driver is not really to make backups easier, but to make disk
> snapshots more consistent, by flushing all data that is cached in
> memory before taking a snapshot and preventing applications from
> writing to disk during the snapshot.

Ah, I see.

> So it's not really related to being able to mount vmdk files or
> anything like that - it's just a helper driver that runs in the
> guest, which is triggered by the snapshotting code in some VMware
> products.

OK.

> The way it works is the tools daemon (vmware-guestd) receives a
> command to "freeze" the filesystems in the VM, and it then tells the
> driver to do that. The driver flushes all caches and "freezes" the
> filesystems (meaning no writes are allowed until it's "thawed"). The
> VMware code in the host then takes a snapshot and notifies
> vmware-guestd that it's done, and then it tells the driver to "thaw"
> the filesystems, resuming normal operation.

Thanks for that explanation.

I was hoping this could be the right place to ask for the
mount-vmdks-feature on linux, but apparently it was not... ;-(

Thanks anyway,
OJ
--=20
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
(Benjamin Franklin, 1759)

Re: [open-vm-tools-devel] Next release

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

Hi Johannes,

Johannes Kastl wrote:
> Elliot Lee schrieb:
>> . Adding the vmsync kernel module (makes it easier to backup a virtual
>> machine)
> 
> Yes. How will that "backup" work? Will it be possible to mount
> vmdk-files on linux? Or is this some kind of shared-folder-thingy kind
> of way?

I think Elliot's comments are not 100% accurate. :-) The purpose of the driver is not really to make backups easier, but to make disk snapshots more consistent, by flushing all data that is cached in memory before taking a snapshot and preventing applications from writing to disk during the snapshot.

So it's not really related to being able to mount vmdk files or anything like that - it's just a helper driver that runs in the guest, which is triggered by the snapshotting code in some VMware products.

The way it works is the tools daemon (vmware-guestd) receives a command to "freeze" the filesystems in the VM, and it then tells the driver to do that. The driver flushes all caches and "freezes" the filesystems (meaning no writes are allowed until it's "thawed"). The VMware code in the host then takes a snapshot and notifies vmware-guestd that it's done, and then it tells the driver to "thaw" the filesystems, resuming normal operation.

-- 
- Marcelo

Re: [open-vm-tools-devel] Next release

[Johannes K. <oj...@gm...>]

Elliot Lee schrieb:

> . Adding the vmsync kernel module (makes it easier to backup a virtual
> machine)

> Any suggestions or questions?

Yes. How will that "backup" work? Will it be possible to mount
vmdk-files on linux? Or is this some kind of shared-folder-thingy kind
of way?

Maybe I completely misunderstood that statement... ;-)

OJ
--=20
Working with Unix is like wrestling a worthy opponent. Working with
windows is like attacking a small whining child who is carrying a .38.

Re: [open-vm-tools-devel] Power functions in vmware-guestd

[Justin M. F. <jmf...@li...>]

On Thu, 2007-11-08 at 18:21 -0800, Elliot Lee wrote:

> Thanks for the explanation. I think a .d scheme would be very useful and
> very easy to do. Can't promise it for the next release (which I'm hoping
> will be ready in a week or so), but I'll try if there's time. The main thing
> I'd like feedback from others on is the actual directory path that these
> scripts will be dropped into. I'm thinking of either
> 
> Scriptsdir="`dirname $0`"/scripts/`basename $0`.d"
> 
> (to match your current setup) or just
> 
> Scriptsdir=$0.d
> 
> The main constraint is that it has to work properly even if the scripts are
> in /usr/local/etc or /var/fooblah.
> 
Right, so the scripts really have to be in a set place at build time, by
default that is $sysconfdir/vmware-tools.  It seems to make the most
sense to me that we look in that tree for the user scripts.
Scriptsdir="`dirname $0`"/scripts/`basename $0`.d" would work just fine,
our actual scripts use %(sysconfdir)s/vmware-tools/ and use conary macro
substitution to place that as /etc/vmware-tools at build time.  Of
course if the builder has those set elsewhere, that is fine too.

Justin

Re: [open-vm-tools-devel] RPM packages?

[Ragavan S <rag...@gm...>]

>
> For a lot of the components, I'm not really sure what they do, which
> makes it hard to know how to package them.  For instance, I made the
> guess that 'vmblock' is used for drag-and-drop (something ESX users
> don't have to use).  However, its not clear to me if its used for
> anything else.  Likewise, most of the other components don't have what
> they're used for specified.

Good idea. I've started a new page to document this on the wiki.
http://open-vm-tools.wiki.sourceforge.net/ComponentFunctionality

Right now it is sparse - I copied Andrew's description of where
vmblock is used. We'll start adding similar descriptions for the other
components as well.

>
> I'd also like to note that the Packaging page references
> vmware-xferlogs, which isn't actually available in the source download.

This was missed due to an oversight on our part. As Elliot said, it
will be in the next release.

Regards,
Ragavan

Re: [open-vm-tools-devel] RPM packages?

[Elliot L. <el...@vm...>]

On 11/9/07 10:06 AM, "Sean Dilda" <se...@du...> wrote:

> I'd also like to note that the Packaging page references
> vmware-xferlogs, which isn't actually available in the source download.

It'll be in the next release. :)

Best,
-- Elliot