[ovirt-users] oVirt 3.6.4 / PXE guest boot issues

[Alan Griffiths]

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 was to present all VLANs on a single trunked vNIC to
the blade and configure VLAN tagging as per normal. The result is the tags
are stripped off the packets before being passed to the VM and DHCP now
works.

The same issue applies to VM-FEX as packets coming off the VF will have the
802.1q header. The only solution I can see here is to configure a bridged
interface for initial build of the VM and then switch to VM-FEX afterwards.

I found a discussion on the iPXE mailing list about addressing the vlan 0
issue, but I could see no agreed solution.

http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004901.html

Alan

--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HCN6MC4DSKN33RABI7LY2PLEQQGPZJDC/

[ovirt-users] oVirt 3.6.4 / PXE guest boot issues

[Alan Griffiths]

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 was to present all VLANs on a single trunked vNIC to
the blade and configure VLAN tagging as per normal. The result is the tags
are stripped off the packets before being passed to the VM and DHCP now
works.

The same issue applies to VM-FEX as packets coming off the VF will have the
802.1q header. The only solution I can see here is to configure a bridged
interface for initial build of the VM and then switch to VM-FEX afterwards.

I found a discussion on the iPXE mailing list about addressing the vlan 0
issue, but I could see no agreed solution.

http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004901.html

Alan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 3.6.4 / PXE guest boot issues

[Jamie Lawrence]

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 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
>
> --
>
> This communication is private and confidential and may contain information
> that is proprietary, privileged or otherwise legally exempt from
> disclosure. If you have received this message in error, please notify the
> sender immediately by e-mail and delete all copies of the message. In
> accordance with our guidelines, emails sent or received may be
> monitored.Inmarsat plc, Registered No 4886072 and Inmarsat Global Limited,
> Registered No. 3675885. Both Registered in England and Wales with
> Registered Office at 99 City Road, London EC1Y 1AX
>
> _
> This e-mail has been scanned for viruses by Verizon Business Internet
> Managed Scanning Services - powered by MessageLabs.
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 3.6.4 / PXE guest boot issues

[Alan Griffiths]

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



This communication is private and confidential and may contain information that 
is proprietary, privileged or otherwise legally exempt from disclosure. If you 
have received this message in error, please notify the sender immediately by 
e-mail and delete all copies of the message. In accordance with our guidelines, 
emails sent or received may be monitored.Inmarsat plc, Registered No 4886072 
and Inmarsat Global Limited, Registered No. 3675885. Both Registered in England 
and Wales with Registered Office at 99 City Road, London EC1Y 1AX

_
This e-mail has been scanned for viruses by Verizon Business Internet Managed 
Scanning Services - powered by MessageLabs.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt 3.6.4 / PXE guest boot issues

[David LeVene]

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 - but have since changed them back.

There's a few differences to the environment I setup as well and am looking for 
any pointers.

http://lists.ovirt.org/pipermail/users/2015-March/031690.html

This is the config & a fresh build as of last week - so I'm using ovirt 3.6.4


1.   All 3 physical hosts were built from a vanilla foreman server which 
does everything (TFTP, DNS, DHCP, Puppet, and Puppet CA) - this is the same 
server I'm trying to use for the guests, so I know it works for bare metal 
hosts.

2.   Ovirt engine was installed using the rpm bundle/image (Cent OS7)

3.   3 Node ovirt setup very close to this guide -  
http://blogs-ramesh.blogspot.com.au/2016/01/ovirt-and-gluster-hyperconvergence.html

4.   There is a VMFEX/SRIOV network setup in the oVirt config and this is 
what is being used to provision the guest VM's

When I try and boot a host via PXE (have tried e1000 etc, but leaving as VirtIO 
driver) it fails to get the DHCP address, I can see the broadcast traffic 
hitting the foreman server, and the foreman server replying with an IP - but it 
isn't getting to the guest, or the packets are getting corrupted. The UCS is 
correctly identifying and seeing the MAC address, so that looks good as well 
from the VMFEX side of things.

Tested the dhcp only component, so I grabbed an ISO and booted from a CD. The 
installer correctly got its DHCP address and proceed to install. Once the host 
was on-line it correctly got its IP via DHCP - So by this I've proven that a vm 
guest can correctly receive DHCP packets when using the VMFEX network.

Open to any further suggestions - as when using this and a foreman 
server/katello satellite pxe booting is kinda important!

Screenshot of iPXE boot version
[cid:image001.png@01D18E9F.FE7AA5D0]

Cheers
David
This email and any attachments may contain confidential and proprietary 
information of Blackboard that is for the sole use of the intended recipient. 
If you are not the intended recipient, disclosure, copying, re-distribution or 
other use of any of this information is strictly prohibited. Please immediately 
notify the sender and delete this transmission if you received this email in 
error.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users