VMware tools for FreeBSD
Hi, I am running an ESXi 5.1 VMware server, with one FreeBSD (8.3) guest. I am trying to figure how to install the VMware tools: - the linux one are working, but I woul prefere a more native FreeBSD - should I install /usr/ports/emulators/vmware-guest6d ? It fails with not finding vmware-guestd. - should I install /usr/ports/emulators/vmware-tools6 ? It seems it needs vmware-guest6d as a prerequisite. What else? All documentation I find on the web refers to a VMwareTools for FreeBSD, that I could not locate. Help please. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VMware tools for FreeBSD
If this is a production server operation VMWare will *only* support you running their list of supported FreeBSD versions and their official VMWare Tools. This means you'll often be left behind several releases with the most recent available being completely abandoned by the FreeBSD project. It's a sad situation that they call this supported. If you really don't have any concerns about that what you want is emulators/open-vm-tools or emulators/open-vm-tools-nox11 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: VMware tools for FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/8/13 7:09 AM, Olivier Nicole wrote: Hi, I am running an ESXi 5.1 VMware server, with one FreeBSD (8.3) guest. I am trying to figure how to install the VMware tools: - the linux one are working, but I woul prefere a more native FreeBSD - should I install /usr/ports/emulators/vmware-guest6d ? It fails with not finding vmware-guestd. - should I install /usr/ports/emulators/vmware-tools6 ? It seems it needs vmware-guest6d as a prerequisite. What else? All documentation I find on the web refers to a VMwareTools for FreeBSD, that I could not locate. Help please. Olivier Hi Olivier, If you want to install the official VMware guest tools for FreeBSD, check pages 25-26 in this document: http://www.vmware.com/pdf/vmware-tools-installation-configuration.pdf If you have any further questions, please reply here and we'll go from there. Best of luck, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGKPtoACgkQ0sRouByUApAhsQCfTH77ZqtdqEpqBNc9brUyUwW8 j/0An3Ho9UW8u+Yp2pTEqnwUzjkiejS1 =r8zT -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installing VMware Tools on FreeBSD 9, amd64
I've installed the compat6x libraries and made a symlink to /lib for libc.so.6 as per some docs I found; however, the vmware tools installation is still failing with: Unable to copy the source file /usr/local/lib/vmware-tools/modules/binary/FreeBSD8.0-amd64/vmxnet.ko to the destination file /boot/modules/vmxnet.ko. The reason being is that /usr/local/lib/vmware-tools/modules/binary/ only contains: FreeBSD6.0-amd64FreeBSD6.0-i386FreeBSD7.0-amd64 FreeBSD7.0-i386 Is this a bug in the vmware install script or have I missed something--or can I use a different option? Thing is, I'm on 9.0 RELEASE. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
vmware-tools-freebsd No drivers for x.org version: 7.6.5.
Hello, I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and I tried to install the vmware-tools-freebsd of VMware to get the driver for Xorg, but it seems that X.org 7.6.5. is not supported. My other VM runs a 8-CURRENT with X.org 7.4_1 which works fine. Any idea how to solve this? Should I go back to X.org 7.4_1 in 9-CURRENT? Or should I fake the vmware-tools installer to see X.org as /.4 while it is 7.6.5? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vmware-tools-freebsd No drivers for x.org version: 7.6.5.
On 2011-04-08 10:42, Matthias Apitz wrote: I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and I tried to install the vmware-tools-freebsd of VMware to get the driver for Xorg, but it seems that X.org 7.6.5. is not supported. My other VM runs a 8-CURRENT with X.org 7.4_1 which works fine. Any idea how to solve this? Should I go back to X.org 7.4_1 in 9-CURRENT? Or should I fake the vmware-tools installer to see X.org as /.4 while it is 7.6.5? X.org 7.5 already has VMware drivers, so you can just install the x11-drivers/xf86-input-vmmouse and x11-drivers/xf86-video-vmware ports. Alternatively, run make config in x11-drivers/xorg-drivers, check the VMMOUSE and VMWARE entries, and rebuild this meta-port. Btw, I have no idea why these drivers are not enabled by default. They would seem very useful in a default X.org installation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vmware-tools-freebsd No drivers for x.org version: 7.6.5.
On 08/04/2011 12:17, Dimitry Andric wrote: On 2011-04-08 10:42, Matthias Apitz wrote: I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and I tried to install the vmware-tools-freebsd of VMware to get the driver for Xorg, but it seems that X.org 7.6.5. is not supported. My other VM runs a 8-CURRENT with X.org 7.4_1 which works fine. Any idea how to solve this? Should I go back to X.org 7.4_1 in 9-CURRENT? Or should I fake the vmware-tools installer to see X.org as /.4 while it is 7.6.5? X.org 7.5 already has VMware drivers, so you can just install the x11-drivers/xf86-input-vmmouse and x11-drivers/xf86-video-vmware ports. Alternatively, run make config in x11-drivers/xorg-drivers, check the VMMOUSE and VMWARE entries, and rebuild this meta-port. Btw, I have no idea why these drivers are not enabled by default. They would seem very useful in a default X.org installation. Probably because a lot of people do not use VMware products. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vmware-tools-freebsd No drivers for x.org version: 7.6.5.
El día Friday, April 08, 2011 a las 12:17:03PM +0200, Dimitry Andric escribió: On 2011-04-08 10:42, Matthias Apitz wrote: I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and I tried to install the vmware-tools-freebsd of VMware to get the driver for Xorg, but it seems that X.org 7.6.5. is not supported. My other VM runs a 8-CURRENT with X.org 7.4_1 which works fine. Any idea how to solve this? Should I go back to X.org 7.4_1 in 9-CURRENT? Or should I fake the vmware-tools installer to see X.org as /.4 while it is 7.6.5? X.org 7.5 already has VMware drivers, so you can just install the x11-drivers/xf86-input-vmmouse and x11-drivers/xf86-video-vmware ports. Alternatively, run make config in x11-drivers/xorg-drivers, check the VMMOUSE and VMWARE entries, and rebuild this meta-port. Dimitry, Thanks for your kind fast answer; does this also mean that I could completely get rid of the VMware' vmware-tools-freebsd? I'm using on the 8-CURRENT system the emulators/open-vom-tools and will install them in the 9-CURRENT too. Thanks again matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vmware-tools-freebsd No drivers for x.org version: 7.6.5.
On Apr 8, 2011, at 5:03 AM, Matthias Apitz g...@unixarea.de wrote: El día Friday, April 08, 2011 a las 12:17:03PM +0200, Dimitry Andric escribió: On 2011-04-08 10:42, Matthias Apitz wrote: I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and I tried to install the vmware-tools-freebsd of VMware to get the driver for Xorg, but it seems that X.org 7.6.5. is not supported. My other VM runs a 8-CURRENT with X.org 7.4_1 which works fine. Any idea how to solve this? A co-worker and I recently went through this. Seems the trick is to install xf86-video-vmware-10.16.9 (we are using 8.1-RELEASE), then re-run the vmware-config.pl file that you un-packed from the vmware-tools tarball, then run X -configure (as root), then copy /root/xorg.conf.new to /etc/X11/xorg.conf (making appropriate backups first, of course). We were able to achieve 1600x1200 resolution. -- Devin Should I go back to X.org 7.4_1 in 9-CURRENT? Or should I fake the vmware-tools installer to see X.org as /.4 while it is 7.6.5? X.org 7.5 already has VMware drivers, so you can just install the x11-drivers/xf86-input-vmmouse and x11-drivers/xf86-video-vmware ports. Alternatively, run make config in x11-drivers/xorg-drivers, check the VMMOUSE and VMWARE entries, and rebuild this meta-port. Dimitry, Thanks for your kind fast answer; does this also mean that I could completely get rid of the VMware' vmware-tools-freebsd? I'm using on the 8-CURRENT system the emulators/open-vom-tools and will install them in the 9-CURRENT too. Thanks again matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vmware tools for ESX Server 3.5
On Sep 3, 2008, at 12:11 PM, John Nielsen wrote: On Wednesday 03 September 2008, B. Cook wrote: I am setting up FreeBSD 7.0 and he is asking about the vmware-tools. Ports has some things, but I am not sure what I need, and neither is he. Can anyone tell me what it needs? I usually create VM's with the Intel gigabit vNIC's which can use FreeBSD's em driver. Since Xorg includes the vmmouse and vmware video drivers already, the main things you should be looking for are the memory balloon driver and the guestd service. In the past I have gotten these to work by using the supplied tools (on the CD image that is inserted when you select Install VMware tools from the host). However it is much easier nowadays to use the free version in ports/emulators/open-vm-tools (or open-vm-tools-nox11). JN Well this is the other way.. FreeBSD is the guest not the host. This is what the owner of the cluster is telling me: The tools aren't absolutely necessary but if we can we always install them in guest machines. They allow the VMWare server to gracefully shutdown the guest, improve memory management, replace the virtual NIC with a higher performance one, replace the video driver (if you are running a GUI which we aren't in this case.) etc But this machine is running fine, including the nightly snapshots. Below is the dmesg from the guest: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE-p2 #0: Fri Jul 11 15:42:07 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (2992.58-MHz 686- class CPU) Origin = GenuineIntel Id = 0x10678 Stepping = 8 Features = 0xfebfbff FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS Features2=0x82211SSE3,DS_CPL,SSSE3,CX16,b19 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF real memory = 536870912 (512 MB) avail memory = 511385600 (487 MB) ACPI APIC Table: PTLTD APIC MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jul 11 2008 15:39:33) acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1050-0x105f at device 7.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: bridge at device 7.3 (no driver attached) vgapci0: VGA-compatible display port 0x1060-0x106f mem 0xf800-0xfbff,0xf400-0xf47f at device 15.0 on pci0 mpt0: LSILogic 1030 Ultra4 Adapter port 0x1080-0x10ff mem 0xf480-0xf4800fff irq 17 at device 16.0 on pci0 mpt0: [ITHREAD] mpt0: MPI Version=1.2.0.0 le0: AMD PCnet-PCI port 0x1400-0x147f irq 18 at device 17.0 on pci0 le0: 16 receive buffers, 4 transmit buffers le0: Ethernet address: 00:50:56:83:49:9d le0: [ITHREAD] acpi_acad0: AC Adapter on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xca000-0xcafff, 0xdc000-0xd,0xe-0xe3fff pnpid ORM on isa0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 ppbus0: [ITHREAD] plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem
Re: vmware tools for ESX Server 3.5
On Thursday 04 September 2008, B. Cook wrote: On Sep 3, 2008, at 12:11 PM, John Nielsen wrote: On Wednesday 03 September 2008, B. Cook wrote: I am setting up FreeBSD 7.0 and he is asking about the vmware-tools. Ports has some things, but I am not sure what I need, and neither is he. Can anyone tell me what it needs? I usually create VM's with the Intel gigabit vNIC's which can use FreeBSD's em driver. Since Xorg includes the vmmouse and vmware video drivers already, the main things you should be looking for are the memory balloon driver and the guestd service. In the past I have gotten these to work by using the supplied tools (on the CD image that is inserted when you select Install VMware tools from the host). However it is much easier nowadays to use the free version in ports/emulators/open-vm-tools (or open-vm-tools-nox11). JN Well this is the other way.. FreeBSD is the guest not the host. What I said applies to FreeBSD running as a guest VM. (You don't install VMware tools on a host.) This is what the owner of the cluster is telling me: The tools aren't absolutely necessary but if we can we always install them in guest machines. They allow the VMWare server to gracefully shutdown the guest That's guestd. The VMware-supplied version actually does a shutdown -h for power-down. On Linux that works but on FreeBSD it simply halts the OS so you have to power down the VM yourself. The open-vm-tools power down correctly. improve memory management That's the balloon memctl driver. It actually improves memory management for the host by asking the guest (where it is running) to feed it available memory, which the host can then allocate to other VM's if needed. replace the virtual NIC with a higher performance one That applies to the vmxnet/lance type of virtual NIC. I've heard of people getting the VMware-supplied driver running under FreeBSD, but I've never messed with it. The le(4) driver does fine. Or you can do as I suggested and switch your virtual NIC to an intel one (which is the default for 64-bit VM's, may require editing the .vmx file for 32-bit VM's) which will use the em(4) driver. replace the video driver (if you are running a GUI which we aren't in this case.) The vmware video driver is already included in current versions of Xorg, as is the vmmouse input driver which will synch the mouse pointer with the viewer's external session and release the cursor when it reaches the edge. etc I think he covered just about everything. :) But this machine is running fine, including the nightly snapshots. I would still advise you to install some form of VMware tools. Again my preferences is for open-vm-tools. Below is the dmesg from the guest: snip le0: AMD PCnet-PCI port 0x1400-0x147f irq 18 at device 17.0 on pci0 le0: 16 receive buffers, 4 transmit buffers le0: Ethernet address: 00:50:56:83:49:9d You may want to look at switching to the Intel virtual nic in the VM's configuration. (You would then also need to change any ifconfig_le0 entries in the guest's /etc/rc.conf to ifconfig_em0). For Workstation (and IIRC it's the same for Server and ESX) you do this by changing (or adding) a line like this: ethernet0.virtualDev = e1000 in the config (.vmx) file for the VM. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vmware tools for ESX Server 3.5
Hello, I am setting up FreeBSD 7.0 and he is asking about the vmware-tools. Ports has some things, but I am not sure what I need, and neither is he. Can anyone tell me what it needs? Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vmware tools for ESX Server 3.5
On Wednesday 03 September 2008, B. Cook wrote: I am setting up FreeBSD 7.0 and he is asking about the vmware-tools. Ports has some things, but I am not sure what I need, and neither is he. Can anyone tell me what it needs? I usually create VM's with the Intel gigabit vNIC's which can use FreeBSD's em driver. Since Xorg includes the vmmouse and vmware video drivers already, the main things you should be looking for are the memory balloon driver and the guestd service. In the past I have gotten these to work by using the supplied tools (on the CD image that is inserted when you select Install VMware tools from the host). However it is much easier nowadays to use the free version in ports/emulators/open-vm-tools (or open-vm-tools-nox11). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VMWare Tools for FreeBSD
David Robillard wrote: Basically the only reason I have for using VM Tools is for the ability of Vmotion and such with our ESX Server farm. It's really the only benefit that the VM tools will give me on FreeBSD as all my virtual machines which are running FreeBSD are servers and don't use any GUI's either. Currently there is nothing that doesn't run correctly under VMWare and I have not seen any lack of performance or anything compared to a physical machine. Maybe if enough of us push to have the VMWare Tools developed and certified for use with VMWare that they might actually get started. I might develop some sort of E-Petition for it, what you think? Why not? I'm in the exact same position as you are with ESX FreeBSD. Hence I'd love to have VMWare Tools developed and certified for use with FreeBSD. Actually, I'd really like to see VMWare Server and Player certified for FreeBSD i386 and amd64. VMWare is great stuff, I use and support all of it, but as a company they have a bit of Fortune 500 tunnel vision. Their pricing is geared towards nickel and diming large enterprises and their software support is geared too much towards Windows. Hyper-V will cut deeply into their market and they might regret being too MS-centered. I already have potential customers asking Gee, what about Hyper-V. It's a lot cheaper than ESX and we don't really care about non-MS... Pricing ESX enterprise (with all the bells whistles, including vmotion, virtual center, HA, etc) at around US$500 per node and providing better support for FreeBSD and other alternative OSes would go a LONG way towards long-term competitiveness. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VMWare Tools for FreeBSD
Jeff Dickens wrote: I just made a copy of /usr/lib/vmware/isoimages/freebsd.iso from VMware Server v1.0.4 under a different name, and moved it to the ESX server. Then I mounted that ISO as a virtual cdrom on the freebsd guest, untarred the tools and ran the install script. It seems to work fine. A couple of provisos: I don't use X windows on any of my FreeBSD systems, and the vmxnet accelerated virtual network adapter does not work properly. I use the e1000 adapter instead. It wouldn't be a bad idea to comment out the 'vmxnet_load=YES' line from /boot/loader.conf, but it doesn't seem to cause problems just being loaded. Furthermore, I don't use any of the virtualcenter features like vmotion, etc. I use freebsd guests for small-footprint servers, for example a dhcp and dnscache server with 512MB disk and 32MB ram. SNIP Jeff, Basically the only reason I have for using VM Tools is for the ability of Vmotion and such with our ESX Server farm. It's really the only benefit that the VM tools will give me on FreeBSD as all my virtual machines which are running FreeBSD are servers and don't use any GUI's either. Currently there is nothing that doesn't run correctly under VMWare and I have not seen any lack of performance or anything compared to a physical machine. Maybe if enough of us push to have the VMWare Tools developed and certified for use with VMWare that they might actually get started. I might develop some sort of E-Petition for it, what you think? Terry signature.asc Description: OpenPGP digital signature
Re: VMWare Tools for FreeBSD
Basically the only reason I have for using VM Tools is for the ability of Vmotion and such with our ESX Server farm. It's really the only benefit that the VM tools will give me on FreeBSD as all my virtual machines which are running FreeBSD are servers and don't use any GUI's either. Currently there is nothing that doesn't run correctly under VMWare and I have not seen any lack of performance or anything compared to a physical machine. Maybe if enough of us push to have the VMWare Tools developed and certified for use with VMWare that they might actually get started. I might develop some sort of E-Petition for it, what you think? Why not? I'm in the exact same position as you are with ESX FreeBSD. Hence I'd love to have VMWare Tools developed and certified for use with FreeBSD. Actually, I'd really like to see VMWare Server and Player certified for FreeBSD i386 and amd64. David -- David Robillard UNIX systems administrator Oracle DBA CISSP, RHCE Sun Certified Security Administrator Montreal: +1 514 966 0122 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
On Tue, March 18, 2008 12:23, Peter Boosten wrote: Gelsema, P (Patrick) - FreeBSD wrote: On Tue, March 18, 2008 11:40, Peter Boosten wrote: http://open-vm-tools.sourceforge.net/ Just to confirm. This one runs on RELENG_7_0? quote Kernel modules for FreeBSD, including an experimental port of HGFS to FreeBSD. /quote It allows dymanic memory management by the VM Ware host? It also allows the VMWare host to gracefully shutdown the Freebsd guest? I get an error running an install on RELENG_7_0 I386. Making check in hgfsmounter gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\ -DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\ 2008.03.03-79993\ -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED] -DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DX_DISPLAY_MISSING=1 -DHAVE_DLOPEN=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I. -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS -I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o hgfsmounter.c hgfsmounter.c: In function 'ParseOptions': hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this function) hgfsmounter.c:607: error: (Each undeclared identifier is reported only once hgfsmounter.c:607: error: for each function it appears in.) *** Error code 1 Someone seen this before? Rgds, Patrick quote The following components have been released as OSS: * Drivers for devices and filesystems access * Memory ballooning * Shared folders * Drag and Drop, Text and File Copy/Paste * Clipboard sharing * Disk wiping and shrinking * Time synchronization * Automatic guest screen resolution resizing * GuestInfo (provides statistics about guest environment) * Guest SDK (provides information about the VM) * Soft power operations * Multiple monitor support * GTK Toolbox UI /quote Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
--On Tuesday, March 18, 2008 22:34:30 +0800 Gelsema, P (Patrick) - FreeBSD [EMAIL PROTECTED] wrote: I get an error running an install on RELENG_7_0 I386. Making check in hgfsmounter gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\ -DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\ 2008.03.03-79993\ -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED] -DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DX_DISPLAY_MISSING=1 -DHAVE_DLOPEN=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I. -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS -I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o hgfsmounter.c hgfsmounter.c: In function 'ParseOptions': hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this function) hgfsmounter.c:607: error: (Each undeclared identifier is reported only once hgfsmounter.c:607: error: for each function it appears in.) *** Error code 1 Someone seen this before? Yes, I got it as well. I was going to create a port for it, but I have no idea how to solve the make problem. If there is a programmer reading this that wants to work with me to get the software to make on FreeBSD, I'll be happy to submit and maintain the port. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
I believe the issue is that MNT_NODEV which should be defined in /usr/include/sys/mount.h was deprecated and removed from FreeBSD: http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715 At line 42 in hgfsmounter.c, add # define MNT_NODEV 0 Then rebuild. SHould work fine now. I configured my build environment via the README with ./configure LDFLAGS=/usr/local/lib etc. -aps On Tue, Mar 18, 2008 at 10:42 AM, Paul Schmehl [EMAIL PROTECTED] wrote: --On Tuesday, March 18, 2008 22:34:30 +0800 Gelsema, P (Patrick) - FreeBSD [EMAIL PROTECTED] wrote: I get an error running an install on RELENG_7_0 I386. Making check in hgfsmounter gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\ -DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\ 2008.03.03-79993\ -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED] -DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DX_DISPLAY_MISSING=1 -DHAVE_DLOPEN=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I. -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS -I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o hgfsmounter.c hgfsmounter.c: In function 'ParseOptions': hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this function) hgfsmounter.c:607: error: (Each undeclared identifier is reported only once hgfsmounter.c:607: error: for each function it appears in.) *** Error code 1 Someone seen this before? Yes, I got it as well. I was going to create a port for it, but I have no idea how to solve the make problem. If there is a programmer reading this that wants to work with me to get the software to make on FreeBSD, I'll be happy to submit and maintain the port. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- What lies behind us and what lies in front of us is of little concern to what lies within us. -Ralph Waldo Emerson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
--On Tuesday, March 18, 2008 11:36:53 -0400 Alexander Sack [EMAIL PROTECTED] wrote: I believe the issue is that MNT_NODEV which should be defined in /usr/include/sys/mount.h was deprecated and removed from FreeBSD: http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715 At line 42 in hgfsmounter.c, add # define MNT_NODEV 0 Then rebuild. SHould work fine now. Thanks. I was contacted privately by someone else on the list and advised of the same thing. I chose to remove the lines mentioning MNT_NODEV from the hgfsmounter.c file. I wasn't aware you could simply define it as 0. Which is preferable? I configured my build environment via the README with ./configure LDFLAGS=/usr/local/lib etc. I'm compiling and making without problems now that the NODEV problem is cleared up, but I didn't define any LDFLAGS. Should I? -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
On Tue, March 18, 2008 23:36, Alexander Sack wrote: I believe the issue is that MNT_NODEV which should be defined in /usr/include/sys/mount.h was deprecated and removed from FreeBSD: http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715 At line 42 in hgfsmounter.c, add # define MNT_NODEV 0 Then rebuild. SHould work fine now. I configured my build environment via the README with ./configure LDFLAGS=/usr/local/lib etc. Done #./configure LDFLAGS=/usr/local/lib --without-x #make #make install That all goes ok But when I run #make modules I get an error wolverine# make modules make -C modules make -C freebsd/vmmemctl make -C freebsd/vmxnet cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c if_vxn.c if_vxn.c: In function 'vxn_attach': if_vxn.c:302: warning: passing argument 4 of 'bus_setup_intr' from incompatible pointer type if_vxn.c:302: warning: passing argument 5 of 'bus_setup_intr' from incompatible pointer type if_vxn.c:302: error: too few arguments to function 'bus_setup_intr' if_vxn.c:378: error: 'struct arpcom' has no member named '_ac_enaddr' if_vxn.c:385: error: 'struct arpcom' has no member named '_ac_enaddr' *** Error code 1 Stop in /tmp/open-vm-tools-2008.03.03-79993/modules/freebsd/vmxnet. *** Error code 1 Any ideas? -aps On Tue, Mar 18, 2008 at 10:42 AM, Paul Schmehl [EMAIL PROTECTED] wrote: --On Tuesday, March 18, 2008 22:34:30 +0800 Gelsema, P (Patrick) - FreeBSD [EMAIL PROTECTED] wrote: I get an error running an install on RELENG_7_0 I386. Making check in hgfsmounter gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\ -DPACKAGE_VERSION=\2008.03.03-79993\ -DPACKAGE_STRING=\open-vm-tools\ 2008.03.03-79993\ -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED] -DPACKAGE=\open-vm-tools\ -DVERSION=\2008.03.03-79993\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DX_DISPLAY_MISSING=1 -DHAVE_DLOPEN=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DNO_MULTIMON=1 -I. -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -DVMX86_TOOLS -I/tmp/open-vm-tools-2008.03.03-79993/lib/include -DUSING_AUTOCONF=1 -MT hgfsmounter.o -MD -MP -MF .deps/hgfsmounter.Tpo -c -o hgfsmounter.o hgfsmounter.c hgfsmounter.c: In function 'ParseOptions': hgfsmounter.c:607: error: 'MNT_NODEV' undeclared (first use in this function) hgfsmounter.c:607: error: (Each undeclared identifier is reported only once hgfsmounter.c:607: error: for each function it appears in.) *** Error code 1 Someone seen this before? Yes, I got it as well. I was going to create a port for it, but I have no idea how to solve the make problem. If there is a programmer reading this that wants to work with me to get the software to make on FreeBSD, I'll be happy to submit and maintain the port. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- What lies behind us and what lies in front of us is of little concern to what lies within us. -Ralph Waldo Emerson ___ 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: FW: VMWare Tools for FreeBSD
Comments below: On Tue, Mar 18, 2008 at 12:13 PM, Gelsema, P (Patrick) [EMAIL PROTECTED] wrote: On Tue, March 18, 2008 23:36, Alexander Sack wrote: I believe the issue is that MNT_NODEV which should be defined in /usr/include/sys/mount.h was deprecated and removed from FreeBSD: http://ftp.cz.freebsd.org/pub/FreeBSD-cvs/gnats/conf/79715 At line 42 in hgfsmounter.c, add # define MNT_NODEV 0 Then rebuild. SHould work fine now. I configured my build environment via the README with ./configure LDFLAGS=/usr/local/lib etc. Done #./configure LDFLAGS=/usr/local/lib --without-x #make #make install That all goes ok But when I run #make modules I get an error wolverine# make modules make -C modules make -C freebsd/vmmemctl make -C freebsd/vmxnet cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c if_vxn.c if_vxn.c: In function 'vxn_attach': if_vxn.c:302: warning: passing argument 4 of 'bus_setup_intr' from incompatible pointer type if_vxn.c:302: warning: passing argument 5 of 'bus_setup_intr' from incompatible pointer type if_vxn.c:302: error: too few arguments to function 'bus_setup_intr' if_vxn.c:378: error: 'struct arpcom' has no member named '_ac_enaddr' if_vxn.c:385: error: 'struct arpcom' has no member named '_ac_enaddr' *** Error code 1 Stop in /tmp/open-vm-tools-2008.03.03-79993/modules/freebsd/vmxnet. *** Error code 1 Any ideas? bus_setup_intr() kernel API seems to have either changed or handled differently in 7.0. I believe you can add a NULL after the flags (INTR_MPSAFE) which tells BSD to use the standard interrupt handler instead of a top-level handler. _ac_enaddr is because arpcom as defined in net/if_arp.h no longer exists. Typically the protocol bits are stuffed in if_l2com (layer 2). I made the macro in net_compat.h #define VXN_SC2ENADDR(softc)(IF_LLADDR(VXN_SC2IFP(softc)) and then removed the from both references in if_vxn.c as this macro already returns a pointer to char. That got me past this problem. Btw, this isn't an official port since I didn't really rectify the net_compat.h stuff (I suppose you could make the 60 to 700055, etc.). I'm still getting some further issues with vnodeops and vfsops with some modules (I believe vops_lcok should be vops_lock1) but I don't know about the other problem. -aps -- What lies behind us and what lies in front of us is of little concern to what lies within us. -Ralph Waldo Emerson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
--On Tuesday, March 18, 2008 15:24:53 -0400 Alexander Sack [EMAIL PROTECTED] wrote: bus_setup_intr() kernel API seems to have either changed or handled differently in 7.0. I believe you can add a NULL after the flags (INTR_MPSAFE) which tells BSD to use the standard interrupt handler instead of a top-level handler. _ac_enaddr is because arpcom as defined in net/if_arp.h no longer exists. Typically the protocol bits are stuffed in if_l2com (layer 2). I made the macro in net_compat.h # define VXN_SC2ENADDR(softc)(IF_LLADDR(VXN_SC2IFP(softc)) and then removed the from both references in if_vxn.c as this macro already returns a pointer to char. That got me past this problem. Btw, this isn't an official port since I didn't really rectify the net_compat.h stuff (I suppose you could make the 60 to 700055, etc.). I'm still getting some further issues with vnodeops and vfsops with some modules (I believe vops_lcok should be vops_lock1) but I don't know about the other problem. Well, you're way beyond my skill level now. I'll be happy to create a port for this, but someone with a much deeper knowledge of FreeBSD and C is going to have to resolve the problems with the modules. If someone is interested in doing that, I'll submit the patches to the developers *and* add them to the port so that it can be committed. (Other than the kernel modules, the software builds fine from what I can tell.) -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
Paul: I'd have to look at this some more. I got much further in the porting when I hit another snag with the vmblock driver (the inline assembly needs to be __asm__ instead of asm or something needs to process it that way for it to work, I also hacked around a vfsops issue which I'm not 100% sure what should really be there) and then all of it needs to be devtested. I use VMWare Fusion and have installed the existing vmtools that come with the product along with installing the individual X11 vmware driver which works for me but I agree it would be nice to have full port to FreeBSD 7.0-RELEASE. I'm sorry for not giving you patch files its just I was doing this on and off as a exercise to learn a little bit more about it I believe at least now as you said, the userland stuff builds fine now. Thanks! -aps On Tue, Mar 18, 2008 at 4:58 PM, Paul Schmehl [EMAIL PROTECTED] wrote: --On Tuesday, March 18, 2008 15:24:53 -0400 Alexander Sack [EMAIL PROTECTED] wrote: bus_setup_intr() kernel API seems to have either changed or handled differently in 7.0. I believe you can add a NULL after the flags (INTR_MPSAFE) which tells BSD to use the standard interrupt handler instead of a top-level handler. _ac_enaddr is because arpcom as defined in net/if_arp.h no longer exists. Typically the protocol bits are stuffed in if_l2com (layer 2). I made the macro in net_compat.h # define VXN_SC2ENADDR(softc)(IF_LLADDR(VXN_SC2IFP(softc)) and then removed the from both references in if_vxn.c as this macro already returns a pointer to char. That got me past this problem. Btw, this isn't an official port since I didn't really rectify the net_compat.h stuff (I suppose you could make the 60 to 700055, etc.). I'm still getting some further issues with vnodeops and vfsops with some modules (I believe vops_lcok should be vops_lock1) but I don't know about the other problem. Well, you're way beyond my skill level now. I'll be happy to create a port for this, but someone with a much deeper knowledge of FreeBSD and C is going to have to resolve the problems with the modules. If someone is interested in doing that, I'll submit the patches to the developers *and* add them to the port so that it can be committed. (Other than the kernel modules, the software builds fine from what I can tell.) -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- What lies behind us and what lies in front of us is of little concern to what lies within us. -Ralph Waldo Emerson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FW: VMWare Tools for FreeBSD
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Terry Sposato Sent: Sunday, March 16, 2008 3:04 PM To: freebsd-questions@freebsd.org Subject: Re: FW: VMWare Tools for FreeBSD SNIP Ted Mittelstaedt wrote: Are you asking if FreeBSD can be made to run the ESX software so that a FreeBSD server can virtualize multiple systems, or are you asking if an ESX server can create a virtual machine that FreeBSD can run in? If your using the commercial ESX product I would assume you would be using it on it's own bare metal product incarnation which I think uses a hacked-up version of Linux (without a compiler or any other normal Linux tools). In that case I do not see why you would have a problem running multiple FreeBSD virtual servers on the ESX server. That's not what OP is asking. He wants to run FreeBSD as VM in ESX. There's currently no support from VMWare for FreeBSD, but it runs anyway. I figured that was what he was asking, but we should probably hear from him to make sure that this is really what he was asking. Unfortunately, the original post was either from someone who didn't use English as their native language, or they are paying for their Internet connection by-the-byte and were trying to make the question as short as possible, as a result, the entire meaning of the post was lost. Ted OK, maybe I was not clear enough so I will try again. I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently there is no problem with it and it works fine. The problems arise when you want to take advantage of the HA ability of ESX Server, as it only supports Virtual Machines with the VM Tools running. So what I am asking is if someone has ever though about porting the VMWare Tools to run in a FreeBSD Virtual Machine image. Terry, Jeff Dickens replied this morning - perhaps his mail crossed yours? The answer is yes, you can do it with the free vm tools from the free vmware product. If you have problems compiling these, please post. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: VMWare Tools for FreeBSD
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jeff Dickens Sent: Sunday, March 16, 2008 5:17 AM To: Terry Sposato; freebsd-questions@freebsd.org Subject: RE: VMWare Tools for FreeBSD I use the vmware tools for freebsd from the free vmware server product for my esx-hoster freebsd servers. Did you have to do anything special to build and install them? Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Terry Sposato Sent: Sunday, March 16, 2008 3:04 PM To: freebsd-questions@freebsd.org Subject: Re: FW: VMWare Tools for FreeBSD SNIP Ted Mittelstaedt wrote: Are you asking if FreeBSD can be made to run the ESX software so that a FreeBSD server can virtualize multiple systems, or are you asking if an ESX server can create a virtual machine that FreeBSD can run in? If your using the commercial ESX product I would assume you would be using it on it's own bare metal product incarnation which I think uses a hacked-up version of Linux (without a compiler or any other normal Linux tools). In that case I do not see why you would have a problem running multiple FreeBSD virtual servers on the ESX server. That's not what OP is asking. He wants to run FreeBSD as VM in ESX. There's currently no support from VMWare for FreeBSD, but it runs anyway. I figured that was what he was asking, but we should probably hear from him to make sure that this is really what he was asking. Unfortunately, the original post was either from someone who didn't use English as their native language, or they are paying for their Internet connection by-the-byte and were trying to make the question as short as possible, as a result, the entire meaning of the post was lost. Ted OK, maybe I was not clear enough so I will try again. I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently there is no problem with it and it works fine. The problems arise when you want to take advantage of the HA ability of ESX Server, as it only supports Virtual Machines with the VM Tools running. So what I am asking is if someone has ever though about porting the VMWare Tools to run in a FreeBSD Virtual Machine image. Terry, Jeff Dickens replied this morning - perhaps his mail crossed yours? The answer is yes, you can do it with the free vm tools from the free vmware product. If you have problems compiling these, please post. Ted Ted / Jeff, Could you please let me know where to download these free vm tools. The only description at google I can find is that of the actual VMWare Tools by VMWare. If you point me to a download link that would be great! Terry signature.asc Description: OpenPGP digital signature
Re: VMWare Tools for FreeBSD
I just made a copy of /usr/lib/vmware/isoimages/freebsd.iso from VMware Server v1.0.4 under a different name, and moved it to the ESX server. Then I mounted that ISO as a virtual cdrom on the freebsd guest, untarred the tools and ran the install script. It seems to work fine. A couple of provisos: I don't use X windows on any of my FreeBSD systems, and the vmxnet accelerated virtual network adapter does not work properly. I use the e1000 adapter instead. It wouldn't be a bad idea to comment out the 'vmxnet_load=YES' line from /boot/loader.conf, but it doesn't seem to cause problems just being loaded. Furthermore, I don't use any of the virtualcenter features like vmotion, etc. I use freebsd guests for small-footprint servers, for example a dhcp and dnscache server with 512MB disk and 32MB ram. Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jeff Dickens Sent: Sunday, March 16, 2008 5:17 AM To: Terry Sposato; freebsd-questions@freebsd.org Subject: RE: VMWare Tools for FreeBSD I use the vmware tools for freebsd from the free vmware server product for my esx-hoster freebsd servers. Did you have to do anything special to build and install them? Ted ___ 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: FW: VMWare Tools for FreeBSD
Terry Sposato wrote: Ted / Jeff, Could you please let me know where to download these free vm tools. The only description at google I can find is that of the actual VMWare Tools by VMWare. If you point me to a download link that would be great! Although my name isn't Ted or Jeff I will post the link :-) This is from a discussion last week: http://open-vm-tools.sourceforge.net/ Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
On Tue, March 18, 2008 11:40, Peter Boosten wrote: Terry Sposato wrote: Ted / Jeff, Could you please let me know where to download these free vm tools. The only description at google I can find is that of the actual VMWare Tools by VMWare. If you point me to a download link that would be great! Although my name isn't Ted or Jeff I will post the link :-) This is from a discussion last week: http://open-vm-tools.sourceforge.net/ Just to confirm. This one runs on RELENG_7_0? It allows dymanic memory management by the VM Ware host? It also allows the VMWare host to gracefully shutdown the Freebsd guest? thanks Patrick Gelsema Peter -- http://www.boosten.org ___ 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: FW: VMWare Tools for FreeBSD
Gelsema, P (Patrick) - FreeBSD wrote: On Tue, March 18, 2008 11:40, Peter Boosten wrote: http://open-vm-tools.sourceforge.net/ Just to confirm. This one runs on RELENG_7_0? quote Kernel modules for FreeBSD, including an experimental port of HGFS to FreeBSD. /quote It allows dymanic memory management by the VM Ware host? It also allows the VMWare host to gracefully shutdown the Freebsd guest? quote The following components have been released as OSS: * Drivers for devices and filesystems access * Memory ballooning * Shared folders * Drag and Drop, Text and File Copy/Paste * Clipboard sharing * Disk wiping and shrinking * Time synchronization * Automatic guest screen resolution resizing * GuestInfo (provides statistics about guest environment) * Guest SDK (provides information about the VM) * Soft power operations * Multiple monitor support * GTK Toolbox UI /quote Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VMWare Tools for FreeBSD
Hi, Is there any future development work being undertaken in order to port vmware-tools to FreeBSD. As our organisation using VMWare ESX Server and a lot of our servers are being virtualised to save hardware costs, this would let our FreeBSD servers follow as well. It does work find under Linux so I am 50% confident that it would port to FreeBSD if the work was done. Is it a licensing issue or another reason? Not being a developer myself was just wondering if this has been tackled and if it is being incorporated somewhere in the future? Regards, Terry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VMWare Tools for FreeBSD
Hi, Is there any future development work being undertaken in order to port vmware-tools to FreeBSD. As our organisation using VMWare ESX Server and a lot of our servers are being virtualised to save hardware costs, this would let our FreeBSD servers follow as well. It does work find under Linux so I am 50% confident that it would port to FreeBSD if the work was done. Is it a licensing issue or another reason? Not being a developer myself was just wondering if this has been tackled and if it is being incorporated somewhere in the future? Regards, Terry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: VMWare Tools for FreeBSD
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Terry Sposato Sent: Saturday, March 15, 2008 10:52 PM To: freebsd-questions@freebsd.org Subject: VMWare Tools for FreeBSD Hi, Is there any future development work being undertaken in order to port vmware-tools to FreeBSD. As our organisation using VMWare ESX Server and a lot of our servers are being virtualised to save hardware costs, this would let our FreeBSD servers follow as well. It does work find under Linux so I am 50% confident that it would port to FreeBSD if the work was done. Is it a licensing issue or another reason? Not being a developer myself was just wondering if this has been tackled and if it is being incorporated somewhere in the future? Are you asking if FreeBSD can be made to run the ESX software so that a FreeBSD server can virtualize multiple systems, or are you asking if an ESX server can create a virtual machine that FreeBSD can run in? If your using the commercial ESX product I would assume you would be using it on it's own bare metal product incarnation which I think uses a hacked-up version of Linux (without a compiler or any other normal Linux tools). In that case I do not see why you would have a problem running multiple FreeBSD virtual servers on the ESX server. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VMWare Tools for FreeBSD
Ted Mittelstaedt wrote: Are you asking if FreeBSD can be made to run the ESX software so that a FreeBSD server can virtualize multiple systems, or are you asking if an ESX server can create a virtual machine that FreeBSD can run in? If your using the commercial ESX product I would assume you would be using it on it's own bare metal product incarnation which I think uses a hacked-up version of Linux (without a compiler or any other normal Linux tools). In that case I do not see why you would have a problem running multiple FreeBSD virtual servers on the ESX server. That's not what OP is asking. He wants to run FreeBSD as VM in ESX. There's currently no support from VMWare for FreeBSD, but it runs anyway. Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: VMWare Tools for FreeBSD
-Original Message- From: Peter Boosten [mailto:[EMAIL PROTECTED] Sent: Sunday, March 16, 2008 12:29 AM To: Ted Mittelstaedt Cc: Terry Sposato; freebsd-questions@freebsd.org Subject: Re: VMWare Tools for FreeBSD Ted Mittelstaedt wrote: Are you asking if FreeBSD can be made to run the ESX software so that a FreeBSD server can virtualize multiple systems, or are you asking if an ESX server can create a virtual machine that FreeBSD can run in? If your using the commercial ESX product I would assume you would be using it on it's own bare metal product incarnation which I think uses a hacked-up version of Linux (without a compiler or any other normal Linux tools). In that case I do not see why you would have a problem running multiple FreeBSD virtual servers on the ESX server. That's not what OP is asking. He wants to run FreeBSD as VM in ESX. There's currently no support from VMWare for FreeBSD, but it runs anyway. I figured that was what he was asking, but we should probably hear from him to make sure that this is really what he was asking. Unfortunately, the original post was either from someone who didn't use English as their native language, or they are paying for their Internet connection by-the-byte and were trying to make the question as short as possible, as a result, the entire meaning of the post was lost. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VMWare Tools for FreeBSD
On Sun, Mar 16, 2008 at 05:52:27PM +1100, Terry Sposato wrote: Is there any future development work being undertaken in order to port vmware-tools to FreeBSD. I don't know if somebody is actually preparing an official port of http://open-vm-tools.sourceforge.net/ but I don't think it's too difficult to compile and run them on FreeBSD 7.0. I hope I'll find the time to test this soon but I wouldn't be able to roll a port without some help. :) As our organisation using VMWare ESX Server and a lot of our servers are being virtualised to save hardware costs, this would let our FreeBSD servers follow as well. If you're using FreeBSD 6.x, you can use the vmware-tools that come with VMware server 1.04. I tested them with 6.2/amd64 and 6.3/amd64 and they work fine (vmmemctl.ko and vmware-guestd), including VMotion. It does work find under Linux so I am 50% confident that it would port to FreeBSD if the work was done. Is it a licensing issue or another reason? Not No, it's not a licensing issue, since vmware-tools are released as open source now. I guess it's simply lack of interest and that there aren't many ESX users who are using FreeBSD as a platform. FreeBSD is not an enterprise system, you know... :-/ Uwe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: VMWare Tools for FreeBSD
I use the vmware tools for freebsd from the free vmware server product for my esx-hoster freebsd servers. The good people at vmware are apparently not interested in adding official freebsd support to esx. -Original Message- From: Terry Sposato [EMAIL PROTECTED] Sent: Sunday, March 16, 2008 2:23 AM To: freebsd-questions@freebsd.org Subject: VMWare Tools for FreeBSD Hi, Is there any future development work being undertaken in order to port vmware-tools to FreeBSD. As our organisation using VMWare ESX Server and a lot of our servers are being virtualised to save hardware costs, this would let our FreeBSD servers follow as well. It does work find under Linux so I am 50% confident that it would port to FreeBSD if the work was done. Is it a licensing issue or another reason? Not being a developer myself was just wondering if this has been tackled and if it is being incorporated somewhere in the future? Regards, Terry ___ 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: FW: VMWare Tools for FreeBSD
SNIP Ted Mittelstaedt wrote: Are you asking if FreeBSD can be made to run the ESX software so that a FreeBSD server can virtualize multiple systems, or are you asking if an ESX server can create a virtual machine that FreeBSD can run in? If your using the commercial ESX product I would assume you would be using it on it's own bare metal product incarnation which I think uses a hacked-up version of Linux (without a compiler or any other normal Linux tools). In that case I do not see why you would have a problem running multiple FreeBSD virtual servers on the ESX server. That's not what OP is asking. He wants to run FreeBSD as VM in ESX. There's currently no support from VMWare for FreeBSD, but it runs anyway. I figured that was what he was asking, but we should probably hear from him to make sure that this is really what he was asking. Unfortunately, the original post was either from someone who didn't use English as their native language, or they are paying for their Internet connection by-the-byte and were trying to make the question as short as possible, as a result, the entire meaning of the post was lost. Ted OK, maybe I was not clear enough so I will try again. I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently there is no problem with it and it works fine. The problems arise when you want to take advantage of the HA ability of ESX Server, as it only supports Virtual Machines with the VM Tools running. So what I am asking is if someone has ever though about porting the VMWare Tools to run in a FreeBSD Virtual Machine image. Terry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: VMWare Tools for FreeBSD
--On March 17, 2008 10:03:54 AM +1100 Terry Sposato [EMAIL PROTECTED] wrote: OK, maybe I was not clear enough so I will try again. I want to run FreeBSD as a VM Guest on a VMWare ESX Server. Currently there is no problem with it and it works fine. The problems arise when you want to take advantage of the HA ability of ESX Server, as it only supports Virtual Machines with the VM Tools running. So what I am asking is if someone has ever though about porting the VMWare Tools to run in a FreeBSD Virtual Machine image. I downloaded the open-vm-tools from Sourceforge and tried to compile and make them. The compile went fine, but the make failed. I'm not a programmer, so I struggle trying to resolve such problems. I'd be happy to make a port for it, but I would need help from someone with more programming knowledge than I. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ 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 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 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMwaretools)
scratch that, guestd6 worked fine after make clearing it. bad download I guess. -Sean -- From: Sean Cavanaugh [EMAIL PROTECTED] Sent: Thursday, February 28, 2008 9:48 PM To: [EMAIL PROTECTED]; freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMwaretools) 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] ___ 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]
FreeBSD 7RC2 and VMware tools
Hello to all. 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. 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 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]
VMware Tools
Hi , I am using Vmware workstation for Win32 Vr.3.0. it runs only 640x480.Can any one tell me from where i have to download Vmware Tools for Vmware workstation for Win32 Vr.3.0. Vmware tools available for 1.x and FreeBSD Guest Operating Systems only.it is avl in VMware.com. i am unable to find VMwatr Tools for Vmware workstation for Win32 Vr.3.0. Any Vmware users please let me know from where i have to download. Thanks ah. - Original Message - From: Nick Slager [EMAIL PROTECTED] To: Nathan Kinkade [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, October 11, 2002 4:23 AM Subject: Re: vmware Thus spake Nathan Kinkade ([EMAIL PROTECTED]): I was just running it in 640x480 mode. It kept barking at me that I needed to install vmare-tools in order to run at a higher resolution. I installed vmware-tools and played around with it, but as soon as I looked at the XF86Config file that it wanted me to install I quickly pkg_deinstall'ed it. I also had to I think that's referring to the vmware-tools that come as part of the vmware software. Choose `VMware Tools Install' from the Settings menu after your VM has booted, then double-click the icon for your floppy drive in My Computer. The software there will enable you to run your microsoft VM in resolutions other than standard vga (640x480x16colors). My microsoft vm currently runs at 1024x768x16bit on a 1400x1050x16bit X display. Regards, Nick -- We demand rigidly defined areas of doubt and uncertainty. -- Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
