[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: vmware and linuxthreads



>> 
>> Currently running natively under debian amd64 gcc-3.4. That is the
>> only reason I don't boot into 32 bit anymore. It can be done, and
>> works well.

>Really?  I only though you were using a chroot because you said so
>yourself only a month ago:

Well don't exactly remember what I posted but never could get vmware
to work in chroot because of module problems. Don't remember the
details, but someone posted here that it worked under amd64 (original
post is below that I used to setup vmware) and I finally lucked out
one day.

Below is my /etc/ld.so.conf
/emul/ia32-linux/lib
/emul/ia32-linux/usr/lib
/emul/ia32-linux/usr/X11R6/lib
/ia32/lib
/ia32/usr/lib
/ia32/usr/X11R6/lib
/ia32/usr/local/lib

I had to place the /emul first in order for the normal upgrading of
/emul directory to occur. If the /ia32 directory was first it would
not work. 

>in a chroot and making sure they appear in /etc/ld.so.conf before the
>ia32-libs versions of the same libraries.  So far this has allowed me to
>install Windows XP in vmware.  Not sure if it's a good long-term
>solution, and if Debian/ia32 every switches to NPTL I'll be up a
>creek.

I was able to install and run win200 and winxp sp2. win2000 was
unstable, so currently using winxp sp2. 

>APK, what's the output of ldd /usr/local/lib/vmware/bin/vmware?  Here's
>mine:

>        linux-gate.so.1 =>  (0x00000000)
>        libdl.so.2 => /var/chroot/sid-ia32/lib/tls/libdl.so.2 (0x55583000)
>        libm.so.6 => /var/chroot/sid-ia32/lib/tls/libm.so.6 (0x55586000)
>        libX11.so.6 => /emul/ia32-linux/usr/X11R6/lib/libX11.so.6 (0x555aa000)
>        libXext.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXext.so.6 (0x55671000)
>        libXi.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXi.so.6 (0x5567f000)
>        libgdk_pixbuf.so.2 => not found
>        libglib-1.2.so.0 => /emul/ia32-linux/usr/lib/libglib-1.2.so.0 (0x55687000)
>        libgmodule-1.2.so.0 => /emul/ia32-linux/usr/lib/libgmodule-1.2.so.0 (0x556a8000)
>        libgdk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgdk-1.2.so.0 (0x556ac000)
>        libgtk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgtk-1.2.so.0 (0x556e4000)
>        libpthread.so.0 => /var/chroot/sid-ia32/lib/tls/libpthread.so.0 (0x5582c000)
>        libc.so.6 => /var/chroot/sid-ia32/lib/tls/libc.so.6 (0x5583b000)
>        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x55555000)

Here is mine:


 ldd /usr/local/lib/vmware/bin/vmware
        linux-gate.so.1 =>  (0x00000000)
        libdl.so.2 => /ia32/lib/tls/libdl.so.2 (0x55587000)
        libm.so.6 => /ia32/lib/tls/libm.so.6 (0x5558b000)
        libX11.so.6 => /emul/ia32-linux/usr/X11R6/lib/libX11.so.6 (0x555ae000)
        libXext.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXext.so.6 (0x55675000)
        libXi.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXi.so.6 (0x55683000)
        libgdk_pixbuf.so.2 => /emul/ia32-linux/usr/lib/libgdk_pixbuf.so.2 (0x5568b000)
        libglib-1.2.so.0 => /emul/ia32-linux/usr/lib/libglib-1.2.so.0 (0x556a0000)
        libgmodule-1.2.so.0 => /emul/ia32-linux/usr/lib/libgmodule-1.2.so.0 (0x556c2000)
        libgdk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgdk-1.2.so.0 (0x556c5000)
        libgtk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgtk-1.2.so.0 (0x556fd000)
        libpthread.so.0 => /ia32/lib/tls/libpthread.so.0 (0x55845000)
        libc.so.6 => /ia32/lib/tls/libc.so.6 (0x55854000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x55555000)

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

So it is using the pthread library. I found the original message from
this list that I used to setup my system with vmware. I hope the
original author does not mind me reposting. 

***************************** Start message  **********
                            

Lennart Sorensen wrote:

>On Sun, Oct 31, 2004 at 10:38:52AM -0800, David Liontooth wrote:
>  
>
>>Thanks, Len -- I didn't realize the upgrade was free, so that's very 
>>useful.
>>It turns out the problem can't have been vmware after all, however, as the
>>same thing happened when I wasn't using it. I reverted the most recent
>>change, which was upgrading the hotplug package, and it hasn't happened
>>again, but this is not a diagnosis.
>>
>>I'll upgrade VMware anyway -- if I can run it on the amd64, that would 
>>be very cool --
>>but it would mean running a 32-bit app within a pure64 environment. My 
>>guess is
>>that VMware 4.5 won't run in our pure64 Debian -- is that correct?
>>    
>>
>
>Hmm, no idea I haven't tried vmware on 64bit myself, I just read about
>some kernel patches/driver patches for vmware related to amd64 support.
>I have found 4.5 much better than 4.0 for some things, so it's worth
>downloading the new one.  VMware seems to always consider any point
>releases to be free upgrades.
>
>I suspect if/when they release a version with full 64bit support (both
>host and guest), it will be version 5.x and require an upgrade. :)
>
>Len Sorensen
>
>
>  
>
Well, good news on that front -- vmware 4.5.2 works great on Debian
pure64, with these reservations:

  * it needs the libpopt library in /emul for smbpasswd to work
  * it may need X11 libraries in /emul too

I run vmware over a network rather than locally and needed only libpopt.
Snappy performance!  It supports 32-bit guest OSes like WinXP.

Cheers,

************************ End Message **********



Reply to: