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:
Created attachment 158651 [details] xen src tree patch
Created attachment 158652 [details] kernel spec file patch
posted for review on 2007-07-22
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.
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. :)
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.
change QA contact