I dug a little deeper, vmxnet driver is not found in the vmware-tools
distribution for Solaris 10:
bash-3.00# pwd
/usr/lib/vmware-tools/modules/binary
bash-3.00# ls *
10:
vmmemctl vmmemctl.conf

10_64:
vmmemctl vmmemctl.conf

9:
vmmemctl vmmemctl.conf vmxnet
bash-3.00#

So how do we get Solaris 10 to use vmxnet????


Alan Boon Chia Kong/NETS wrote on 07/09/2007 09:40:53:

> Hi Dirk,
>
> Can I force 64-bit Solaris to use the vmxnet drivers? How do I check
> what type of drivers I'm using?
> ifconfig -a shows:
> bash-3.00# ifconfig -a
> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> mtu 8232 index 1
>         inet 127.0.0.1 netmask ff000000
> e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 2
>         inet 192.168.16.21 netmask ffffff00 broadcast 192.168.16.255
>         ether 0:50:56:82:71:fa
> e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 3
>         inet 192.168.20.21 netmask ffffff00 broadcast 192.168.20.255
>         ether 0:50:56:82:5f:18
>
> Thanks.
>
> Regards,
> Alan
>
> [EMAIL PROTECTED] wrote on 07/09/2007 05:08:08:
>
> > Hi Alan,
> >
> > I had similar problems with S10 running as VM. Then I figured out that
> > some of the problems were due to the network driver.
> >
> > One reason for this is that the network driver for Solaris 64bit is not

> > replaced by the vmxnet of vmware. In 32 bit mode this actually happens
> > and the performance is much better. Unfortunately 64-bit mode is
> > automatically selected, if the host is supporting it. Forcing 32-bit
> > mode can be done though.
> >
> > Check out this article for more info:
> > http://kb.vmware.com/selfservice/microsites/search.do?
> > cmd=displayKC&externalId=1975
> >
> > -Dirk
> >
> >
> > [EMAIL PROTECTED] wrote:
> > > Hi,
> > >
> > > I am running 2x Solaris 10 x86 64-bit VM in 2 ESX 3.0.1
> separately and SRSS
> > > 3.1 are installed in the Solaris VM. The 2 Solaris VM is running at
100%
> > > CPU load as reported by the Virtual Centre. I am trying to find out
what
> > > process is causing the problem. At first, we thought we didn't add
enough
> > > users. So we used bbmkuser to add more than what I have deployed so
far.
> > > And my SunRay sessions are not using dtsession, so the memory
utilisation
> > > is very low at the moment (abt 500MB Guest memory usage). They have 2
> > > critical apps running - windows connector (with the virtual keyboard
> > > running to provide screen lock upon card removal) and usbdisk. The
Sunray
> > > server should be acting as a pass-thru connector to the windows vm.
> > >
> > > It was so bad last night that the screen-lock script within the
> > > windows_connector script didn't work, and tt took a long time between
card
> > > insertion to presenting the desktop VM. After reboot, the scriptis
working
> > > again.
> > >
> > > ESX servers: 2x IBM X3650 with 24GB RAM each and 2x quad-core E5320
per
> > > server.
> > >
> > > Any idea what's happening?
> > > Thanks for the help.
> > >
> > > Regards,
> > > Alan
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
********************************************************************************

> > >
> > > IMPORTANT NOTICE:  This email and any files transmitted with  it is
> > > intended only for  the use of the person(s) to whom it is addressed,
and
> > > may  contain information that is privileged, confidential and exempt
from
> > > disclosure under applicable law. If you are not the intended
recipient,
> > > please immediately notify the sender and delete  the email. Thank
you.
> > >
> >
>
********************************************************************************

> > >
> > > _______________________________________________
> > > SunRay-Users mailing list
> > > [email protected]
> > > http://www.filibeto.org/mailman/listinfo/sunray-users
> >
> > _______________________________________________
> > SunRay-Users mailing list
> > [email protected]
> > http://www.filibeto.org/mailman/listinfo/sunray-users

> >
***************************************************************************
> >   IMPORTANT NOTICE:
> > This email and any files transmitted with it is intended only for
> > the use of the person(s) to whom it is addressed, and may
> > contain information that is privileged, confidential and exempt
> > from disclosure under applicable law. If you are not the intended
> > recipient, please immediately notify the sender and delete
> > the email. Thank you.
> >
***************************************************************************
>
***************************************************************************
>   IMPORTANT NOTICE:
> This email and any files transmitted with it is intended only for
> the use of the person(s) to whom it is addressed, and may
> contain information that is privileged, confidential and exempt
> from disclosure under applicable law. If you are not the intended
> recipient, please immediately notify the sender and delete
> the email. Thank you.
>
***************************************************************************



********************************************************************************

IMPORTANT NOTICE:  This email and any files transmitted with  it is
intended only for  the use of the person(s) to whom it is addressed,  and
may  contain information that is privileged, confidential and exempt from
disclosure under applicable law. If you are not the intended recipient,
please immediately notify the sender and delete  the email. Thank you.
********************************************************************************

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to