The KVM wiki is editable. You could always start writing something up
based on what you (and others) have been asked to provide, then ask
the devs to look it over when you are done.
Sent from my iPhone
On Jan 16, 2009, at 9:09 AM, paolo pedaletti
<[email protected]> wrote:
Ciao,
this mail just to say that it would be useful to have guide/howto that
explain some basic/standard action to help to debug failure on KVM.
The idea is the following:
most of the KVM users are just "users" (ok, maybe system
administrator,
but) not kernel hacker or programmer.
like most of the OpenOffice.org users.
I contribute to OpenOffice.org not coding but testing every new
version
with some basic/trivial test.
So instead saying "it doesn't work" it would be much more useful to
say:
it doesn't work, AND as the howto-help-kvm say, the result of the
following actions are:
(for example)
0) kvm command line is: .......
1) with -no-kvm .........
2) kvm_stat says ...
3) gdb says...
4) the filesystem is {qcow2|row|lvm2|...}
5) host computer is ...
6) guest computer is ...
7) ...
8) .
and all the test that a end-user (usually a sysadmin, a skilled person
but not a kernel hacker) con do to reproduce/explain/mitigate the
problem.
(by the way, is there an explanation of "Weekly KVM Testing Report"
tests?)
just my thought
thank you.
ciao
--
Paolo Pedaletti
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
