[Xen-devel] boot failure in recent cset... dom0 compat issue?

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

Hmmm... somewhere between xen-unstable cset 19043 and 19109
my Intel Weybridge box stops booting dom0.  Is this a known
problem?  I am admittedly trying to boot a 4 months old
3.1-timeframe 2.6.18.8-based dom0.  Were hypervisor changes
made recently that render older dom0's useless? (I realize
this happens sometimes with xen-unstable, just wondering if
this is indeed the problem and, if so, if it was intentional.)

Thanks,
Dan


(XEN) PCI add device 00:03.2
(XEN) PCI remove device 00:03.2
(XEN) PCI add device 00:1f.5
(XEN) PCI remove device 00:1f.5
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1f.2
ata1.00: failed to set xfermode (err_mask=0x104)
ata1: port failed to respond (30 secs)
ata1: COMRESET failed (device not ready)
ata1.00: revalidation failed (errno=-5)
ata1: port failed to respond (30 secs)
ata1: COMRESET failed (device not ready)
ata1.00: revalidation failed (errno=-5)




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel