Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Gelsema, P (Patrick) - FreeBSD
On Tue, March 18, 2008 12:23, Peter Boosten wrote:
 Gelsema, P (Patrick) - FreeBSD wrote:
 On Tue, March 18, 2008 11:40, Peter Boosten wrote:

 http://open-vm-tools.sourceforge.net/


 Just to confirm. This one runs on RELENG_7_0?

 quote
 Kernel modules for FreeBSD, including an experimental port of HGFS to
 FreeBSD.
 /quote

 It allows dymanic memory management by the VM Ware host?
  
   It also allows the VMWare host to gracefully shutdown the Freebsd
 guest?
  

I get an error running an install on RELENG_7_0 I386.

Making check in hgfsmounter
gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\
-DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\
2008.03.03-79993\
-DPACKAGE_BUGREPORT=\[EMAIL PROTECTED]
-DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\
-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_DLOPEN=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1
-DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I.   
 -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing
-Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS
-I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT
hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o
hgfsmounter.c
hgfsmounter.c: In function 'ParseOptions':
hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this function)
hgfsmounter.c:607: error: (Each undeclared identifier is reported only once
hgfsmounter.c:607: error: for each function it appears in.)
*** Error code 1

Someone seen this before?

Rgds,

Patrick


 quote
 The following components have been released as OSS:

  * Drivers for devices and filesystems access
  * Memory ballooning
  * Shared folders
  * Drag and Drop, Text and File Copy/Paste
  * Clipboard sharing
  * Disk wiping and shrinking
  * Time synchronization
  * Automatic guest screen resolution resizing
  * GuestInfo (provides statistics about guest environment)
  * Guest SDK (provides information about the VM)
  * Soft power operations
  * Multiple monitor support
  * GTK Toolbox UI
 /quote

 Peter

 --
 http://www.boosten.org


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Paul Schmehl
--On Tuesday, March 18, 2008 22:34:30 +0800 Gelsema, P (Patrick) - FreeBSD 
[EMAIL PROTECTED] wrote:


I get an error running an install on RELENG_7_0 I386.

Making check in hgfsmounter
gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\
-DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\
2008.03.03-79993\
-DPACKAGE_BUGREPORT=\[EMAIL PROTECTED]
-DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\
-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_DLOPEN=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1
-DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I.
 -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing
-Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS
-I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT
hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o
hgfsmounter.c
hgfsmounter.c: In function 'ParseOptions':
hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this function)
hgfsmounter.c:607: error: (Each undeclared identifier is reported only once
hgfsmounter.c:607: error: for each function it appears in.)
*** Error code 1

Someone seen this before?



Yes, I got it as well.  I was going to create a port for it, but I have no idea 
how to solve the make problem.  If there is a programmer reading this that 
wants to work with me to get the software to make on FreeBSD, I'll be happy to 
submit and maintain the port.


--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Alexander Sack
I believe the issue is that MNT_NODEV which should be defined in
/usr/include/sys/mount.h was deprecated and removed from FreeBSD:

http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715

At line 42 in hgfsmounter.c, add

# define MNT_NODEV  0

Then rebuild.  SHould work fine now.

I configured my build environment via the README with ./configure
LDFLAGS=/usr/local/lib etc.

-aps

On Tue, Mar 18, 2008 at 10:42 AM, Paul Schmehl [EMAIL PROTECTED] wrote:
 --On Tuesday, March 18, 2008 22:34:30 +0800 Gelsema, P (Patrick) - FreeBSD


 [EMAIL PROTECTED] wrote:
  
   I get an error running an install on RELENG_7_0 I386.
  
   Making check in hgfsmounter
   gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\
   -DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\
   2008.03.03-79993\
   -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED]
   -DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\
   -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_DLOPEN=1 -DHAVE_INTTYPES_H=1
   -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1
   -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1
   -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I.
-Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing
   -Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS
   -I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT
   hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o
   hgfsmounter.c
   hgfsmounter.c: In function 'ParseOptions':
   hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this 
 function)
   hgfsmounter.c:607: error: (Each undeclared identifier is reported only once
   hgfsmounter.c:607: error: for each function it appears in.)
   *** Error code 1
  
   Someone seen this before?
  

  Yes, I got it as well.  I was going to create a port for it, but I have no 
 idea
  how to solve the make problem.  If there is a programmer reading this that
  wants to work with me to get the software to make on FreeBSD, I'll be happy 
 to
  submit and maintain the port.

  --

 Paul Schmehl ([EMAIL PROTECTED])
  Senior Information Security Analyst
  The University of Texas at Dallas
  http://www.utdallas.edu/ir/security/

  ___


 freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]




-- 
What lies behind us and what lies in front of us is of little concern
to what lies within us. -Ralph Waldo Emerson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Paul Schmehl
--On Tuesday, March 18, 2008 11:36:53 -0400 Alexander Sack [EMAIL PROTECTED] 
wrote:



I believe the issue is that MNT_NODEV which should be defined in
/usr/include/sys/mount.h was deprecated and removed from FreeBSD:

http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715

At line 42 in hgfsmounter.c, add

# define MNT_NODEV  0

Then rebuild.  SHould work fine now.


Thanks.  I was contacted privately by someone else on the list and advised of 
the same thing.  I chose to remove the lines mentioning MNT_NODEV from the 
hgfsmounter.c file.  I wasn't aware you could simply define it as 0.  Which is 
preferable?




I configured my build environment via the README with ./configure
LDFLAGS=/usr/local/lib etc.



I'm compiling and making without problems now that the NODEV problem is cleared 
up, but I didn't define any LDFLAGS.  Should I?


--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Gelsema, P (Patrick)
On Tue, March 18, 2008 23:36, Alexander Sack wrote:
 I believe the issue is that MNT_NODEV which should be defined in
 /usr/include/sys/mount.h was deprecated and removed from FreeBSD:

 http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715

 At line 42 in hgfsmounter.c, add

 # define MNT_NODEV  0

 Then rebuild.  SHould work fine now.

 I configured my build environment via the README with ./configure
 LDFLAGS=/usr/local/lib etc.

Done

#./configure LDFLAGS=/usr/local/lib --without-x
#make
#make install

That all goes ok
But when I run #make modules I get an error

wolverine# make modules
make -C modules
make -C freebsd/vmmemctl
make -C freebsd/vmxnet
cc -O2 -fno-strict-aliasing -pipe  -D_KERNEL -DKLD_MODULE -std=c99
-nostdinc   -I. -I@ -I@/contrib/altq -finline-limit=8000 --param
inline-unit-growth=100 --param large-function-growth=1000 -fno-common 
-mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow
-mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -c
if_vxn.c
if_vxn.c: In function 'vxn_attach':
if_vxn.c:302: warning: passing argument 4 of 'bus_setup_intr' from
incompatible pointer type
if_vxn.c:302: warning: passing argument 5 of 'bus_setup_intr' from
incompatible pointer type
if_vxn.c:302: error: too few arguments to function 'bus_setup_intr'
if_vxn.c:378: error: 'struct arpcom' has no member named '_ac_enaddr'
if_vxn.c:385: error: 'struct arpcom' has no member named '_ac_enaddr'
*** Error code 1

Stop in /tmp/open-vm-tools-2008.03.03-79993/modules/freebsd/vmxnet.
*** Error code 1

Any ideas?

 -aps

 On Tue, Mar 18, 2008 at 10:42 AM, Paul Schmehl [EMAIL PROTECTED] wrote:
 --On Tuesday, March 18, 2008 22:34:30 +0800 Gelsema, P (Patrick) -
 FreeBSD


 [EMAIL PROTECTED] wrote:
  
   I get an error running an install on RELENG_7_0 I386.
  
   Making check in hgfsmounter
   gcc -DPACKAGE_NAME=\open-vm-tools\
 -DPACKAGE_TARNAME=\open-vm-tools\
   -DPACKAGE_VERSION=\2008.03.03-79993\
 -DPACKAGE_STRING=\open-vm-tools\
   2008.03.03-79993\
   -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED]
   -DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\
   -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_DLOPEN=1 -DHAVE_INTTYPES_H=1
   -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1
 -DHAVE_SYS_PARAM_H=1
   -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1
 -DHAVE_STDBOOL_H=1
   -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1
 -I.
