Has anyone done this and what are your experiences. Positive and negative.
Thanks very much,
Jeff
My advice would be to run D3/Linux instead ... works fine, and far
more stable overall (I'm talking D3 generally, rather than something
specifice with vmware
Provided you understand that CURRENTLY Tiger Logic don't officially
support D3 in virtualized environments I wouldn't imagine you would
have any problems
I have a client that has been running d3 on vmware for a few years.
their production server is 90+ users. they run their development
machine and some test servers - all virtually. they have not
experienced any vmware-to-d3 issues. They are big fans of vmware
********
Ross, you (and others) may be interested to know that I had a conversation
with Robert Burke at TL just a few days ago and he confirmed that they DO
support vmware on the current releases of D3 Windows (that was my specific
inquiry).
He also was very encouraging and supportive of our efforts to move in that
direction. He did go into detail about how TL is embracing this technology
(also why they waited) and I would encourage others to make similar
inquiries, if interested.
Also, after speaking with Robert, my impression of TL, their technical
expertise, their understanding of the current IT environments, and their
desire to support their VARs and users has taken a significant turn for the
better.
Jeff
Didn't realize that the current release was supported, but was aware
that one of the features of D3 9 was going to be virtualization
support.
Also nice to know TL changes are obvious to anyone that bothers to
contact them NOW, rather than relaying ancient histories :-)
Be aware that there does exist a problem with RH/CentOS 5.3 on vmware
where sleeping d3 processes go into permanent sleeping beauty mode
(i.e. spooler, etc). Apparently fixed in RH/CentOS 5.4 but the 5.3
fix can be found here:
Below is a sample from a CentOS system but RedHat is the same.
The change is the ......divider=10 clocksource=acpi_pm.... portion in /
boot/grub/grub.conf
[root@d3server root]# more /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-164.el5PAE)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.el5PAE ro root=/dev/VolGroup00/LogVol00
rhgb quiet divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-164.el5PAE.img
title CentOS (2.6.18-128.el5PAE)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.el5PAE ro root=/dev/VolGroup00/LogVol00
rhgb quiet divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-128.el5PAE.img
[root@d3server root]#