[ipxe-devel] Problem with ipxe on Xen 4.4

Eytan Heidingsfeld eytanh at gmail.com
Sat Dec 30 23:44:53 UTC 2017

Sorry for the delay,
Managed to test it locally too and it seems to fix the problem,
Thanks Too!


On Thu, Dec 28, 2017 at 2:16 PM, Michael Brown <mcb30 at ipxe.org> wrote:

> On 26/12/17 12:47, Michael Brown wrote:
>> On 25/12/17 11:20, Eytan Heidingsfeld wrote:
>>> I retried with DEBUG=xenbus and saw that xenbus_probe_type failed for
>>> the device: device/suspend/event-channel (I think because it doesn't have a
>>> backend key - it is empty). As this device isn't critical for the usage of
>>> netfront I just commented out the error in xenbus_probe_type for one device
>>> and now it works fine.
>>> Is there any reason failing to probe the type of one device should fail
>>> the whole probe of the xenbus?
>>> I can formalize a patch the prints a warning with DBG and allows it to
>>> continue but I was wondering if there was any downside to that?
>> Does the attached (untested) patch fix the problem?  This patch skips
>> probing any device type for which we don't have a driver anyway.
> I checked that this patch did not cause a regression, and have pushed it as
>   http://git.ipxe.org/ipxe.git/commitdiff/e4461f6
> Thanks!
> Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20171231/2e7a2009/attachment.htm>

More information about the ipxe-devel mailing list