What |Removed |Added
------- Comment #5 from henning_sprang@xxxxxx 2007-07-03 01:37 -------
> Installed Fedora 5 no gui
> Kernel 2.6.15-1/2054_FC5 and installed Xen 3.0.3_6.fc5 from yum install
Please report bugs in Xen versions delivered by distribution vendors to these
They male significant changes (and deliver Linux Kernels that are not produced
by XenSource upstream), and they should check first, if these problems come
fromt these. Their development teams will forward problems that are repoducable
on upstream Xen current versions.
So the rest of this mail is more or less to help you write better bug reports,
which yoiu should send to the Fedora developers.
You should, still, try everything on an up to date version of Fedora and Xen
before posting a bug report to them, and try to ask the user lists for help.
> typed xend start; nothing
> typed xm list; nothing
"nothing" seems not to be a clear description of what is happening.
You will either get an error message on the console (at least, that the command
does not exist), or in the xen logfiles. "nothing" is very unlikely.
Still, it is normal that a reboot is needed after Xen packages are installed,
because the hypervisor needs to be loaded first.
> rebooted server
> received posted error
Where do you read the error message exactly? What else can be read in the Xen
log files? What processor is built into the system you are using (that seems to
be imprtant when debugging such a hardware-related feature)?
Please be aware, that tracking and fixing bugs in software is a very exact
science - without getting evenly exact error descriptions, developers cannot
make software better.
Sorry if my tone here is very direct, but the bug tracking system is only
useful when developers use it to coordinate their optimization work, and they
can only use it if bug reports from users are exact and help reproducing and
tracking down problems. This requires some care with entering bugs into the
system, and some rules to be followed.
Even then, ypu should add more info to the bug #1004 (which I just found when
researching for your problem) instead of keeping this one open.
#1004 is already about missing powernow support, and, if not the newest, at
least a newer version.
I also found the mailing list posts you mentioned and will add this info to the
*** This bug has been marked as a duplicate of 1004 ***
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Xen-bugs mailing list