-Wall -Werror -Wno-pointer-sign -Wno-unused-value
 -fno-strict-aliasing
   -Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS
   -I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1
 -MT
   hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o
   hgfsmounter.c
   hgfsmounter.c: In function 'ParseOptions':
   hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this
 function)
   hgfsmounter.c:607: error: (Each undeclared identifier is reported
 only once
   hgfsmounter.c:607: error: for each function it appears in.)
   *** Error code 1
  
   Someone seen this before?
  

  Yes, I got it as well.  I was going to create a port for it, but I have
 no idea
  how to solve the make problem.  If there is a programmer reading this
 that
  wants to work with me to get the software to make on FreeBSD, I'll be
 happy to
  submit and maintain the port.

  --

 Paul Schmehl ([EMAIL PROTECTED])
  Senior Information Security Analyst
  The University of Texas at Dallas
  http://www.utdallas.edu/ir/security/

  ___


 freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to
 [EMAIL PROTECTED]




 --
 What lies behind us and what lies in front of us is of little concern
 to what lies within us. -Ralph Waldo Emerson
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Alexander Sack
Comments below:

On Tue, Mar 18, 2008 at 12:13 PM, Gelsema, P (Patrick)
[EMAIL PROTECTED] wrote:
 On Tue, March 18, 2008 23:36, Alexander Sack wrote:
   I believe the issue is that MNT_NODEV which should be defined in
   /usr/include/sys/mount.h was deprecated and removed from FreeBSD:
  
   http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715
  
   At line 42 in hgfsmounter.c, add
  
   # define MNT_NODEV  0
  
   Then rebuild.  SHould work fine now.
  
   I configured my build environment via the README with ./configure
   LDFLAGS=/usr/local/lib etc.
  
  Done

  #./configure LDFLAGS=/usr/local/lib --without-x
  #make
  #make install

  That all goes ok
  But when I run #make modules I get an error

  wolverine# make modules
  make -C modules
  make -C freebsd/vmmemctl
  make -C freebsd/vmxnet
  cc -O2 -fno-strict-aliasing -pipe  -D_KERNEL -DKLD_MODULE -std=c99
  -nostdinc   -I. -I@ -I@/contrib/altq -finline-limit=8000 --param
  inline-unit-growth=100 --param large-function-growth=1000 -fno-common
  -mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow
  -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
  -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -c
  if_vxn.c
  if_vxn.c: In function 'vxn_attach':
  if_vxn.c:302: warning: passing argument 4 of 'bus_setup_intr' from
  incompatible pointer type
  if_vxn.c:302: warning: passing argument 5 of 'bus_setup_intr' from
  incompatible pointer type
  if_vxn.c:302: error: too few arguments to function 'bus_setup_intr'
  if_vxn.c:378: error: 'struct arpcom' has no member named '_ac_enaddr'
  if_vxn.c:385: error: 'struct arpcom' has no member named '_ac_enaddr'
  *** Error code 1

  Stop in /tmp/open-vm-tools-2008.03.03-79993/modules/freebsd/vmxnet.
  *** Error code 1

  Any ideas?

bus_setup_intr() kernel API seems to have either changed or handled
differently in 7.0.  I believe you can add a NULL after the flags
(INTR_MPSAFE) which tells BSD to use the standard interrupt handler
instead of a top-level handler.

_ac_enaddr is because arpcom as defined in net/if_arp.h no longer
exists.  Typically the protocol bits are stuffed in if_l2com (layer
2).

I made the macro in net_compat.h

#define VXN_SC2ENADDR(softc)(IF_LLADDR(VXN_SC2IFP(softc))

and then removed the  from both references in if_vxn.c as this
macro already returns a pointer to char.

That got me past this problem.  Btw, this isn't an official port since
I didn't really rectify the net_compat.h stuff (I suppose you could
make the 60 to 700055, etc.).

I'm still getting some further issues with vnodeops and vfsops with
some modules (I believe vops_lcok should be vops_lock1) but I don't
know about the other problem.

-aps

