Vmware tools on Openbsd 4.6?

[Stellar]

This could be a guide for installing vmware tools,dunno tough just read till the end where the problem really are

My Setup : Vmware Workstation 7,Freebsd Option,LSI Logic+IDE

You need to recompile your kernel with this :

# cd /usr/src
# wget ftp://your.mirror/pub/OpenBSD/4.5/sys.tar.gz
# tar -xzvpf sys.tar.gz
# cp /bsd /bsd.backup
# cp /usr/src/sys/arch/i386/conf/GENERIC /usr/src/sys/arch/i386/conf/GENERIC.vmt
# vi /usr/src/sys/arch/i386/conf/GENERIC.vmt
-> uncomment the line: vmt0    at mainbus?             # VMware Tools
# cd /usr/src/sys/arch/i386/conf
# config GENERIC.vmt
# cd ..
# make clean && make depend && make
# make install

Credit : http://serverfault.com/questions/287...e-server-2-0-x

Eventough after i recompile i still get a lot of unknown devices :

ppb2 at pci0 dev 21 function 0 vendor "VMware", unknown product 0x07a0 rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci0 dev 21 function 1 vendor "VMware", unknown product 0x07a0 rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci0 dev 21 function 2 vendor "VMware", unknown product 0x07a0 rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 vendor "VMware", unknown product 0x07a0 rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 vendor "VMware", unknown product 0x07a0 rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 vendor "VMware", unknown product 0x07a0 rev 0x01
pci8 at ppb7 bus 8
ppb8 at pci0 dev 21 function 6 vendor "VMware", unknown product 0x07a0 rev 0x01
pci9 at ppb8 bus 9
ppb9 at pci0 dev 21 function 7 vendor "VMware", unknown product 0x07a0 rev 0x01
pci10 at ppb9 bus 10
ppb10 at pci0 dev 22 function 0 vendor "VMware", unknown product 0x07a0 rev 0x01
pci11 at ppb10 bus 11
ppb11 at pci0 dev 22 function 1 vendor "VMware", unknown product 0x07a0 rev 0x01
pci12 at ppb11 bus 12
ppb12 at pci0 dev 22 function 2 vendor "VMware", unknown product 0x07a0 rev 0x01
pci13 at ppb12 bus 13
ppb13 at pci0 dev 22 function 3 vendor "VMware", unknown product 0x07a0 rev 0x01
pci14 at ppb13 bus 14
ppb14 at pci0 dev 22 function 4 vendor "VMware", unknown product 0x07a0 rev 0x01
pci15 at ppb14 bus 15
ppb15 at pci0 dev 22 function 5 vendor "VMware", unknown product 0x07a0 rev 0x01
pci16 at ppb15 bus 16
ppb16 at pci0 dev 22 function 6 vendor "VMware", unknown product 0x07a0 rev 0x01
pci17 at ppb16 bus 17
ppb17 at pci0 dev 22 function 7 vendor "VMware", unknown product 0x07a0 rev 0x01
pci18 at ppb17 bus 18
ppb18 at pci0 dev 23 function 0 vendor "VMware", unknown product 0x07a0 rev 0x01
pci19 at ppb18 bus 19
ppb19 at pci0 dev 23 function 1 vendor "VMware", unknown product 0x07a0 rev 0x01
pci20 at ppb19 bus 20
ppb20 at pci0 dev 23 function 2 vendor "VMware", unknown product 0x07a0 rev 0x01
pci21 at ppb20 bus 21
ppb21 at pci0 dev 23 function 3 vendor "VMware", unknown product 0x07a0 rev 0x01
pci22 at ppb21 bus 22
ppb22 at pci0 dev 23 function 4 vendor "VMware", unknown product 0x07a0 rev 0x01
pci23 at ppb22 bus 23
ppb23 at pci0 dev 23 function 5 vendor "VMware", unknown product 0x07a0 rev 0x01
pci24 at ppb23 bus 24
ppb24 at pci0 dev 23 function 6 vendor "VMware", unknown product 0x07a0 rev 0x01
pci25 at ppb24 bus 25
ppb25 at pci0 dev 23 function 7 vendor "VMware", unknown product 0x07a0 rev 0x01
pci26 at ppb25 bus 26
ppb26 at pci0 dev 24 function 0 vendor "VMware", unknown product 0x07a0 rev 0x01
pci27 at ppb26 bus 27
ppb27 at pci0 dev 24 function 1 vendor "VMware", unknown product 0x07a0 rev 0x01
pci28 at ppb27 bus 28
ppb28 at pci0 dev 24 function 2 vendor "VMware", unknown product 0x07a0 rev 0x01
pci29 at ppb28 bus 29
ppb29 at pci0 dev 24 function 3 vendor "VMware", unknown product 0x07a0 rev 0x01
pci30 at ppb29 bus 30
ppb30 at pci0 dev 24 function 4 vendor "VMware", unknown product 0x07a0 rev 0x01
pci31 at ppb30 bus 31
ppb31 at pci0 dev 24 function 5 vendor "VMware", unknown product 0x07a0 rev 0x01
pci32 at ppb31 bus 32
ppb32 at pci0 dev 24 function 6 vendor "VMware", unknown product 0x07a0 rev 0x01
pci33 at ppb32 bus 33
ppb33 at pci0 dev 24 function 7 vendor "VMware", unknown product 0x07a0 rev 0x01
pci34 at ppb33 bus 34

I just try my luck to install vmwaretools without x system based on this obsolete guide : http://communities.vmware.com/message/531232?tstart=0 , ih have slightest edited for the current changes in vmware tools

Just wanted to post that I was able to get OpenBSD 4.0 working on my ESX 3.0.1 server. Others have posted information regarding OpenBSD on VMWare Server, but nobody had actually said whether or not it would work on ESX.

If you install the vmware tools per the directions below, Virtual Infrastructure Client will show the VMWare Tools with a status of OK, and you will be able to shutdown or restart the OS from the Virtual Infrastructure Client without having to login to OpenBSD.

VMWare doesn't support OpenBSD as a VM operating system. Under VMWare Server, people have gotten it to work by choosing FreeBSD as the "Guest Operating System." For some reason, ESX does not support FreeBSD like VMWare Server does.

Unfortunately the most complicated thing about this procedure is that ESX does not appear to come with a copy of the FreeBSD vmware tools. On VMWare Server, you can choose "Install VMWare Tools" from the vmware client window, mount /dev/cd0a /mnt, and see the vmware-freebsd-tools.tar.gz file. As far as I could tell, this file was not available under ESX. Therefore, to get the file, I had to download a copy of VMWare Server, do an install of OpenBSD and use the procedure above to get a copy of the file. If anyone from VMWare is listening, it would be great if you would provide a direct download for this file for your valuable ESX customers!

1. When creating your VM, set the Guest Operating System: "Other" version: "Other."

2. Use the LSI Logic SCSI type

3. Install OpenBSD, reboot and login

4. Enable FreeBSD emulation in OpenBSD by running:
sysctl -w kern.emul.freebsd=1

5. Make the freebsd emulation directories:
mkdir -p /emul/freebsd/sbin

