Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Wed, Mar 05, 2008 at 02:44:12PM +0100, Ivan Voras wrote: - The only thing that VMWare tools are useful (on FreeBSD) is to get GUI features like clipboard sharing and automatic mouse focus grab in X.Org. You're right, normally you don't need vmware-tools for running FreeBSD as a guest, but: if your host is an ESX server, you need vmmemctl and the vmware-guestd for the livemigration of your virtual machine from one ESX host to another. A while ago, VMware decided to release vmware-tools as open source, maybe someone wants to take a look at it: http://open-vm-tools.sourceforge.net/ VMWare tools on Linux seem to include a driver that does something with memory management, but it's not available for FreeBSD. You don't need It is available, it's included in VMware server and also in open-vm-tools (see link above). bye, Uwe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Wednesday 05 March 2008 8:44 am, Ivan Voras wrote: Dimitri Yioulos wrote: On Tuesday 04 March 2008 12:22 pm, [EMAIL PROTECTED] wrote: It seems that everybody tries to hack around the problem...:) Does somebody know if this is a FreeBSD problem or a VMware problem and who should fix it, resp. when is a fix expected? I mean, in 6.x the VMware tools just work. That would, indeed, be good to know. Um, I've read this thread and I still don't get what is the supposed problem is here? I'm using VMWare all the time with FreeBSD since 6.0 and here are my experiences: - The only thing that VMWare tools are useful (on FreeBSD) is to get GUI features like clipboard sharing and automatic mouse focus grab in X.Org. VMWare tools on Linux seem to include a driver that does something with memory management, but it's not available for FreeBSD. You don't need VMWare Tools for the following things to work: networking, timer, X.Org GUI. - Networking is handled by the le driver (in the old versions of FreeBSD there was lnc) or the em driver. These two will work without any special configuration of FreeBSD. To use the em driver, you might need to modify the VM configuration to include ethernet0.virtualDev = e1000 or a similar appropriate line. To use the VMWare vmxnet driver (which as far as I can see isn't much different than the le driver), you need to build a kernel without the le driver first. - Timer problems can be lessened (never solved, even with vmware tools) by reducing kern.hz to something like 50 or 100 Hz (in loader.conf), and installing ntpd. - X.Org can use the generic vmware display driver which is included in the default X.Org collection of drivers. Mouse, etc. are also handled generically. Don't expect great performance, but if you're using VM technology you're used to it. Thank you, Ivan! Very insightful post on the issue. As you may know, the documentation regarding VMware Server and FreeBSD isn't great (one of the burdens we bear :-) ). It's not clear about the NIC driver at all; the installed le0 iface is working just fine as it is. I've also got the GUI working, but for the most part, it's worthless. I just thought it best to use the the included VMware Tools, as per VMware. My thanks, also, to everyone else who responded. Much appreciated. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
Dimitri Yioulos wrote: On Tuesday 04 March 2008 12:22 pm, [EMAIL PROTECTED] wrote: It seems that everybody tries to hack around the problem...:) Does somebody know if this is a FreeBSD problem or a VMware problem and who should fix it, resp. when is a fix expected? I mean, in 6.x the VMware tools just work. That would, indeed, be good to know. Um, I've read this thread and I still don't get what is the supposed problem is here? I'm using VMWare all the time with FreeBSD since 6.0 and here are my experiences: - The only thing that VMWare tools are useful (on FreeBSD) is to get GUI features like clipboard sharing and automatic mouse focus grab in X.Org. VMWare tools on Linux seem to include a driver that does something with memory management, but it's not available for FreeBSD. You don't need VMWare Tools for the following things to work: networking, timer, X.Org GUI. - Networking is handled by the le driver (in the old versions of FreeBSD there was lnc) or the em driver. These two will work without any special configuration of FreeBSD. To use the em driver, you might need to modify the VM configuration to include ethernet0.virtualDev = e1000 or a similar appropriate line. To use the VMWare vmxnet driver (which as far as I can see isn't much different than the le driver), you need to build a kernel without the le driver first. - Timer problems can be lessened (never solved, even with vmware tools) by reducing kern.hz to something like 50 or 100 Hz (in loader.conf), and installing ntpd. - X.Org can use the generic vmware display driver which is included in the default X.Org collection of drivers. Mouse, etc. are also handled generically. Don't expect great performance, but if you're using VM technology you're used to it. signature.asc Description: OpenPGP digital signature
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Wed, Mar 5, 2008 at 1:44 PM, Ivan Voras [EMAIL PROTECTED] wrote: - Timer problems can be lessened (never solved, even with vmware tools) by reducing kern.hz to something like 50 or 100 Hz (in loader.conf), and installing ntpd. Installing the VMware Tools is a very good idea for timer problems as it helps the VM catch up after the host was unable to send it interrupts fast enough. If you don't install the tools, you should run ntp instead (but never both together). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Monday 03 March 2008 2:33 pm, Michael C. Cambria wrote: Dimitri Yioulos wrote: I've followed a couple of posts in other forums (or fora, if you prefer :-) ) that suggest using the e1000 NIC driver (e.g. communities.vmware.com/message/352504), but it fails. This is the last piece I need to make work. Suggestions? What's the problem you see? All I've ever needed to do was edit my .vmx file and add: ethernet0.virtualDev = e1000 MikeC ___ So, Mike, do I do nothing with the ifconfig_le0= line in /etc/rc.conf? The post I read said to change it to ifconfig_em0= ..., but that didn't seem to work. Thanks. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Tuesday 04 March 2008 9:51 am, Dimitri Yioulos wrote: On Monday 03 March 2008 2:33 pm, Michael C. Cambria wrote: Dimitri Yioulos wrote: I've followed a couple of posts in other forums (or fora, if you prefer :-) ) that suggest using the e1000 NIC driver (e.g. communities.vmware.com/message/352504), but it fails. This is the last piece I need to make work. Suggestions? What's the problem you see? All I've ever needed to do was edit my .vmx file and add: ethernet0.virtualDev = e1000 MikeC ___ So, Mike, do I do nothing with the ifconfig_le0= line in /etc/rc.conf? The post I read said to change it to ifconfig_em0= ..., but that didn't seem to work. Thanks. Dimitri More info. - I added ethernet0.virtualDev = e1000 to the vmx file and rebooted the FBSD server. I have network connectivity, but a check of dmesg shows the following: le0: AMD PCnet-PCI port 0x1400-0x147f irq 18 at device 17.0 on pci0 So, am I not using the virtual e1000? Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
It seems that everybody tries to hack around the problem...:) Does somebody know if this is a FreeBSD problem or a VMware problem and who should fix it, resp. when is a fix expected? I mean, in 6.x the VMware tools just work. Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Tuesday 04 March 2008 12:22 pm, [EMAIL PROTECTED] wrote: It seems that everybody tries to hack around the problem...:) Does somebody know if this is a FreeBSD problem or a VMware problem and who should fix it, resp. when is a fix expected? I mean, in 6.x the VMware tools just work. Iv That would, indeed, be good to know. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
Dimitri Yioulos wrote: I've followed a couple of posts in other forums (or fora, if you prefer :-) ) that suggest using the e1000 NIC driver (e.g. communities.vmware.com/message/352504), but it fails. This is the last piece I need to make work. Suggestions? What's the problem you see? All I've ever needed to do was edit my .vmx file and add: ethernet0.virtualDev = e1000 MikeC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Thursday 28 February 2008 9:54 pm, John Nielsen wrote: On Thursday 28 February 2008 09:48:43 pm Sean Cavanaugh wrote: which version of the guest tool should I be installing for VMWare Server 1.0.4? guestd5 and guestd6 both core dump. I haven't actually tried to use any version from the ports recently, opting instead to manually use the tarball on the CD that gets inserted when you select the Install VMware Tools option in the host. JN -- From: [EMAIL PROTECTED] Sent: Thursday, February 28, 2008 9:56 AM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools) Barry Byrne wrote: I've had no problem installing the tools via the ports on 7.0 release on ESX server 3.0.1. ... cd /usr/ports/emulators/vmware-guestd6/ make clean install reboot. I was thinking about the ports. How does the ports version compare to the official coming with the VMware? Iv (Not sure if top-posting is frowned on here, but I'll follow the convention used by other lists I subscribe to, and continue this here.) Mine has been a long, strange trip in installing and making VMware Tools work on FBSD 7.0. My latest go has me installing /usr/ports/emulators/vmware-guestd6/, then the VMware-supplied tools. I've already mentioned that I had to symlink libc.so.6 to get the VMware version to run. I also had to symlink /lib/libm.so.4 to /lib/libm.so.5 in order to get vmware-toolbox to work. I've followed a couple of posts in other forums (or fora, if you prefer :-) ) that suggest using the e1000 NIC driver (e.g. communities.vmware.com/message/352504), but it fails. This is the last piece I need to make work. Suggestions? Thanks. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
I have the same issue with RC3 and with the 7.0 release. Is this VMware problem (resp. shall we expect them to fix it) or FreeBSD problem (resp. shall we wait for 7.x until it works). Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] I have the same issue with RC3 and with the 7.0 release. Is this VMware problem (resp. shall we expect them to fix it) or FreeBSD problem (resp. shall we wait for 7.x until it works). I've had no problem installing the tools via the ports on 7.0 release on ESX server 3.0.1. Get the latest freebsd.iso image from Vmware Server. And use this in the CD for the VM. Then: cd /usr/ports/emulators/vmware-guestd6/ make clean install reboot. If you want X support the use: /usr/ports/emulators/vmware-tools6 Cheers, Barry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
Barry Byrne wrote: I've had no problem installing the tools via the ports on 7.0 release on ESX server 3.0.1. ... cd /usr/ports/emulators/vmware-guestd6/ make clean install reboot. I was thinking about the ports. How does the ports version compare to the official coming with the VMware? Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
which version of the guest tool should I be installing for VMWare Server 1.0.4? guestd5 and guestd6 both core dump. -Sean -- From: [EMAIL PROTECTED] Sent: Thursday, February 28, 2008 9:56 AM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools) Barry Byrne wrote: I've had no problem installing the tools via the ports on 7.0 release on ESX server 3.0.1. ... cd /usr/ports/emulators/vmware-guestd6/ make clean install reboot. I was thinking about the ports. How does the ports version compare to the official coming with the VMware? Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
On Thursday 28 February 2008 09:48:43 pm Sean Cavanaugh wrote: which version of the guest tool should I be installing for VMWare Server 1.0.4? guestd5 and guestd6 both core dump. I haven't actually tried to use any version from the ports recently, opting instead to manually use the tarball on the CD that gets inserted when you select the Install VMware Tools option in the host. JN -- From: [EMAIL PROTECTED] Sent: Thursday, February 28, 2008 9:56 AM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools) Barry Byrne wrote: I've had no problem installing the tools via the ports on 7.0 release on ESX server 3.0.1. ... cd /usr/ports/emulators/vmware-guestd6/ make clean install reboot. I was thinking about the ports. How does the ports version compare to the official coming with the VMware? Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7RC2 and VMware tools
On Monday 18 February 2008 5:02 pm, Dimitri Yioulos wrote: On Mon, 18 Feb 2008 15:58:26 -0500, John Nielsen wrote On Monday 18 February 2008 01:47:14 pm Dimitri Yioulos wrote: On Mon, 18 Feb 2008 13:29:28 -0500, John Nielsen wrote On Monday 18 February 2008 12:31:37 pm Dimitri Yioulos wrote: On Sun, 17 Feb 2008 22:44:17 -0500, John Nielsen wrote On Sunday 17 February 2008 01:06:28 pm Dimitri Yioulos wrote: I'm not sure whether to have posted this here or on a VMware list; apologies if I'm in the wrong place. The other day, I did a fresh install of v. 7RC2 from the minimal CD on a CentOS 5.1 box running VMware server 1.0.4. I had previously successfully installed v. 6.2, and upgraded to 6.3 on the same box. All has gone well, except for the installation of VMware Tools. Getting the Tools tarball and extracting the requisite files was trivial. However, when I try to run Vmware-Config-Tools.pl, I get a message saying that the program must be run on a virtual machine. Well, it is. Is there a needed FBSD package I'm missing (the Tools install program doesn't complain about it). A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. I just went through almost the same thing, installing FreeBSD 7 under VMware Workstation on Windows. The config-tools script has a hard-coded version check which looks for libc.so.6 under /lib only. Rather than mess with the script, I just hard-linked the library from /usr/local/lib/compat (where it was installed by the compat6x port). Seemed to work fine after that. You'll need to be careful not to erase it if you ever run make delete-old-libs, though. Thanks for the response! A symlink won't do for the above? Try it and see! I think I decided on a hard link since the script uses something like if [ -f /lib/libc.so.6 ] so it's looking only for a regular file and not a symlink. Hmm, when I try to hard-link (ln /usr/compat/linux/lib/libc.so.6 libc.so.6), I get ln: ./libc.so.6: Cross-device link. But, when I do a symlink, which takes, I get /usr/libexec/ld-elf.so.1: Shared object ld-linux.so.2 not found, required by libc.so.6 when i run vmware-config-tools.pl. So, I symlink ld-linux.so.2, and run tools. Then, I get /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. Arrgh. Any other ideas? You have /usr on a different partition than / in your VM, so you can't do a hard link. I would just copy the file back to /lib and not worry about it. Linking in other random libraries will cause problems, as you've observed. JN If I copy libc.so.6 to /lib, then tools complains about ld-linux.so.2. If I copy ld-linux.so.2, it then complains about /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. This is pretty much the same as if I symlink the two files. Even though I'm a glass half-full guy, this is beginning to look dire (but it's the worst thing to happen to me, I'm sure I'll live). Still, it would be nice to get this working. I did this a few days ago: /lib/libc.so. existed. I symlinked libc.so.6 to it. I then proceeded to install VMware Tools without complaint. However, I'm not sure if there's a vmware FreeBSD NIC driver. If there is, it's not being used (as per dmesg, the AMD PCnet-PCI driver appears to be used). On a Linux vm (please, no stone throwing :-) ), to use the vmxnet driver, I'd stop the network service, load the vmxnet driver module, then restart the service. Is there a similar procedure on FreeBSD? Thanks. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7RC2 and VMware tools
On Wednesday 27 February 2008 11:14:26 am Dimitri Yioulos wrote: On Monday 18 February 2008 5:02 pm, Dimitri Yioulos wrote: On Mon, 18 Feb 2008 15:58:26 -0500, John Nielsen wrote On Monday 18 February 2008 01:47:14 pm Dimitri Yioulos wrote: On Mon, 18 Feb 2008 13:29:28 -0500, John Nielsen wrote On Monday 18 February 2008 12:31:37 pm Dimitri Yioulos wrote: On Sun, 17 Feb 2008 22:44:17 -0500, John Nielsen wrote On Sunday 17 February 2008 01:06:28 pm Dimitri Yioulos wrote: I'm not sure whether to have posted this here or on a VMware list; apologies if I'm in the wrong place. The other day, I did a fresh install of v. 7RC2 from the minimal CD on a CentOS 5.1 box running VMware server 1.0.4. I had previously successfully installed v. 6.2, and upgraded to 6.3 on the same box. All has gone well, except for the installation of VMware Tools. Getting the Tools tarball and extracting the requisite files was trivial. However, when I try to run Vmware-Config-Tools.pl, I get a message saying that the program must be run on a virtual machine. Well, it is. Is there a needed FBSD package I'm missing (the Tools install program doesn't complain about it). A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. I just went through almost the same thing, installing FreeBSD 7 under VMware Workstation on Windows. The config-tools script has a hard-coded version check which looks for libc.so.6 under /lib only. Rather than mess with the script, I just hard-linked the library from /usr/local/lib/compat (where it was installed by the compat6x port). Seemed to work fine after that. You'll need to be careful not to erase it if you ever run make delete-old-libs, though. Thanks for the response! A symlink won't do for the above? Try it and see! I think I decided on a hard link since the script uses something like if [ -f /lib/libc.so.6 ] so it's looking only for a regular file and not a symlink. Hmm, when I try to hard-link (ln /usr/compat/linux/lib/libc.so.6 libc.so.6), I get ln: ./libc.so.6: Cross-device link. But, when I do a symlink, which takes, I get /usr/libexec/ld-elf.so.1: Shared object ld-linux.so.2 not found, required by libc.so.6 when i run vmware-config-tools.pl. So, I symlink ld-linux.so.2, and run tools. Then, I get /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. Arrgh. Any other ideas? You have /usr on a different partition than / in your VM, so you can't do a hard link. I would just copy the file back to /lib and not worry about it. Linking in other random libraries will cause problems, as you've observed. JN If I copy libc.so.6 to /lib, then tools complains about ld-linux.so.2. If I copy ld-linux.so.2, it then complains about /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. This is pretty much the same as if I symlink the two files. Even though I'm a glass half-full guy, this is beginning to look dire (but it's the worst thing to happen to me, I'm sure I'll live). Still, it would be nice to get this working. I did this a few days ago: /lib/libc.so. existed. I symlinked libc.so.6 to it. I then proceeded to install VMware Tools without complaint. However, I'm not sure if there's a vmware FreeBSD NIC driver. If there is, it's not being used (as per dmesg, the AMD PCnet-PCI driver appears to be used). On a Linux vm (please, no stone throwing :-) ), to use the vmxnet driver, I'd stop the network service, load the vmxnet driver module, then restart the service. Is there a similar procedure on FreeBSD? FreeBSD 7 handles the NIC with the le(4) driver, which is built in to the GENERIC kernel by default. In order for the hardware to be available for the vmxnet driver to attach to, le needs to be disabled. I would do this by building a custom kernel that doesn't include it, but it may also be possible using device.hints. Once you're able to boot without another driver attaching to the hardware, you should be able to load the vmxnet module and have it see the hardware. If it's available and will work with 7.0, that is.. I've been happy enough with re(4) that I haven't gone that route myself. Further, 64-bit VM's use an e1000 NIC which is supported by the em driver. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7RC2 and VMware tools
On Mon, 18 Feb 2008 13:29:28 -0500, John Nielsen wrote On Monday 18 February 2008 12:31:37 pm Dimitri Yioulos wrote: On Sun, 17 Feb 2008 22:44:17 -0500, John Nielsen wrote On Sunday 17 February 2008 01:06:28 pm Dimitri Yioulos wrote: I'm not sure whether to have posted this here or on a VMware list; apologies if I'm in the wrong place. The other day, I did a fresh install of v. 7RC2 from the minimal CD on a CentOS 5.1 box running VMware server 1.0.4. I had previously successfully installed v. 6.2, and upgraded to 6.3 on the same box. All has gone well, except for the installation of VMware Tools. Getting the Tools tarball and extracting the requisite files was trivial. However, when I try to run Vmware-Config-Tools.pl, I get a message saying that the program must be run on a virtual machine. Well, it is. Is there a needed FBSD package I'm missing (the Tools install program doesn't complain about it). A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. I just went through almost the same thing, installing FreeBSD 7 under VMware Workstation on Windows. The config-tools script has a hard-coded version check which looks for libc.so.6 under /lib only. Rather than mess with the script, I just hard-linked the library from /usr/local/lib/compat (where it was installed by the compat6x port). Seemed to work fine after that. You'll need to be careful not to erase it if you ever run make delete-old-libs, though. Thanks for the response! A symlink won't do for the above? Try it and see! I think I decided on a hard link since the script uses something like if [ -f /lib/libc.so.6 ] so it's looking only for a regular file and not a symlink. JN -- Hmm, when I try to hard-link (ln /usr/compat/linux/lib/libc.so.6 libc.so.6), I get ln: ./libc.so.6: Cross-device link. But, when I do a symlink, which takes, I get /usr/libexec/ld-elf.so.1: Shared object ld-linux.so.2 not found, required by libc.so.6 when i run vmware-config-tools.pl. So, I symlink ld-linux.so.2, and run tools. Then, I get /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. Arrgh. Any other ideas? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7RC2 and VMware tools
On Monday 18 February 2008 01:47:14 pm Dimitri Yioulos wrote: On Mon, 18 Feb 2008 13:29:28 -0500, John Nielsen wrote On Monday 18 February 2008 12:31:37 pm Dimitri Yioulos wrote: On Sun, 17 Feb 2008 22:44:17 -0500, John Nielsen wrote On Sunday 17 February 2008 01:06:28 pm Dimitri Yioulos wrote: I'm not sure whether to have posted this here or on a VMware list; apologies if I'm in the wrong place. The other day, I did a fresh install of v. 7RC2 from the minimal CD on a CentOS 5.1 box running VMware server 1.0.4. I had previously successfully installed v. 6.2, and upgraded to 6.3 on the same box. All has gone well, except for the installation of VMware Tools. Getting the Tools tarball and extracting the requisite files was trivial. However, when I try to run Vmware-Config-Tools.pl, I get a message saying that the program must be run on a virtual machine. Well, it is. Is there a needed FBSD package I'm missing (the Tools install program doesn't complain about it). A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. I just went through almost the same thing, installing FreeBSD 7 under VMware Workstation on Windows. The config-tools script has a hard-coded version check which looks for libc.so.6 under /lib only. Rather than mess with the script, I just hard-linked the library from /usr/local/lib/compat (where it was installed by the compat6x port). Seemed to work fine after that. You'll need to be careful not to erase it if you ever run make delete-old-libs, though. Thanks for the response! A symlink won't do for the above? Try it and see! I think I decided on a hard link since the script uses something like if [ -f /lib/libc.so.6 ] so it's looking only for a regular file and not a symlink. Hmm, when I try to hard-link (ln /usr/compat/linux/lib/libc.so.6 libc.so.6), I get ln: ./libc.so.6: Cross-device link. But, when I do a symlink, which takes, I get /usr/libexec/ld-elf.so.1: Shared object ld-linux.so.2 not found, required by libc.so.6 when i run vmware-config-tools.pl. So, I symlink ld-linux.so.2, and run tools. Then, I get /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. Arrgh. Any other ideas? You have /usr on a different partition than / in your VM, so you can't do a hard link. I would just copy the file back to /lib and not worry about it. Linking in other random libraries will cause problems, as you've observed. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7RC2 and VMware tools
On Mon, 18 Feb 2008 15:58:26 -0500, John Nielsen wrote On Monday 18 February 2008 01:47:14 pm Dimitri Yioulos wrote: On Mon, 18 Feb 2008 13:29:28 -0500, John Nielsen wrote On Monday 18 February 2008 12:31:37 pm Dimitri Yioulos wrote: On Sun, 17 Feb 2008 22:44:17 -0500, John Nielsen wrote On Sunday 17 February 2008 01:06:28 pm Dimitri Yioulos wrote: I'm not sure whether to have posted this here or on a VMware list; apologies if I'm in the wrong place. The other day, I did a fresh install of v. 7RC2 from the minimal CD on a CentOS 5.1 box running VMware server 1.0.4. I had previously successfully installed v. 6.2, and upgraded to 6.3 on the same box. All has gone well, except for the installation of VMware Tools. Getting the Tools tarball and extracting the requisite files was trivial. However, when I try to run Vmware-Config-Tools.pl, I get a message saying that the program must be run on a virtual machine. Well, it is. Is there a needed FBSD package I'm missing (the Tools install program doesn't complain about it). A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. I just went through almost the same thing, installing FreeBSD 7 under VMware Workstation on Windows. The config-tools script has a hard-coded version check which looks for libc.so.6 under /lib only. Rather than mess with the script, I just hard-linked the library from /usr/local/lib/compat (where it was installed by the compat6x port). Seemed to work fine after that. You'll need to be careful not to erase it if you ever run make delete-old-libs, though. Thanks for the response! A symlink won't do for the above? Try it and see! I think I decided on a hard link since the script uses something like if [ -f /lib/libc.so.6 ] so it's looking only for a regular file and not a symlink. Hmm, when I try to hard-link (ln /usr/compat/linux/lib/libc.so.6 libc.so.6), I get ln: ./libc.so.6: Cross-device link. But, when I do a symlink, which takes, I get /usr/libexec/ld-elf.so.1: Shared object ld-linux.so.2 not found, required by libc.so.6 when i run vmware-config-tools.pl. So, I symlink ld-linux.so.2, and run tools. Then, I get /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. Arrgh. Any other ideas? You have /usr on a different partition than / in your VM, so you can't do a hard link. I would just copy the file back to /lib and not worry about it. Linking in other random libraries will cause problems, as you've observed. JN If I copy libc.so.6 to /lib, then tools complains about ld-linux.so.2. If I copy ld-linux.so.2, it then complains about /usr/libexec/ld-elf.so.1: Undefined symbol __stdoutp referenced from COPY relocation in /usr/local/sbin/vmware-checkvm. This is pretty much the same as if I symlink the two files. Even though I'm a glass half-full guy, this is beginning to look dire (but it's the worst thing to happen to me, I'm sure I'll live). Still, it would be nice to get this working. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7RC2 and VMware tools
On Sunday 17 February 2008 01:06:28 pm Dimitri Yioulos wrote: I'm not sure whether to have posted this here or on a VMware list; apologies if I'm in the wrong place. The other day, I did a fresh install of v. 7RC2 from the minimal CD on a CentOS 5.1 box running VMware server 1.0.4. I had previously successfully installed v. 6.2, and upgraded to 6.3 on the same box. All has gone well, except for the installation of VMware Tools. Getting the Tools tarball and extracting the requisite files was trivial. However, when I try to run Vmware-Config-Tools.pl, I get a message saying that the program must be run on a virtual machine. Well, it is. Is there a needed FBSD package I'm missing (the Tools install program doesn't complain about it). A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. I just went through almost the same thing, installing FreeBSD 7 under VMware Workstation on Windows. The config-tools script has a hard-coded version check which looks for libc.so.6 under /lib only. Rather than mess with the script, I just hard-linked the library from /usr/local/lib/compat (where it was installed by the compat6x port). Seemed to work fine after that. You'll need to be careful not to erase it if you ever run make delete-old-libs, though. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