-- 
What lies behind us and what lies in front of us is of little concern
to what lies within us. -Ralph Waldo Emerson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Paul Schmehl
--On Tuesday, March 18, 2008 15:24:53 -0400 Alexander Sack [EMAIL PROTECTED] 
wrote:


bus_setup_intr() kernel API seems to have either changed or handled
differently in 7.0.  I believe you can add a NULL after the flags
(INTR_MPSAFE) which tells BSD to use the standard interrupt handler
instead of a top-level handler.

_ac_enaddr is because arpcom as defined in net/if_arp.h no longer
exists.  Typically the protocol bits are stuffed in if_l2com (layer
2).

I made the macro in net_compat.h

# define VXN_SC2ENADDR(softc)(IF_LLADDR(VXN_SC2IFP(softc))

and then removed the  from both references in if_vxn.c as this
macro already returns a pointer to char.

That got me past this problem.  Btw, this isn't an official port since
I didn't really rectify the net_compat.h stuff (I suppose you could
make the 60 to 700055, etc.).

I'm still getting some further issues with vnodeops and vfsops with
some modules (I believe vops_lcok should be vops_lock1) but I don't
know about the other problem.



Well, you're way beyond my skill level now.  I'll be happy to create a port for 
this, but someone with a much deeper knowledge of FreeBSD and C is going to 
have to resolve the problems with the modules.


If someone is interested in doing that, I'll submit the patches to the 
developers *and* add them to the port so that it can be committed.  (Other than 
the kernel modules, the software builds fine from what I can tell.)


--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-18 Thread Alexander Sack
Paul:

I'd have to look at this some more.  I got much further in the porting
when I hit another snag with the vmblock driver (the inline assembly
needs to be __asm__ instead of asm or something needs to process it
that way for it to work, I also hacked around a vfsops issue which I'm
not 100% sure what should really be there) and then all of it needs to
be devtested.  I use VMWare Fusion and have installed the existing
vmtools that come with the product along with installing the
individual X11 vmware driver which works for me but I agree it would
be nice to have full port to FreeBSD 7.0-RELEASE.

I'm sorry for not giving you patch files its just I was doing this on
and off as a exercise to learn a little bit more about it

I believe at least now as you said, the userland stuff builds fine now.

Thanks!

-aps

On Tue, Mar 18, 2008 at 4:58 PM, Paul Schmehl [EMAIL PROTECTED] wrote:
 --On Tuesday, March 18, 2008 15:24:53 -0400 Alexander Sack [EMAIL PROTECTED]
  wrote:
  

  bus_setup_intr() kernel API seems to have either changed or handled
   differently in 7.0.  I believe you can add a NULL after the flags
   (INTR_MPSAFE) which tells BSD to use the standard interrupt handler
   instead of a top-level handler.
  
   _ac_enaddr is because arpcom as defined in net/if_arp.h no longer
   exists.  Typically the protocol bits are stuffed in if_l2com (layer
   2).
  
   I made the macro in net_compat.h
  
  # define VXN_SC2ENADDR(softc)(IF_LLADDR(VXN_SC2IFP(softc))
  
   and then removed the  from both references in if_vxn.c as this
   macro already returns a pointer to char.
  
   That got me past this problem.  Btw, this isn't an official port since
   I didn't really rectify the net_compat.h stuff (I suppose you could
   make the 60 to 700055, etc.).
  
   I'm still getting some further issues with vnodeops and vfsops with
   some modules (I believe vops_lcok should be vops_lock1) but I don't
   know about the other problem.
  

  Well, you're way beyond my skill level now.  I'll be happy to create a port 
 for
  this, but someone with a much deeper knowledge of FreeBSD and C is going to
  have to resolve the problems with the modules.

  If someone is interested in doing that, I'll submit the patches to the
  developers *and* add them to the port so that it can be committed.  (Other 
 than
  the kernel modules, the software builds fine from what I can tell.)

  --


 Paul Schmehl ([EMAIL PROTECTED])
  Senior Information Security Analyst
  The University of Texas at Dallas
  http://www.utdallas.edu/ir/security/

  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]




-- 
What lies behind us and what lies in front of us is of little concern
to what lies within us. -Ralph Waldo Emerson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: FW: VMWare Tools for FreeBSD

