search for: vlanc

...t machine connects > > to host machine via vmnet1. I have dhcpd service on debian wheezy: > > root 8433 1 0 21:19 ? 00:00:00 /usr/sbin/dhcpd -q -cf > > /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid eth1 vmnet1 > > Thanks. > > vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware VMXNet3? Feel free to directly email me your .vmx file if you don't know. So that should be vlance or flexible (which can be PCNet32 or e1000). Could you verify with a real OS? I see it has two cores per socket. Is it one socket? What exact make/model is t...

On 03/08/2014 10:06 PM, Gene Cumm wrote: >> Hi Gene, >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got >> > the same issue. My client machine >> > still only shows: >> > ==================== >> > Getting cached packets >> > My IP is 192.168.120.1 >> > ==================== >> > The syslog log

...2014 at 8:09 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: >>> >>> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware >>> VMXNet3? Feel free to directly email me your .vmx file if you don't know. >> >> So that should be vlance or flexible (which can be PCNet32 or e1000). Could >> you verify with a real OS? > > I finally got the opportunity...

On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: >> >> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware >> VMXNet3? Feel free to directly email me your .vmx file if you don't know. > > So that should be vlance or flexible (which can be PCNet32 or e1000). Could > you verify with a real OS? I finally got the opportunity to test your VMX and I ca...

>>> ... Bottom line; There are timing issues with TFTP transfers on VM machines emulating BIOS hardware. Probably the interrupt based timer is not the culprit; now I'm working on /core/fs/pxe/core.c trying to see if there's something wrong there. Best, Patrick <<< I've been working on this issue, I have tested the timers, and as you guys mentioned before they

...transfer. > I wonder if the "vmxnet3" driver is probably "too fast" for the Sequential lwIP API? It's been a while since I bothered looking at the lpxelinux.0/TFTP issue in my VMware Workstation VMs. From what I recall, the vmxnet3 had the biggest issues and the others vlance/pcnet32, e1000, and e1000e, still had issues but to a far lower extent, topping out around 1-2 MB/s. Working in a VMware vSphere environment, VMware Workstation is a better fit for me and has been my primary testing area for years. At the moment, I have at least 6 different VMs on my main PC wit...

...g on debian wheezy. The client machine connects > to host machine via vmnet1. I have dhcpd service on debian wheezy: > root 8433 1 0 21:19 ? 00:00:00 /usr/sbin/dhcpd -q -cf > /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid eth1 vmnet1 > Thanks. vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware VMXNet3? Feel free to directly email me your .vmx file if you don't know. --Gene

...-devel at lists.ipxe.org" <ipxe-devel at lists.ipxe.org> On Mon, Mar 17, 2014 at 4:43 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > > Hi Gene, > > I tried to use pxelinux.0 version 4.07 and 4.05 but the issue still happens. In VMware Workstation 10.0.1 using vlance (pcnet32; AMD 79C970A) and Intel e1000 I have success on 4.07. Each shows a different !PXE info address, both by plan A. I think additional details are in order: iPXE version/commit, NICs (make/model/PCI ID) andiPXE format. -- -Gene

On 2014/3/10 ?? 05:48, Gene Cumm wrote: > 1) My assumption would be that the VMware virtualized AMD 79C970A > (PCNet32 driver; vlance virtualDev) lacks proper EFI64 support. > > 2) I have 0 speed issues using your VMX. If you only have two real > cores for this 2vCPU VM, you're choking it as the host needs time to > run. If you choke it, you mess with timers. If you mess with timers, > interface polling and...

On Thu, Jun 5, 2014 at 8:50 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > More information about this? > > I have found in the syslinux git that this commit id is the last good > commit: > > commit 41c29c26d70fde563d7c255872bbadad87a39dfa (tag: > refs/tags/syslinux-5.02-pre3) > Author: Matt Fleming <matt.fleming at intel.com> >

Hello Experts, I have a severe Problem with my current samba installations. Here in my Home-Office networt I have a dual-CPU machine with Debian Sarge, hosting some samba 3.0 shares and as well being a host for 4 vmware-sessions (Vmware Workstation v4.52, with 3xServer2003 and 1xXPpro). As well I have a separate raid5-server with samba 3.0 in the exakt same configuration (of course all parameters