in XenDomain. The devices we will add, like network, will need to run
console commands when a domain is started. So I have made console be
a part of domain object, which it's tied to anyway.
Signed-off-by: Daniel Stekloff <dsteklof@us.ibm.com>
to respond first time. For restored and unpaused domains there is no need for
the console to output data, so we cannot use this as a way to detect the
liveness of a console. Instead, a command must always be sent to the console,
which means that this failure can only be detected once the constructor of the
Console class has returned successfully. The __chewall loop still remains, in
order to detect runaway consoles and to clear out previous data from the
console before executing commands, but we no longer treat failure of that
method to read data as a failure of the console itself.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
current Console.py API, because no bytes have come from it, but that's not a
failure -- an unpaused domain has no reason to output any more data. We need
to send a command to the domain before we can be sure whether it is alive or
dead, so move the FAIL call, allowing the console connection to throw
ConsoleError.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
in with xm-test in changeset 7634. It also adds an "autogen" script
that re-creates these files.
The auto-generated files really don't need to be in the tree, as they
should be generated by the user on the machine where they plan to run
xm-test.
Signed-off-by: Dan Smith <danms@us.ibm.com>
2. Change the MEM_PER_DOM amount in 11_create_concurrent to 24MB, so
that the test will run on x86_64.
3. Increase the number of DomUs created in 12_create_concurrent to 5
4. Fix a logic error in 01_unpause
5. Add a test 06_help that checks all xm commands with 0-10 arguments
to make sure none of them traceback with varying argument counts.
Signed-off-by: Dan Smith <danms@us.ibm.com>
emellor@leeni.uk.xensource.com