From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: RE: boot failure in recent cset... dom0 compat issue?
Date: Fri, 30 Jan 2009 20:57:21 +0000 (GMT) [thread overview]
Message-ID: <0cd89c36-2cb0-48f7-b618-88a520791eb1@default> (raw)
In-Reply-To: <C5A8F6A8.941%keir.fraser@eu.citrix.com>
> <dan.magenheimer@oracle.com> wrote:
>
> > linux-2.6.18-xen.hg tip is c/s 786
> >
> > 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
> >
> > 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.
>
> I don't think there have been any intentional interface
> breakages there just
> now. So I don't really have an easy solution.
>
> -- 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
prev parent reply other threads:[~2009-01-30 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:12 boot failure in recent cset... dom0 compat issue? Dan Magenheimer
2009-01-29 22:32 ` Keir Fraser
2009-01-30 15:39 ` Dan Magenheimer
2009-01-30 15:51 ` Dan Magenheimer
2009-01-30 15:55 ` Keir Fraser
2009-01-30 15:51 ` Keir Fraser
2009-01-30 17:56 ` Dan Magenheimer
2009-01-30 18:25 ` Keir Fraser
2009-01-30 20:57 ` Dan Magenheimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cd89c36-2cb0-48f7-b618-88a520791eb1@default \
--to=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.