A explanation/work-around for this issue raised back in April.
It seems that if, in UCS, you configure a vNIC with a single native VLAN it
will still add an 802.1q header with tag 0 - possibly to do with QoS. And
this extra header prevents iPXE from parsing the DHCP response.
The solution for me
A explanation/work-around for this issue raised back in April.
It seems that if, in UCS, you configure a vNIC with a single native VLAN it
will still add an 802.1q header with tag 0 - possibly to do with QoS. And
this extra header prevents iPXE from parsing the DHCP response.
The solution for me
I had the same issue a while back. Never figured it out, and don't have
much else useful to add, other than to say it isn't just you two.
-j
On Tue, Apr 5, 2016 at 3:22 AM, Alan Griffiths
wrote:
> Hi,
>
>
>
> I’m seeing the same PXE boot issue with 3.6.4 on Centos 7. Booting from
> ISO DHCP wor
Hi,
I'm seeing the same PXE boot issue with 3.6.4 on Centos 7. Booting from ISO
DHCP works fine. With PXE I can see the offer coming back from the DHCP server
but the VM just seems to ignore it. I also tried swapping the ROMs as per
previous post, but had no effect.
Alan
_
Hey All,
Summary: ipxe fails to get DHCP address, but it works when I don't use ipxe eg
from iso installer.
I'm running into the same issue which is noted in this thread, but the
workaround they used didn't seem to work for me. I only change the rom images
on the 1 ovirt host, nothing else - b
5 matches
Mail list logo