| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit cda7fa973cbdd5fc4ad3974dcc6b5ea02ec6bb44)
|
|
|
|
|
|
|
| |
We could sometimes hit the 120 second timeout, eg. if the appliance
needed to be rebuilt and the machine was very slow and/or under heavy
I/O load. 10 minutes should be enough for any reasonable situation.
(cherry picked from commit 912284b02e28bd63bdf3397ef841b9782adfd2cd)
|
|
|
|
| |
(cherry picked from commit 95136b149212b92e87d0c9badb7d6849a084ed4d)
|
|
|
|
| |
(cherry picked from commit c7b88da039725ecd0d1d826b112bc69b518d4c78)
|
|
|
|
| |
(cherry picked from commit f0f3e1621180724e0a907a30ff5dea9695ddead0)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This simplifies the libguestfs-test-tool program down to essentials.
Bugs most commonly occur when starting the appliance, so what we
should concentrate on test is just that.
Previously the test tool built a special static binary helper program,
packaged it up in an ISO, then ran this inside the appliance. None of
this really tested useful failure modes, but they did make the test
tool itself harder to build, harder for users to run, and more
brittle.
This change also adds some more debugging of libguestfs state.
|
|
This is an end-user testing tool, designed to test basic functionality
of libguestfs/qemu/kernel combination on the end-user's final host
machine.
It does not perform a thorough test, but should be enough to find
most booting issues.
Also this is intended to be used when reporting bugs.
|