2008-03-17 Thread Ted Mittelstaedt


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Terry Sposato
 Sent: Sunday, March 16, 2008 3:04 PM
 To: freebsd-questions@freebsd.org
 Subject: Re: FW: VMWare Tools for FreeBSD


 SNIP

 
  Ted Mittelstaedt wrote:
  Are you asking if FreeBSD can be made to run the ESX software so that
  a FreeBSD server can virtualize multiple systems, or are you asking
  if an ESX server can create a virtual machine that FreeBSD can run in?
 
  If your using the commercial ESX product I would assume you would be
  using it on it's own bare metal product incarnation which I think
  uses a hacked-up version of Linux (without a compiler or any other
  normal Linux tools).  In that case I do not see why you would have
  a problem running multiple FreeBSD virtual servers on the ESX
  server.
 
  That's not what OP is asking. He wants to run FreeBSD as VM in ESX.
  There's currently no support from VMWare for FreeBSD, but it
 runs anyway.
 
 
  I figured that was what he was asking, but we should probably
  hear from him to make sure that this is really what he was asking.
 
  Unfortunately,
  the original post was either from someone who didn't use English
  as their native language, or they are paying for their Internet
  connection by-the-byte and were trying to make the question as
  short as possible, as a result, the entire meaning of the post
  was lost.
 
  Ted
 

 OK, maybe I was not clear enough so I will try again.
 I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently
 there is no problem with it and it works fine. The problems arise when
 you want to take advantage of the HA ability of ESX Server, as it only
 supports Virtual Machines with the VM Tools running.

 So what I am asking is if someone has ever though about porting the
 VMWare Tools to run in a FreeBSD Virtual Machine image.


Terry, Jeff Dickens replied this morning - perhaps his mail
crossed yours?  The answer is yes, you can do it with the
free vm tools from the free vmware product.  If you have
problems compiling these, please post.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-17 Thread Terry Sposato

Ted Mittelstaedt wrote:



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Terry Sposato
Sent: Sunday, March 16, 2008 3:04 PM
To: freebsd-questions@freebsd.org
Subject: Re: FW: VMWare Tools for FreeBSD


SNIP


Ted Mittelstaedt wrote:

Are you asking if FreeBSD can be made to run the ESX software so that
a FreeBSD server can virtualize multiple systems, or are you asking
if an ESX server can create a virtual machine that FreeBSD can run in?

If your using the commercial ESX product I would assume you would be
using it on it's own bare metal product incarnation which I think
uses a hacked-up version of Linux (without a compiler or any other
normal Linux tools).  In that case I do not see why you would have
a problem running multiple FreeBSD virtual servers on the ESX
server.


That's not what OP is asking. He wants to run FreeBSD as VM in ESX.
There's currently no support from VMWare for FreeBSD, but it

runs anyway.

I figured that was what he was asking, but we should probably
hear from him to make sure that this is really what he was asking.

Unfortunately,
the original post was either from someone who didn't use English
as their native language, or they are paying for their Internet
connection by-the-byte and were trying to make the question as
short as possible, as a result, the entire meaning of the post
was lost.

Ted


OK, maybe I was not clear enough so I will try again.
I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently
there is no problem with it and it works fine. The problems arise when
you want to take advantage of the HA ability of ESX Server, as it only
supports Virtual Machines with the VM Tools running.

So what I am asking is if someone has ever though about porting the
VMWare Tools to run in a FreeBSD Virtual Machine image.



Terry, Jeff Dickens replied this morning - perhaps his mail
crossed yours?  The answer is yes, you can do it with the
free vm tools from the free vmware product.  If you have
problems compiling these, please post.

Ted



Ted / Jeff,

Could you please let me know where to download these free vm tools. The 
only description at google I can find is that of the actual VMWare Tools 
by VMWare. If you point me to a download link that would be great!


Terry



signature.asc
Description: OpenPGP digital signature


Re: FW: VMWare Tools for FreeBSD

2008-03-17 Thread Peter Boosten


Terry Sposato wrote:


Ted / Jeff,

Could you please let me know where to download these free vm tools. The 
only description at google I can find is that of the actual VMWare Tools 
by VMWare. If you point me to a download link that would be great!




