search for: 79c970a

...ond > NIC (null IP) > >> I see it has two cores per socket. Is it one socket? What exact make/model >> is the CPU in the host? You might be choking the VM. Have you considered >> just 1 socket and 1 core per socket? 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...

...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...

On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mar 8, 2014 9:27 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > > > > > > 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 > >