This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time.  This request will be
reviewed for a future Red Hat Enterprise Linux release.

*** Bug 443716 has been marked as a duplicate of this bug. ***

We have spent a significant amount of time trying to get the pypxeboot loader to
work even semi-reliably and failed on multiple occasions. PXE fundamentally
needs to be run from the context of the guest OS - paravirt boot process
fundamentally has to run from the Dom0 context. To make this work would require
creating fake Dom0 interfaces with the MAC address of the DomU, and getting PXE
client to attach to this interface rather than regular Dom0 one. In the unlikely
even that works, you're at the mercy of Dom0 network & firewall configuration.
pypxeboot is just a fundamentally flawed approach and cannot be made reliable
enough to consider for RHEL. Upstream Xen developers concurr & have rejected pxe
boot for paravirt.