From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: boot failure in recent cset... dom0 compat issue? Date: Fri, 30 Jan 2009 20:57:21 +0000 (GMT) Message-ID: <0cd89c36-2cb0-48f7-b618-88a520791eb1@default> References: Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org > wrote: >=20 > > linux-2.6.18-xen.hg tip is c/s 786 > >=20 > > xen-19043 boots dom0linux-644 fine > > xen-19109 fails to boot dom0linux-644 > > xen-19064 boots dom0linux-644 fine > > xen-19065 fails to boot dom0linux-644 > > xen-19043 boots dom0linux-786 but I get no networking > > xen-19109 boots dom0linux-786 but I get no networking > >=20 > > Has something changed in tools that might need to > > be matched against latest xen and/or latest dom0, which > > might explain my networking disappearance? I'd > > upgrade tools too, but that's harder to back out if > > it doesn't work, and I'm not keen to reinstall this > > machine from scratch right now. >=20 > I don't think there have been any intentional interface=20 > breakages there just > now. So I don't really have an easy solution. >=20 > -- Keir Apologies, the networking problem was a red herring... a NIC driver issue that I had forgotten needs to be fixed every time I build a new dom0 kernel. So, yes, a matched hypervisor/dom0 tip set works for me now. So it appears, at least on some machines, that c/s 19065 renders dom0 no longer backwards-compatible. No big deal I guess but probably worth noting in the release notes for the 3.4 release. Dan