http://frogger974.homelinux.org/ http://os.newsforge.com/article.pl?sid=06/08/24/1828235&from=rss Using SCSI Disk (/dev/sd0c) LSI Logic SCSI controller (this is a change from the default BusLogic controller) Using IDE Disk (/dev/wd0c) Works fine but is not portable to ESX server... Install the VMware-Tools (FreeBSD Tools) Note: This assumes you setup OpenBSD as FreeBSD Guest, if you did not, you can get the FreeBSD VMware tools by going to the VMware install directory and finding the freebsd.iso image, copy to the OpenBSD installation and substitute in the directions below accordingly... Enable FreeBSD emulation by issuing: sysctl -w kern.emul.freebsd=1 Make this setting permanent by uncommenting the appropriate line in /etc/sysctl.conf. Select Install VMware Tools... on the VM menu; this creates a virtual CD-ROM image which is accessible from the VM and includes a tarball with vmware-tools for FreeBSD. From that tarball we need to install the vmware-guestd daemon, which triggers events sent for the host computer and runs commands accordingly -- such as halt and reboot -- on the guest OS. Run the following commands to mount that image and install the daemon and its configuration: mount /dev/cd0c /mnt tar -zxvpf /mnt/vmware-freebsd-tools.tar.gz -C /tmp mkdir -p /emul/freebsd/sbin install -m 555 -o root -g wheel \ /tmp/vmware-tools-distrib/lib/sbin32/vmware-guestd /emul/freebsd/sbin cp -r /tmp/vmware-tools-distrib/etc /etc/vmware-tools rm -rf /tmp/vmware-tools-distrib umount /mnt Start the daemon with: /emul/freebsd/sbin/vmware-guestd --background /var/run/vmware-guestd.pid \ --halt-command "/sbin/shutdown -p -h now" To have it started on boot add the following lines to your /etc/rc.local file just before the echo '.' line: if [ -x /emul/freebsd/sbin/vmware-guestd ]; then echo -n ' vmware-tools' /emul/freebsd/sbin/vmware-guestd --background /var/run/vmware-guestd.pid \ --halt-command "/sbin/shutdown -p -h now" fi Now you can shut down the VM and check its status from the VMware Web-based management interface or console and have it halt and power off properly. You may have to shutdown the VM and edit the configuration options for shutdown and restart, edit -> options -> power -> power controls: stop -> shutdown guest (not power off) restart -> restart guest (not restart) Modify shutdown as shutdown from the OpenBSD tools will only halt the machine (this does not seem to be the case with OpenBSD 4x): Download source code for shutdown: cd /usr cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs get src/sbin/shutdown Modify shutdown so that -h is the same as -hp: cd /usr/src/sbin/shutdown nano shutdown.c after line 141, on line 142: add dopower = 1; save, exit make Move old shutdown: mv /sbin/shutdown /sbin/shutdown.old Move new shutdown in place: mv /usr/src/sbin/shutdown/shutdown /sbin Test shutdown the system: shutdown -h now While the system is powered down, modify the .vmx file: tools.syncTime="TRUE" OpenBSD pcn0 Driver Issue Resolved (Unknown Author) How to disable the pcn driver and revert to the older le driver (<=3.8). o Boot from the OpenBSD 3.8 boot CD image (I pointed the virtual CD-ROM drive in the VM directly to the corresponding ISO image). o At the OpenBSD “boot>” prompt, type -c and press Enter. This takes you into User Kernel Config, or UKC. o At the UKC prompt, type “disable pcn” to disable the pcn driver. o Type “quit” at the next UKC prompt to exit the kernel config and proceed with the boot process. If you watch the boot process, you will see OpenBSD load the le driver and identify the virtual NIC as le1. o That’s all well and good, but how do you make the changes stick between reboots? Here’s how: o Once you’ve gotten OpenBSD fully installed and are rebooting for the first time after installation, follow the steps above to use the le driver for the next reboot. o Use the “config -e -o nbsd bsd” command (see the relevant man page for details) to modify the kernel again, only this time saving the changes to the file named “nbsd”. o Upon the next reboot after using the config command to create a new kernel file, specify the name of that new kernel file (“nbsd” in our example here) at the OpenBSD “boot>” prompt. o Assuming that everything works OK (it did for me), rename the original kernel to “bsd.original” and rename your new kernel to just “bsd”. Then, upon the next reboot, the pcn driver should be disabled and everything should work just fine. o Using this process, I now have two OpenBSD 3.8 VMs running and haven’t experienced any issues. Now, on to installing ClamAV on OpenBSD….(more details soon) Error Notes (internal) Warning: Unable to start hgfs Working with VMware shared folders (/mnt/hgfs) http://www.vmware.com/support/ws4/doc/running_sharefold_ws.html In Linux, the shared folder should show up in: /mnt/hgfs Warning: Unable to start hgfs. vmware-guestd Warning: Unable to start hgfs. vmware-guestd does indeed start, but /mnt/hgfs has not been mounted. Warning: Error in the RPC receive loop: RpcIn: Unable to send.