Re: [Samba] Problems running samba in vmware
I've switched to a PCI based network card which seems to have helped. Have to wait and see but so far seems much better than the on-board stuff even though its from the same manufacturer (Realtek). Adam Zimmer President Arius Software Corporation (519) 885-9045 x122 Douglas VanLeuven wrote: Adam Zimmer wrote: At the moment I have enabled timeSync with vmware tools. In the general area of time keeping on the host, I added the following settings which avoided errors about the RTC missing interrupts: host.usefastclock=false host.cpukHz=240 host.useTSC=true ptsc.useTSC=true I have two other machines similarly configured (with the exception of running other linux applications not samba). Ntpdate seems to be installed as it is part of the ubuntu-server default config. However, my other machines seem to run it ok. If anything they fall behind a bit and the vmware sync keeps them up-to-date. Ian McDonald wrote: How are your time sync options set for the VM? Is it keeping time ok? (note,AFAIR, you're not supposed to run NTP within a VM.). True. I refer to this document from vmware. http://www.vmware.com/pdf/vmware_timekeeping.pdf Generally, ntp vmware timesync fight each other. The usual method is to turn off the ntp service, figure out how to minimize interrupts, allow the clock to run a little slow and allow vmware timesync to bump up the time when it gets about 1 minute slow. There's another thread that mentions issues with on-board nics and drivers. Over the years, I've bumped into that myself. To the extent I try and use host-only and route whenever possible. That's worked better for me in generic usage. Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
On Thu, Mar 6, 2008 at 10:13 PM, Adam Zimmer [EMAIL PROTECTED] wrote: I have used samba for nearly 9 years with no problems and we have about 20 users. In the past we have had a dedicated samba server. We have recently virtualized this server to a quad core Q6600 using vmware virtual server 1.0.4 on a 64 bit host running ubuntu 7.10. bad idea. Vmware server is not meant for production servers. Don't try to save a buck and buy a copy of esx. It will save you all this trouble and time is money. If you really want to go along the free road, get yourself xen, linux runs perfectly with the opensource 'free as in free beer' xensource. Vmware server is a great testing tool, not a production one. -- Groeten, J.Asenjo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Natxo Asenjo wrote: On Thu, Mar 6, 2008 at 10:13 PM, Adam Zimmer [EMAIL PROTECTED] wrote: I have used samba for nearly 9 years with no problems and we have about 20 users. In the past we have had a dedicated samba server. We have recently virtualized this server to a quad core Q6600 using vmware virtual server 1.0.4 on a 64 bit host running ubuntu 7.10. bad idea. Vmware server is not meant for production servers. Don't try to save a buck and buy a copy of esx. It will save you all this trouble and time is money. If you really want to go along the free road, get yourself xen, linux runs perfectly with the opensource 'free as in free beer' xensource. Vmware server is a great testing tool, not a production one. Why is that? - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1Y5Wmb+gadEcsb4RAh7iAJsEkM7zmX/hSZmv+a6JZyVUFUNASQCg4cvl FQhSxHNYt5Pl3RBzhNj3h8Y= =kRYx -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
Ryan Novosielski wrote: Natxo Asenjo wrote: On Thu, Mar 6, 2008 at 10:13 PM, Adam Zimmer [EMAIL PROTECTED] wrote: I have used samba for nearly 9 years with no problems and we have about 20 users. In the past we have had a dedicated samba server. We have recently virtualized this server to a quad core Q6600 using vmware virtual server 1.0.4 on a 64 bit host running ubuntu 7.10. bad idea. Vmware server is not meant for production servers. Don't try to save a buck and buy a copy of esx. It will save you all this trouble and time is money. If you really want to go along the free road, get yourself xen, linux runs perfectly with the opensource 'free as in free beer' xensource. Vmware server is a great testing tool, not a production one. Why is that? ESX is the OS. Vmware server runs under an OS. All kinds of ramifications to this from allocating specific ethernet cards to specific virtual machines instead of bridging to better cpu and memory management. But this is getting pretty off topic for samba. Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
On Thu, Mar 6, 2008 at 10:13 PM, Adam Zimmer [EMAIL PROTECTED] wrote: I have used samba for nearly 9 years with no problems and we have about 20 users. In the past we have had a dedicated samba server. We have recently virtualized this server to a quad core Q6600 using vmware virtual server 1.0.4 on a 64 bit host running ubuntu 7.10. bad idea. Vmware server is not meant for production servers. Don't try to save a buck and buy a copy of esx. It will save you all this trouble and time is money. If you really want to go along the free road, get yourself xen, linux runs perfectly with the opensource 'free as in free beer' xensource. Vmware server is a great testing tool, not a production one. Why is that? This isn't a forum for the pros cons of virtualization techniques; but I can tell you that it works fine for us. We run Samba on a half dozen VMs hosted in vmware-server. It works fine, Samba doesn't care. And vmware-server on a well tested and proven platform (OS hardware) has been 100% stable. We've tested multiple failures in various ways, most brutally: boot, VMs start automatically, yank power cord, boot, VMs start recover, yank power cord, etc... and it always comes back just fine. No lost data, no crashes. Very impressive. We are buying the real VMware (which BTW, is just based on RedHat anyway) but just for the VMFS feature [we can more efficiently use our SAN] and not because of any stability issues. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
On 3/6/2008, Adam Zimmer ([EMAIL PROTECTED]) wrote: I have tried various socket options including SO_RCVBUF=8192, SO_SNDBUF=8192, IPTOS_LOWDELAY, TCP_NODELAY, SO_KEEPALIVE. At the moment I have set SO_RCVBUF and SO_SNDBUF to be equal to 1400 as I noticed the MTU of the network card was 1500 which seems to but down on the broken pipes. I'm not saying this is cauing your problem, but you shouldn't be setting these at all, as long as you have a modern kernel (2.6 series)... These haven't been needed for a long time. -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
I have now removed those socket options. I am running Linux 2.6.22. However, the delays persist. Any other ideas? I thought it might be name resolution so I tried: name resolve order = wins host bcast But this hasn't helped either. Adam Zimmer President Arius Software Corporation (519) 885-9045 x122 Charles Marcus wrote: On 3/6/2008, Adam Zimmer ([EMAIL PROTECTED]) wrote: I have tried various socket options including SO_RCVBUF=8192, SO_SNDBUF=8192, IPTOS_LOWDELAY, TCP_NODELAY, SO_KEEPALIVE. At the moment I have set SO_RCVBUF and SO_SNDBUF to be equal to 1400 as I noticed the MTU of the network card was 1500 which seems to but down on the broken pipes. I'm not saying this is cauing your problem, but you shouldn't be setting these at all, as long as you have a modern kernel (2.6 series)... These haven't been needed for a long time. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
At the moment I have enabled timeSync with vmware tools. In the general area of time keeping on the host, I added the following settings which avoided errors about the RTC missing interrupts: host.usefastclock=false host.cpukHz=240 host.useTSC=true ptsc.useTSC=true I have two other machines similarly configured (with the exception of running other linux applications not samba). Ntpdate seems to be installed as it is part of the ubuntu-server default config. However, my other machines seem to run it ok. If anything they fall behind a bit and the vmware sync keeps them up-to-date. Adam Zimmer President Arius Software Corporation (519) 885-9045 x122 Ian McDonald wrote: How are your time sync options set for the VM? Is it keeping time ok? (note,AFAIR, you're not supposed to run NTP within a VM.). -- ian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
I checked running mii-tool and it indicated that it was only using 100basetx-FD. Not sure how to change this as using vmware server UI (just vmware server 1.04 not ESX) I don't see any options and also the config file doesn't list anything for the VM. The previous server was running 32 bit. Adam Zimmer President Arius Software Corporation (519) 885-9045 x122 Lukasz Szybalski wrote: On Thu, Mar 6, 2008 at 3:56 PM, Adam Zimmer [EMAIL PROTECTED] wrote: I have now removed those socket options. I am running Linux 2.6.22. However, the delays persist. Any other ideas? I thought it might be name resolution so I tried: name resolve order = wins host bcast But this hasn't helped either. Could you check what settings are set for the vmware network card speed. Is it in fact 1gb? My vmware as default made a 10/100 network card. Not sure what would be some other vmware specific settings that could be checked to see if it has issues. Was the previous server a 64bit as well? Lucas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
I had a similar problem using a machine running 3 VMs on a Linux host (Debian). I don't know what was actually wrong, but switching to a non-onboard NIC helped considerably. My working theory was that the combination of a crappy onboard chipset + promiscuous operation + VMWare Magic was causing it to drop packets, or generate too many interrupts, or something. As is always the case, I didn't have enough time to properly debug it, just fix it. Another theory I had, totally unsubstantiated but possible, was samba network interaction with the VMWare clock skewing problem under Linux 2.6. I'd try putting a high-quality NIC on the machine and see what happens. Another thing you might try is loading up the VMWare drive in VirtualBox and setting it up that way. VirtualBox uses Linux bridging instead of VMWare Magic, and I've seen it fix some things that VMWare didn't handle nicely. Wes On 03/06/2008 04:56 PM, Adam Zimmer wrote: I have now removed those socket options. I am running Linux 2.6.22. However, the delays persist. Any other ideas? I thought it might be name resolution so I tried: name resolve order = wins host bcast But this hasn't helped either. Adam Zimmer President Arius Software Corporation (519) 885-9045 x122 Charles Marcus wrote: On 3/6/2008, Adam Zimmer ([EMAIL PROTECTED]) wrote: I have tried various socket options including SO_RCVBUF=8192, SO_SNDBUF=8192, IPTOS_LOWDELAY, TCP_NODELAY, SO_KEEPALIVE. At the moment I have set SO_RCVBUF and SO_SNDBUF to be equal to 1400 as I noticed the MTU of the network card was 1500 which seems to but down on the broken pipes. I'm not saying this is cauing your problem, but you shouldn't be setting these at all, as long as you have a modern kernel (2.6 series)... These haven't been needed for a long time. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
Adam Zimmer wrote: At the moment I have enabled timeSync with vmware tools. In the general area of time keeping on the host, I added the following settings which avoided errors about the RTC missing interrupts: host.usefastclock=false host.cpukHz=240 host.useTSC=true ptsc.useTSC=true I have two other machines similarly configured (with the exception of running other linux applications not samba). Ntpdate seems to be installed as it is part of the ubuntu-server default config. However, my other machines seem to run it ok. If anything they fall behind a bit and the vmware sync keeps them up-to-date. Ian McDonald wrote: How are your time sync options set for the VM? Is it keeping time ok? (note,AFAIR, you're not supposed to run NTP within a VM.). True. I refer to this document from vmware. http://www.vmware.com/pdf/vmware_timekeeping.pdf Generally, ntp vmware timesync fight each other. The usual method is to turn off the ntp service, figure out how to minimize interrupts, allow the clock to run a little slow and allow vmware timesync to bump up the time when it gets about 1 minute slow. There's another thread that mentions issues with on-board nics and drivers. Over the years, I've bumped into that myself. To the extent I try and use host-only and route whenever possible. That's worked better for me in generic usage. Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems running samba in vmware
Douglas VanLeuven wrote: Adam Zimmer wrote: At the moment I have enabled timeSync with vmware tools. In the general area of time keeping on the host, I added the following settings which avoided errors about the RTC missing interrupts: host.usefastclock=false host.cpukHz=240 host.useTSC=true ptsc.useTSC=true I have two other machines similarly configured (with the exception of running other linux applications not samba). Ntpdate seems to be installed as it is part of the ubuntu-server default config. However, my other machines seem to run it ok. If anything they fall behind a bit and the vmware sync keeps them up-to-date. Ian McDonald wrote: How are your time sync options set for the VM? Is it keeping time ok? (note,AFAIR, you're not supposed to run NTP within a VM.). True. I refer to this document from vmware. http://www.vmware.com/pdf/vmware_timekeeping.pdf Generally, ntp vmware timesync fight each other. The usual method is to turn off the ntp service, figure out how to minimize interrupts, allow the clock to run a little slow and allow vmware timesync to bump up the time when it gets about 1 minute slow. There's another thread that mentions issues with on-board nics and drivers. Over the years, I've bumped into that myself. To the extent I try and use host-only and route whenever possible. That's worked better for me in generic usage. Regards, Doug Just an idea, although I've never tried it in vmware, if you can somehow make it a gig network connection and bring up the MTU and even enable NAPI in the guest, that should cut down on the IRQs, and slow clock drift. Also, if you have a VMI kernel on the guest (that might be VMWare server - 2.0 only, not sure), it should play a little nicer. Also, if you can turn off hardware offloading in the guest, it probably couldn't hurt. With VMs I've found slimmed down kernels really seem to drag less, although it could just be the power of suggestion on my own part after spending twenty minutes staring at 'make menuconfig'. Speaking of which, if you don't need X, running at runlevel 3 will help, too. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
