Bug 247249 - xen doesn't show changeset information
Summary: xen doesn't show changeset information
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen
Version: 5.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Gerd Hoffmann
QA Contact: Martin Jenner
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-06 11:27 UTC by Gerd Hoffmann
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2007-10-25 13:48:06 UTC


Attachments (Terms of Use)
xen src tree patch (928 bytes, patch)
2007-07-06 11:28 UTC, Gerd Hoffmann
no flags Details | Diff
kernel spec file patch (1.45 KB, patch)
2007-07-06 11:29 UTC, Gerd Hoffmann
no flags Details | Diff

Description Gerd Hoffmann 2007-07-06 11:27:41 UTC
Description of problem:
xen doesn't show changeset information, neither in the boot log
nor in the "xm info" output.

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-el32 (xen coming with 3.1)

How reproducible:
"xm info"

Actual results:
[root@rhel5 ~]# xm info
[ ... ]
xen_changeset          : unavailable
[ ... ]

Expected results:
[root@rhel5 ~]# xm info
[ ... ]
xen_changeset          : 15042
[ ... ]

Additional info:

Comment 1 Gerd Hoffmann 2007-07-06 11:28:43 UTC
Created attachment 158651 [details]
xen src tree patch

Comment 2 Gerd Hoffmann 2007-07-06 11:29:14 UTC
Created attachment 158652 [details]
kernel spec file patch

Comment 3 Gerd Hoffmann 2007-07-06 11:30:44 UTC
posted for review on 2007-07-22

Comment 4 Stephen Tweedie 2007-07-06 11:40:48 UTC
I think we need this to include a clear indication that the release is NOT a
specific upstream changeset, but is in fact our own variant on that, complete
with other patches.  So perhaps

xen_changeset          : 15042.el5

makes sense.

Requesting for 5.2.


Comment 5 Stephen Tweedie 2007-07-06 11:43:13 UTC
Also, what do we do about the fact that userland is based off multiple different
releases (one for python, another for hvm environment); and that the kernel and
hypervisor are based off different csets, too?

Sounds like "unavailable" is actually the most accurate response to a user
asking what our Xen version is.  :)

Comment 6 Daniel Berrange 2007-07-06 13:30:38 UTC
Personally I recommend against including any form of changeset information,
simply because there is no meaningful changeset we can provide. The HV may be
based off 3.1, but its got a number of patches added. The userspace bears no
resemblance to any upstream changeset. Nor does the kernel. We should not try to
pretend that we have any correspondance to a changeset because it'll just
encourage people to make meaningless comparisons between functionality/bugs in
upstream vs our tree.

Comment 7 Red Hat Bugzilla 2007-07-25 00:53:41 UTC
change QA contact


Note You need to log in before you can comment on or make changes to this bug.