Although my name isn't Ted or Jeff I will post the link :-)

This is from a discussion last week:

http://open-vm-tools.sourceforge.net/

Peter
--
http://www.boosten.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-17 Thread Gelsema, P (Patrick) - FreeBSD
On Tue, March 18, 2008 11:40, Peter Boosten wrote:

 Terry Sposato wrote:

 Ted / Jeff,

 Could you please let me know where to download these free vm tools. The
 only description at google I can find is that of the actual VMWare Tools
 by VMWare. If you point me to a download link that would be great!


 Although my name isn't Ted or Jeff I will post the link :-)

 This is from a discussion last week:

 http://open-vm-tools.sourceforge.net/


Just to confirm. This one runs on RELENG_7_0?
It allows dymanic memory management by the VM Ware host?

It also allows the VMWare host to gracefully shutdown the Freebsd guest?

thanks

Patrick Gelsema




 Peter
 --
 http://www.boosten.org
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-17 Thread Peter Boosten

Gelsema, P (Patrick) - FreeBSD wrote:

On Tue, March 18, 2008 11:40, Peter Boosten wrote:


http://open-vm-tools.sourceforge.net/



Just to confirm. This one runs on RELENG_7_0?


quote
Kernel modules for FreeBSD, including an experimental port of HGFS to 
FreeBSD.

/quote


It allows dymanic memory management by the VM Ware host?


 It also allows the VMWare host to gracefully shutdown the Freebsd guest?


quote
The following components have been released as OSS:

* Drivers for devices and filesystems access
* Memory ballooning
* Shared folders
* Drag and Drop, Text and File Copy/Paste
* Clipboard sharing
* Disk wiping and shrinking
* Time synchronization
* Automatic guest screen resolution resizing
* GuestInfo (provides statistics about guest environment)
* Guest SDK (provides information about the VM)
* Soft power operations
* Multiple monitor support
* GTK Toolbox UI
/quote

Peter

--
http://www.boosten.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-16 Thread Terry Sposato

SNIP



Ted Mittelstaedt wrote:

Are you asking if FreeBSD can be made to run the ESX software so that
a FreeBSD server can virtualize multiple systems, or are you asking
if an ESX server can create a virtual machine that FreeBSD can run in?

If your using the commercial ESX product I would assume you would be
using it on it's own bare metal product incarnation which I think
uses a hacked-up version of Linux (without a compiler or any other
normal Linux tools).  In that case I do not see why you would have
a problem running multiple FreeBSD virtual servers on the ESX
server.


That's not what OP is asking. He wants to run FreeBSD as VM in ESX.
There's currently no support from VMWare for FreeBSD, but it runs anyway.



I figured that was what he was asking, but we should probably
hear from him to make sure that this is really what he was asking.

Unfortunately,
the original post was either from someone who didn't use English
as their native language, or they are paying for their Internet
connection by-the-byte and were trying to make the question as
short as possible, as a result, the entire meaning of the post
was lost.

Ted



OK, maybe I was not clear enough so I will try again.
I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently 
there is no problem with it and it works fine. The problems arise when 
you want to take advantage of the HA ability of ESX Server, as it only 
supports Virtual Machines with the VM Tools running.


So what I am asking is if someone has ever though about porting the 
VMWare Tools to run in a FreeBSD Virtual Machine image.


Terry
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FW: VMWare Tools for FreeBSD

2008-03-16 Thread Paul Schmehl
--On March 17, 2008 10:03:54 AM +1100 Terry Sposato [EMAIL PROTECTED] 
wrote:


OK, maybe I was not clear enough so I will try again.
I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently
there is no problem with it and it works fine. The problems arise when
you want to take advantage of the HA ability of ESX Server, as it only
supports Virtual Machines with the VM Tools running.

So what I am asking is if someone has ever though about porting the
VMWare Tools to run in a FreeBSD Virtual Machine image.



I downloaded the open-vm-tools from Sourceforge and tried to compile and 
make them.  The compile went fine, but the make failed.  I'm not a 
programmer, so I struggle trying to resolve such problems.  I'd be happy 
to make a port for it, but I would need help from someone with more 
programming knowledge than I.


Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]