6. Copy the vmware-freebsd-tools.tar.gz into /root. (As mentioned above, to get this file, you need to install a copy of VMWare Server and install an OpenBSD VM. More details about this here: http://www.vmware.com/community/thre...ssageID=441903)

7. Extract the VMWare tools:
tar -zxvf vmware-freebsd-tools.tar.gz -C /root

8. Manually install the vmware tools:
cp /root/vmware-tools-distrib/lib/sbin32-63/* /emul/freebsd/sbin
mkdir /etc/vmware-tools
cp /root/vmware-tools-distrib/etc/* /etc/vmware-tools

9. Update rc.local (add the following before the echo '.' line):
# VMWare Tools
if [ -x /emul/freebsd/sbin/vmtoolsd ]; then
echo -n ' vmware-tools';/emul/freebsd/sbin/vmtoolsd --background /v
ar/run/vmtoolsd.pid --halt-command "/sbin/shutdown -p -h now" & > /dev/null
fi

*Note that you can use the command line to provide the parameters for the shutdown command instead of compiling a new version of shutdown (which was recommended elsewhere).

10. If you want your VM to sync time with the ESX server on shutdown, you can shut down the VM and edit the .vmx file:
tools.syncTime="TRUE"
*Since those of us on ESX never shutdown our OpenBSD boxes (all hail vmotion!), a better option is just to enable ntp.

11. Restart the OpenBSD VM. If everything is working properly, on the VM Summary page, the tools should show as OK. You should also be able to choose "Shutdown Guest" or "Restart Guest" from the VI Client.


FYI, I also did some minimal testing with the default "Flexible" network adapter. I was able to get 13 Megabyte/sec transfer rate using FTP, which is fine for my limited usage. I understand that OpenBSD now includes a vmxnet driver, but I have no idea how to enable it on the ESX side. Whenever I edit the .vmx file to change the Ethernet0.virtualDev from "vlance" to "vmxnet", ESX simply overwrites my setting when the server starts up. If anyone has any suggestions for this, I'd be happy to hear it.

try to run with this :

/emul/freebsd/sbin/vmtoolsd --background /var/run/vmtoolsd.pid --halt-command "/sbin/shutdown -p -h now"

comes out with an error :

# /emul/freebsd/sbin/vmtoolsd 
Abort trap

gdb result :

Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (main) pending.
Starting program: /emul/freebsd/sbin/vmtoolsd 

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
You can't do that without a process to debug.

anyone can post their dmesg(vmware)?

[Edit]

From vmt(4):

vmt provides access to the host machines clock as a timedelta sensor.

That's all it can do for you.

http://www.mail-archive.com/misc@ope.../msg78455.html

so vmware tools are not so important?

[BSDfan666]

There are no tools for OpenBSD, using FreeBSD emulation doesn't sound very efficient.. there are however open source versions of the tools that could possibly be ported one day.

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

Not sure if it's maintained or not, nor how much of an effort it would be to port them.

My personal opinion is to avoid all virtualization, it's not worth the problems.. beige boxes are dirt cheap.

[There0]

Yes unfortunitly there is no port of VMTools for OpenBSD, i have tried the FreeBSD emulation mode with all the other crap many times with no real success either.

I run my virutal machine raw, it seems to perform quite well, if i do run a gui it seems to chop a bit (no copy paste or clipboard or anything) but KDE runs quite well, a lighter desktop manager like XFCE is almost unnoticable.

[There0]

Here is a dmesg and hw.sensors off a fresh install of OpenBSD 4.6 i386 into VMWorkstation 7.

[There0]

Also you can enable hardware acceleration under (right click VM) Settings -> Display it helps a bit too, the VMWare Fusion 3d accleration is MUCH improved ...

If you really are looking for performance, create a INDEPENDENT disk and make sure to ALLOCATE DISK SPACE NOW, this helped mucho in performance (I also have a VM of OS 10.6.2 running, it was a REAL headache, using a modded boot cd to boot, but it's working great, all updates and everything)

[Stellar]

Originally Posted by There0

Yes unfortunitly there is no port of VMTools for OpenBSD, i have tried the FreeBSD emulation mode with all the other crap many times with no real success either.

I run my virutal machine raw, it seems to perform quite well, if i do run a gui it seems to chop a bit (no copy paste or clipboard or anything) but KDE runs quite well, a lighter desktop manager like XFCE is almost unnoticable.

@There0
thanks for the dmesg,it seem all the same on all VM platform(vbox,vmware,qemu),all return with the same 'unknown' devices error,my finding is the vmwaretools would be usefull for the ESX or ESXI version,which they depend heavily the OS detection by vmwaretools,well iam still trying right now on ESX trial ,so my observation so far,these vmwaretools only use-full for vsphere(ESX/ESXI) users,while vmware workstation/qemu/vbox just leave out it as it is "unknwon" .(will report back after finishing test on esx).

so 3d acceleration is not only for xp directx 9.0c emulation?would be work for *nix?anything noticeable?.Ah hackintosh?hehhe did you need to modified the bios to modified the acpi?yup man about the tweaking "ALLOCATE DISK SPACE NOW" i was already did it,really makes different.

btw are you Theo de Raadt??if yes,respect to you man!!!you giving me hope to the future of humanity

[BSDfan666]

Originally Posted by Stellar

btw are you Theo de Raadt??if yes,respect to you man!!!you giving me hope to the future of humanity

No, he isn't.

[There0]

btw are you Theo de Raadt??if yes,respect to you man!!!you giving me hope to the future of humanity

Hehe, i do thank you for the compliment but i am certainly not Theo, although i do live in Canada and am not too far from Calgary, i have not seen or met Theo before.

In my language (Hellenic, what you call Greek) "Theo" means "uncle", "Theos" means "god(s)" so calling Theo uncle or god may be ok

The word "Thereo" means something a bit different, not realated to uncles or gods, and it is a "handle" not my real name

[There0]

so 3d acceleration is not only for xp directx 9.0c emulation?would be work for *nix?anything noticeable?.Ah hackintosh?hehhe did you need to modified the bios to modified the acpi?yup man about the tweaking "ALLOCATE DISK SPACE NOW" i was already did it,really makes different.

I have tried enabling 3d acceleration only for Windoz and my MacOS virtual machines, both did make a difference, (notes below on MacOS VM) Linux's i only use BackTrack livedvd, (sometimes i test iso's in VM but don't have any one i use daily). I do not use GUI's on my OpenBSD installs (most are servers), the install of OpenBSD on my laptop is on raw metal, although i can boot it from VMWare through Windoz if i need (i do have 3D enabled, not sure how much it helps in this instance though).

NOTES ON MACOS;
This setup was a bit cranky, it actually took me about 2 months for find a proper solution. The VM was actually created in Fusion 3.0 as an "experiamental" 64bit SERVER (VM for Windoz does not have that type of VM yet) and then i used the config file (.vmx) to create a Windoz VM. This included use a precreated .iso file to actually boot the VM(no BIOS mods required) similar to BOOT132 and other others. There are VMTools available for the MacOS install as well (from Fusion 3) and it's QUITE SMOOTH (especially with dedicated disk space).