Displaying 6 results from an estimated 6 matches for "perves".
Did you mean:
serves
2014 Nov 27
2
pxelinux efi64 boot woes on hyper-v gen 2
Gene,
As it happened I started working on this again just as you mailed me.
It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy.
The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to
2014 Nov 28
0
pxelinux efi64 boot woes on hyper-v gen 2
On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote:
> Gene,
>
> As it happened I started working on this again just as you mailed me.
I saw it in IRC.
> It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no
2006 Oct 15
0
multiple smbd/nmbd on one machine
Hi everybody,
hope my question is not misplaced :)
I have an HA-Cluster (RHEL 4 update 3, Veritas Storage-Foundation
4.1, samba Version 3.0.10-1.4E.9) an have to run 3 different smbd/
nmbd on one machine.
So my smb.conf looks different for each "service", and is also stored
in a separate folder.
(Structure is:
/home/smb/domain/cfg/ ... #config for domain-controlling
2014 Nov 27
0
pxelinux efi64 boot woes on hyper-v gen 2
On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote:
> http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/
>
> P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of
2014 Nov 24
2
pxelinux efi64 boot woes on hyper-v gen 2
http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/
P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of TFTP server makes hyper-v happy. Virtualbox, VmWare seem to have the same EFI boot code & output
2014 Nov 28
2
pxelinux efi64 boot woes on hyper-v gen 2
Gene,
I found a document from IBM that explains why it didn't like Vendor-Class-Identifier option I was using "PXEClient" was causing EFI boot rooms to dummy spit, that's very useful, that combined with RTFMing the PXE specs 3.0-3.2 might solve my problem if I keep at it.
http://www-01.ibm.com/support/docview.wss?uid=swg21247032
Even the PXELinux docs suggest encapsulating